M. C. D. wrote:
>> The documentation is good, but it's getting old. I'd encourage you
>> --- anybody and everybody, in fact --- to post here any changes you
>> think would improve it. There are places where things are now so
>> out of date they're just plain wrong. The layout sections are a
>> case in point. Would you consider adding a paragraph or two to make
>> things clearer in light of your own experiences.)
>
> I wouldn't mind, but I don't know how LyX is supposed to behave.
> LyX/Mac is a little unusual, and I'm also using the Mac distribution
> of
> teTeX rather than the standard Unix one. It turned out that I
> didn't need to install my package in TEXMFLOCAL at all - its regular
> location in HOMETEXMF works fine - but having no other system to
> test on I'm not sure whether that's normal behavior.
Put it this way: if you can add a layout to your machine and get it
working, then others will be able to distil something from your
experiences only if you document them.
>> In general you probably shouldn't change things in the globally
>> accessible directories. At least, not until you're happy with the
>> new layout. LyX differentiates between system configuration files,
>> to be found in ${PREFIX}/share/lyx/
>
> LyX/Mac files appear to be in
> /Applications/LyX.app/Contents/Resources/LyX/.
Whatever. Different names, same principle.
>> and user files, usually found in
>> ${HOME}/.lyx. I'd recommend that you put your new layout file in
>> the ${HOME}/.lyx/layouts directory.
>
> That works too, but can it resolve inputs from there? How would I
> know if it failed?
I'm not sure I understand what "resolve inputs from there" means.
LyX searches the global directory first and then the user directory.
Anything found in the user directory overwrites the same entry in the
global directory. Anything found in the user directory that's not
present in the global directory is simply added.
So, you'll know it failed if you run lyx and your new class layout
isn't present.
--
Angus
