[OS X TeX] TeXShop's %& ugly bug

[Jérôme Laurens]

Le 10 sept. 04, à 12:43, Will Robertson a écrit :

>
> On 10 Sep 2004, at 7:37 PM, Maarten Sneep wrote:
>
>> On 10 sep 2004, at 11:55, Will Robertson wrote:
>>
>>> On 10 Sep 2004, at 6:22 PM, Maarten Sneep wrote:
>>>
>>>> I'd like to add that there should be no real reason to reinvent the 
>>>> wheel: emacs has added meta-data information to tex and other 
>>>> file-types for years. The important ones (master-file and 
>>>> character-encoding) are all there, and I think adding some 
>>>> application specific ones would not be horribly hard.
>>>
>>> Do you know the specifics of how this is done? Is it simply comments 
>>> at the top of the document, or instead a separate file with the 
>>> information inside? It does seem sensible to coerce emacs' method.
>>
>> A set of comments at the end of the file, I'd have to look up a 
>> sample somewhere to get at the specifics, but there are emacs users 
>> on this list (and even the porter of Carbon enhanced emacs hangs 
>> around here), and I think they can provide much more detailed answers 
>> of how emacs does things.
>
> From the AUCTeX documentation (v11.50, which I haven't even worked out 
> how to install yet), it looks something like this at the end of a 
> file: (couldn't find an example for the character encoding)

The character encoding is given in the first line of the file and does 
not seem related to AUCTeX

%-*-coding=blah-*-

It is a list of semicolon separated instructions.

>
> %%% Local Variables:
> %%% TeX-master: "master"
> %%% TeX-command-default: "SliTeX"
> %%% End:
>
> It's ugly enough that I'd be happy just re-implementing the %& 
> functionality to use a different prefix. I find the whole issue fairly 
> trivial, though.

Hummmm, not that trivial I'm afraid...
Moreover, very inefficient if you have to parse the whole file just to 
know the master one, or the command to perform.
This is not a good design if you want to separate the editor and the 
TeX frontend.

An external file would be significantly better. Why not defining 
something more general?

--------------------- Info ---------------------
Mac-TeX Website: http://www.esm.psu.edu/mac-tex/
           & FAQ: http://latex.yauh.de/faq/
TeX FAQ: http://www.tex.ac.uk/faq
List Post: <mailto:MacOSX-TeX at email.esm.psu.edu>