Closed GoogleCodeExporter closed 9 years ago
I'm not sure why they should conflict. It looks like QLM just defines and
registers for the
net.daringfireball.markdown UTI, which QLCC knows nothing about. In fact, I
just installed QLM and it seems
to be working side-by-side with QLCC. Do you have them both installed in the
same location?
The only oddities I can spot with QLM are:
1. It says that markdown is both public.plain-text and public.text, which is
redundant. (Only public.plain-
text is necessary)
2. It registers the .text file extension for markdown, which probably brings it
into conflict with the system's
UTI for plain text. You might try removing the "text" line (line 29) in QLM's
Info.plist and see if it helps.
You also might try rerunning qlmanage with the "-d 3" flag to get debugging
output. (This changed in Snow
Leopard.) If you run "qlmanage -m plugins | grep markdown" it'll tell you what
plugin the system has picked
for markdown. Beyond that, I can't help you much. Apple won't tell us how
they bind plugins to UTIs, so I
don't know how to fix problems with that process.
Original comment by n8gray@gmail.com
on 29 Sep 2009 at 6:02
Correction -- I see that the Info.plist file shipped with the plugin is
different from the one in their source
repository. The shipped version doesn't bind .text to markdown, but it does
still contain oddity #1 above.
BTW, what OS are you using and what kind of machine? The only other thing I
can think of is that QLM is being
penalized because it doesn't include a 64-bit intel binary. But my 64-bit Snow
Leopard machine uses it so that
doesn't seem likely...
Original comment by n8gray@gmail.com
on 29 Sep 2009 at 6:09
I'm typing away on a Mac Mini (circa 2007) with OS X 10.6.1 (x32 extensions,
because Apple wants it so).
Yeah, they're both in my ~/Library/QuickLook. Are you saying that if I shuffle
them around they might get
picked up differently, with the local overriding the one in
/System/Library/QuickLook? That would be so
UNIX-y of them.
1. I re-located QLCC to my desktop, to see a full debug output which looks
something like what you would
expect:
$ qlmanage -d3 -p text.markdown 2>&1
...
[DEBUG] Registering <QLGenerator Text.qlgenerator> for public.plain-text
...
[DEBUG] Registering <QLGenerator
/Users/yuli/Library/QuickLook/QLMarkdown.qlgenerator> for
net.daringfireball.markdown
...
[DEBUG] Preview test for text.markdown -- /Users/yuli/Desktop/. Content type
UTI: org.vim.markdown-file
[DEBUG] Previewing /Users/yuli/Desktop/text.markdown. Content type UTI:
org.vim.markdown-file.
Generator used: <QLGenerator Text.qlgenerator>
[DEBUG] Loading <QLGenerator Text.qlgenerator>
[DEBUG] Previewing file://localhost/Users/yuli/Desktop/text.markdown finished
Note the org.vim.markdown-file UTI. I have MacVim installed, which I use
daily.
Thanks for the tip on SL-specific qlmanage changes, by the way.
2. Nixed the "public.text" declaration from QLM, added a
"org.vim.markdown-file" declaration into
"LSItemContentTypes", and nudged the system by moving QLM bundle around. This
made it work, albeit with
a warning:
[WARNING] Plug-in at /Users/yuli/Library/QuickLook/QLMarkdown.qlgenerator/ is
32bit
Put QLCC back into my ~/Library/QuickLook and everything works as expected now.
I'm so sorry to have taken your time, but it just so happened that I was
looking for things to break when
installing QLCC, so I found some. :)
I'm going to go file a bug with QLM now. Thanks for helping me trace this to
source, and finally – QLCC is very
pretty and quite useful to me, so another 'thank you'.
Original comment by ycherkashin
on 29 Sep 2009 at 6:38
For further reference the bugs filed:
MacVim code.google.com/p/macvim/issues/detail?id=220
QLMarkdown github.com/toland/qlmarkdown/issues#issue/3
Original comment by ycherkashin
on 29 Sep 2009 at 7:09
Ok, it makes sense now. I'll bet that MacVim told the system that markdown is
public.source-code, which put
it into QLCC's domain. I'd been expecting weird problems like this for a long
time now but this is the first one
I've seen.
Actually you should file a bug with MacVim. I'd say
net.daringfireball.markdown is a more sensible UTI than
org.vim.markdown-file, and I would also say that it should conform to
public.plain-text instead of
public.source-code.
You should also file a bug with Apple asking for a central authority for
registering UTIs so this sort of thing
doesn't keep happening.
As for ~/Library/QuickLook overriding /Library/QuickLook, who knows? See this
post:
http://www.n8gray.org/blog/2009/09/24/brush-off-via-bug-report/
Original comment by n8gray@gmail.com
on 29 Sep 2009 at 7:14
Original issue reported on code.google.com by
ycherkashin
on 29 Sep 2009 at 1:37