On 05/07/09 08:26, "[email protected]" <[email protected]> wrote:
>>>> For giggles, I trashed TeXLiveUtility, and then quit Finder. I >>>> restarted Finder, and voilà, I can open DVI with Skim again. Odd >>>> that this is the case; I've had TeXLiveUtility up for weeks now with >>>> none of this nonsense. >> >> Was TLU was running while you updated Skim? > > No, it was not. Skim was already on my machine months ago, when I first > installed TLU. Perhaps "being there first" gave Skim control over DVI's, and > when I updated Skim, the newer version of Skim was no longer "there before > TLU", which gave TLU governing power. I am not going to reinstall TLU since I > don't want to foul things up again, and it was only there for play purposes. I understand. However, there's nothing I can do about this in TLU. If multiple applications/bundles declare a UTI for the same file type (e.g. dvi = org.tug.tex.dvi and dvi = net.sourceforge.skim-app.dvi) and both are imported, the results are not deterministic. I think there are a couple of solutions on the Skim side: a) declare the DVI UTI as exported so it overrides all others b) add org.tug.tex.dvi in LSItemContentTypes for .dvi Neither would break TLU's plugins. I'm prodding the MacTeX group to see if we can get some action on a formal community recommendation for UTIs. It may or may not be org.tug.tex. ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Skim-app-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/skim-app-users
