On Mon, Oct 4, 2010 at 8:40 AM, Stephan Witt <[email protected]> wrote: > Am 04.10.2010 um 13:57 schrieb BH: > >> On Mon, Oct 4, 2010 at 6:04 AM, Stephan Witt <[email protected]> wrote: >>> Am 04.10.2010 um 09:22 schrieb Jürgen Spitzmüller: >>> >>>> Stephan Witt wrote: >>>>> The Mac default for lyxrc.template_path is not the path to LyX's >>>>> templates. >>>>> It's "~/Library/Application Support/l...@version_suffix@/templates". >>>>> That's why you have no templates at all at first. (It's like >>>>> "~/.lyx/templates") >>>> >>>> What is the rationale for this? As you write yourself, it's not really >>>> useful >>>> for many users (who do not have their own templates). And it derives from >>>> what >>>> LyX does on all other platforms. >>> >>> I don't know. It's like that since JMarc introduced it 5 years ago. >>> (http://www.lyx.org/trac/changeset/13231) >> >> The LyX Installer copies LyX's default templates to >> ~/Library/Application Support/LyX/templates/default. > > This I could know - but didn't know :-( > Shame on me. > > And now I'm trying to make an explicit installer obsolete. > It should somehow be built in LyX binary or external helper script. > E. g. the python script Richard wrote. > >> Hence, this is a >> way of making those templates available even without specialized open >> dialogs. (Otherwise, since these templates are inside the LyX.app >> bundle, non-power users will be unable to access them, let alone know >> about their existence.) > > Yes, I know. That's the problem I want to solve with or without the installer. > The same holds true for the example files distributed with LyX.
Yes -- what you're trying to do is clearly the right thing to do, and I'm glad you're taking it on. I just have no clearly better suggestions than what you've tried. The best kludge I can think of would be: 1. have LyX modify lyxrc's template path on launch to point to the current location inside the LyX application bundle (so that File > New from Template... opens in the right directory), and 2. create a new (Mac specific?) menu entry to bring up a dialog for opening example files -- perhaps under the File menu or maybe under the Help menu. Of course, this workaround is far from ideal. > The "copy solution" was rejected by Pavel in the thread "Re: Beta plans > (again, again)" > on 17th of September. But I see no other easy and fast solution, currently. It should perhaps be noted that copying templates, etc. into ~/Library/Application Support is quite common for applications on Mac. BH
