I am seeing the same thing in the Finder on Catalina. My output is the same:
🦊 qlmanage -m plugins | grep TextMate public.source-code -> /Applications/TextMate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator (1.0) public.text -> /Applications/TextMate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator (1.0)
Off topic (apologies in advance if I am stating the obvious): When a message is being composed as rich text (depends on your email client settings; but I believe the default is to reply in the same format is as them message that was received); with a simple copy and paste (⌘ + V) the OS carries the style information and pastes the contents using that formatting. This is what you are seeing. If you don’t want the formatting to happen you paste the content using the “Paste and Match Style” option in the Edit menu (⌥ + ⇧ +⌘ + V).
Best, Farhan
On May 31, 2020, at 8:00 AM, textmate-request@lists.macromates.com wrote:
From: "Marc Wilson" <posguy99@gmail.com mailto:posguy99@gmail.com> Subject: [TxMt] Re: TM's QuickLook plugin Date: May 30, 2020 at 12:18:26 PM EDT To: "TextMate Mailing List" <textmate@lists.macromates.com mailto:textmate@lists.macromates.com> Reply-To: TextMate users <textmate@lists.macromates.com mailto:textmate@lists.macromates.com>
No, just Finder here. Well, Finder and Forklift, but Forklift is not replacing anything, it’s just the OFM I use.
I’ve been poking around and TM’s QL generator on Catalina is not being registered for the same filetypes that it is on Mojave. I’ve collected a bunch of resources and am trying to make time to see if I can do some investigation.
Can I ask you, what filetypes does your Catalina install have registered to the TM plugin?
[ 9:16 AM][ttys000][/Users/mwilson] mbp13 $ qlmanage -m plugins | grep TextMate public.source-code -> /Applications/TextMate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator http://textmate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator (1.0) public.text -> /Applications/TextMate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator http://textmate.app/Contents/Library/QuickLook/TextMateQL.qlgenerator (1.0) [ 9:16 AM][ttys000][/Users/mwilson]
(unrelated side comment… wow, that was weird… I didn’t expect a c-n-p from Terminal into my email client to bring the Terminal theme with it)
-- Marc Wilson posguy99@gmail.com mailto:posguy99@gmail.com
On Sun, May 31, 2020 at 9:02 AM Farhan Ahmed inshany@gmail.com wrote:
I am seeing the same thing in the Finder on Catalina. My output is the same:
*🦊* qlmanage -m plugins | grep TextMate public.source-code -> /Applications/*TextMate* .app/Contents/Library/QuickLook/*TextMate*QL.qlgenerator (1.0) public.text -> /Applications/*TextMate*.app/Contents/Library/QuickLook/ *TextMate*QL.qlgenerator (1.0)
I was not aware of the qlmanage utility until I saw this email....
I am running MacOS 10.14.6 (Mojave) and when I use QuickLook to view a source file such as Foo.scala I just get the generic QuickLook window describing the file.
But if I use this command: qlmanage -p -c public.source-code U.scala
Then I get the correct QuickLook window that uses the TextMate theme.
It seems that the Finder is not associating the "public.source-code" type with the file. However I have told Finder to open all .scala files with TextMate and indeed it is listed as the default App for opening the files. Not sure if there is something else that must be done so that Finder knows that this is a source code file?
The problem is that, on both my Catalina Mac and Mojave Mac, TM’s plugin is registered as being responsible for public.source-code.
But I get the built in Text QL generator being used on Catalina.
I have plenty of, for example, *.applescript files. On Mojave, they’re nicely themed when you QL them. On Catalina, the Text viewer is used. On both machines, the OS thinks they’re public.source-code.
-- Marc Wilson posguy99@gmail.com
On Sun, May 31, 2020, at 9:39 AM, Curt Sellmer wrote:
On Sun, May 31, 2020 at 9:02 AM Farhan Ahmed inshany@gmail.com wrote:
I am seeing the same thing in the Finder on Catalina. My output is the same:
*🦊* qlmanage -m plugins | grep TextMate public.source-code -> /Applications/*TextMate*.app/Contents/Library/QuickLook/*TextMate*QL.qlgenerator (1.0) public.text -> /Applications/*TextMate*.app/Contents/Library/QuickLook/*TextMate*QL.qlgenerator (1.0)
I was not aware of the qlmanage utility until I saw this email....
I am running MacOS 10.14.6 (Mojave) and when I use QuickLook to view a source file such as Foo.scala I just get the generic QuickLook window describing the file.
But if I use this command: qlmanage -p -c public.source-code U.scala
Then I get the correct QuickLook window that uses the TextMate theme.
It seems that the Finder is not associating the "public.source-code" type with the file. However I have told Finder to open all .scala files with TextMate and indeed it is listed as the default App for opening the files. Not sure if there is something else that must be done so that Finder knows that this is a source code file?
TextMate mailing list TextMate@lists.macromates.com https://lists.macromates.com/listinfo/textmate
On 31 May 2020, at 12:39, Curt Sellmer wrote:
I was not aware of the qlmanage utility until I saw this email....
I am running MacOS 10.14.6 (Mojave) and when I use QuickLook to view a source file such as Foo.scala I just get the generic QuickLook window describing the file.
But if I use this command: qlmanage -p -c public.source-code U.scala
Then I get the correct QuickLook window that uses the TextMate theme.
It seems that the Finder is not associating the "public.source-code" type with the file. However I have told Finder to open all .scala files with TextMate and indeed it is listed as the default App for opening the files. Not sure if there is something else that must be done so that Finder knows that this is a source code file?
You can always see what UTIs the system thinks a file has by running
mdls -name kMDItemContentTypeTree filename.xyz
I forget what (if any) influence installed apps have on the list, but that’s almost certainly what Finder is using.
Yup, and thus:
[ 3:25 PM][ttys001][/Users/mwilson]
mbp13 $ mdls -name kMDItemContentTypeTree hello.c
kMDItemContentTypeTree = (
"public.c-source",
"public.source-code",
"public.plain-text",
"public.text",
"public.data",
"public.item",
"public.content"
)
Should mean that the TW generator would be used, since there is no registration for public.c-source, and TM owns the registration for public.source-code. But it isn’t.
Or this one:
[ 3:28 PM][ttys002][../AppleScript/BBEdit]
mbp13 $ mdls -name kMDItemContentTypeTree Create\ New\ File.applescript
kMDItemContentTypeTree = (
"com.apple.applescript.text",
"public.script",
"public.source-code",
"public.plain-text",
"public.text",
"public.data",
"public.item",
"public.content"
)
Should produce the same result. But it doesn’t.
-- Marc Wilson posguy99@gmail.com
On Sun, May 31, 2020, at 1:52 PM, Rob McBroom wrote:
On 31 May 2020, at 12:39, Curt Sellmer wrote:
I was not aware of the qlmanage utility until I saw this email....
I am running MacOS 10.14.6 (Mojave) and when I use QuickLook to view a source file such as Foo.scala I just get the generic QuickLook window describing the file.
But if I use this command: qlmanage -p -c public.source-code U.scala
Then I get the correct QuickLook window that uses the TextMate theme.
It seems that the Finder is not associating the "public.source-code" type with the file. However I have told Finder to open all .scala files with TextMate and indeed it is listed as the default App for opening the files. Not sure if there is something else that must be done so that Finder knows that this is a source code file?
You can always see what UTIs the system thinks a file has by running
`mdls -name kMDItemContentTypeTree filename.xyz
`
I forget what (if any) influence installed apps have on the list, but that’s almost certainly what Finder is using.
-- Rob McBroom
TextMate mailing list TextMate@lists.macromates.com https://lists.macromates.com/listinfo/textmate
In my case:
[curt:misc]$ mdls -name kMDItemContentTypeTree U.scala kMDItemContentTypeTree = ( "dyn.ah62d4rv4ge81g25brvuu", "public.item", "dyn.ah62d4rv4ge81g25brvuu", "public.data" )
public.source-code is not in the list. How can I add it to the list of Content Types?
For me, it just happened, even though it doesn't seem to fail downwards correctly. I don't claim to understand the processes that are happening behind the scenes in macOS... this information is not stored in the filesystem, so I can only assume that it's something Spotlight assigns to the files and puts in a database somewhere.
Allan said something about it being in the Launch Services database?
A question... is *.scala the normal file extension for files of that type?
-- Marc Wilson posguy99@gmail.com
On Sun, May 31, 2020, at 5:32 PM, Curt Sellmer wrote:
In my case:
[curt:misc]$ mdls -name kMDItemContentTypeTree U.scala kMDItemContentTypeTree = ( "dyn.ah62d4rv4ge81g25brvuu", "public.item", "dyn.ah62d4rv4ge81g25brvuu", "public.data" )
public.source-code is not in the list. How can I add it to the list of Content Types?
TextMate mailing list TextMate@lists.macromates.com https://lists.macromates.com/listinfo/textmate
On Mon, Jun 1, 2020 at 10:01 AM Marc Wilson posguy99@gmail.com wrote:
A question... is *.scala the normal file extension for files of that type?
Yes it is the normal file extension for Scala source files.
I noticed that the info.plist file for TextMate contains entries for .c, .java, etc. but does not contain an entry for .scala (Not surprising since it is not as common a language).
Using QL for files that are listed in the info.plist file works for me so perhaps this is just a known limitation.
Sounds like your issue on Catalina is something different.
If I try to force the file type for my Applescript files, I still get the generic text viewer. In fact, so far I haven't been able to get the TextMate QL generator to be used for ANYTHING. Does it work on Catalina for anyone at all? I don't mean the auto-detect of the file type... I mean if you force the file type to be something TM has supposedly been registered for, does it get used?
The OS pops those two error messages each time qlmanage is invoked, but that happens on Mojave too, and it works there. Google says *everyone *gets those two errors regardless.
Curt, you said you were using Mojave, so...
-- Marc Wilson posguy99@gmail.com
On Sun, May 31, 2020, at 9:39 AM, Curt Sellmer wrote:
On Sun, May 31, 2020 at 9:02 AM Farhan Ahmed inshany@gmail.com wrote:
I am seeing the same thing in the Finder on Catalina. My output is the same:
*🦊* qlmanage -m plugins | grep TextMate public.source-code -> /Applications/*TextMate*.app/Contents/Library/QuickLook/*TextMate*QL.qlgenerator (1.0) public.text -> /Applications/*TextMate*.app/Contents/Library/QuickLook/*TextMate*QL.qlgenerator (1.0)
I was not aware of the qlmanage utility until I saw this email....
I am running MacOS 10.14.6 (Mojave) and when I use QuickLook to view a source file such as Foo.scala I just get the generic QuickLook window describing the file.
But if I use this command: qlmanage -p -c public.source-code U.scala
Then I get the correct QuickLook window that uses the TextMate theme.
It seems that the Finder is not associating the "public.source-code" type with the file. However I have told Finder to open all .scala files with TextMate and indeed it is listed as the default App for opening the files. Not sure if there is something else that must be done so that Finder knows that this is a source code file?
TextMate mailing list TextMate@lists.macromates.com https://lists.macromates.com/listinfo/textmate
On Jun 1, 2020, at 10:07 AM, Marc Wilson posguy99@gmail.com wrote:
In fact, so far I haven't been able to get the TextMate QL generator to be used for ANYTHING. Does it work on Catalina for anyone at all?
It does not work for me on two different Catalina machines I have tested. All previews seem to be plain text. See related discussion in the archives for last month "Code preview in Finder"
John DeSoi, Ph.D.
-
Curt Sellmer -
Farhan Ahmed -
John DeSoi -
Marc Wilson -
Rob McBroom