Re: Discussion: document class and fonts for manuals
On Sun, Jan 13, 2013 at 11:54 AM, John R. Hudson wrote: > On Sun, 2013-01-13 at 16:53 +0100, Uwe Stöhr wrote: >> Am 13.01.2013 09:55, schrieb John R. Hudson: >> >> > Since my last mail to the list, I have completed about two thirds of the >> > UserGuide; my plan was to go on to the Alternatives manual after that >> > and I will then look at Customization. >> >> So you only revised the language (writing style), right? That is fine for >> - Intro >> - Tutorial >> - UserGuide >> - Math >> - EmbeddedObjects >> > No, I have also changed things which do not match the current (2.0.5) > interface. I chose to start with the Intro, Tutorial and UserGuide > partly because when I looked on Trac the last commits were 8-9 months > ago and partly because I wanted to get an complete understanding of how > the different manuals hang together. > >> For Additional and Customization much more needs to be done because there >> are some things described >> which do no longer exists in LyX or were replaced by a new machinery. Many >> links are broken or >> outdated and I think we should remove the description of the document >> classes because they are >> completely outdated and these classes change more often than we release LyX. >> >> - Currently the only up-to-date chapter in Customization is chapter 5. >> - Currently the only up-to-date chapter in Additional is chapter 8. >> > Will pay special attention to them then. Do whatever you feel comfortable doing, John. Thank you for the help! Scott
Re: Discussion: document class and fonts for manuals
On Sun, 2013-01-13 at 16:53 +0100, Uwe Stöhr wrote: > Am 13.01.2013 09:55, schrieb John R. Hudson: > > > Since my last mail to the list, I have completed about two thirds of the > > UserGuide; my plan was to go on to the Alternatives manual after that > > and I will then look at Customization. > > So you only revised the language (writing style), right? That is fine for > - Intro > - Tutorial > - UserGuide > - Math > - EmbeddedObjects > No, I have also changed things which do not match the current (2.0.5) interface. I chose to start with the Intro, Tutorial and UserGuide partly because when I looked on Trac the last commits were 8-9 months ago and partly because I wanted to get an complete understanding of how the different manuals hang together. > For Additional and Customization much more needs to be done because there are > some things described > which do no longer exists in LyX or were replaced by a new machinery. Many > links are broken or > outdated and I think we should remove the description of the document classes > because they are > completely outdated and these classes change more often than we release LyX. > > - Currently the only up-to-date chapter in Customization is chapter 5. > - Currently the only up-to-date chapter in Additional is chapter 8. > Will pay special attention to them then. John --
Re: Discussion: document class and fonts for manuals
Am 13.01.2013 09:55, schrieb John R. Hudson: Since my last mail to the list, I have completed about two thirds of the UserGuide; my plan was to go on to the Alternatives manual after that and I will then look at Customization. So you only revised the language (writing style), right? That is fine for - Intro - Tutorial - UserGuide - Math - EmbeddedObjects For Additional and Customization much more needs to be done because there are some things described which do no longer exists in LyX or were replaced by a new machinery. Many links are broken or outdated and I think we should remove the description of the document classes because they are completely outdated and these classes change more often than we release LyX. - Currently the only up-to-date chapter in Customization is chapter 5. - Currently the only up-to-date chapter in Additional is chapter 8. There should only be one problem about returning the Intro and Tutorial to the article class; at one point I put in a New Page to improve the formatting under KOMA Script. OK. I have left Track changes set in the UserGuide; so you can see whether the changes I am suggesting are helpful. Thanks. best regards Uwe
Re: Discussion: document class and fonts for manuals
Am 13.01.2013 09:55, schrieb John R. Hudson: Since my last mail to the list, I have completed about two thirds of the UserGuide; my plan was to go on to the Alternatives manual after that and I will then look at Customization. So you only revised the language (writing style), right? That is fine for - Intro - Tutorial - UserGuide - Math - EmbeddedObjects For Additional and Customization much more needs to be done because there are some things described which do no longer exists in LyX or were replaced by a new machinery. Many links are broken or outdated and I think we should remove the description of the document classes because they are completely outdated and these classes change more often than we release LyX. - Currently the only up-to-date chapter in Customization is chapter 5. - Currently the only up-to-date chapter in Additional is chapter 8. There should only be one problem about returning the Intro and Tutorial to the article class; at one point I put in a New Page to improve the formatting under KOMA Script. OK. I have left Track changes set in the UserGuide; so you can see whether the changes I am suggesting are helpful. Thanks. best regards Uwe
Re: Discussion: document class and fonts for manuals
On Sun, 2013-01-13 at 04:24 +0100, Uwe Stöhr wrote: > Am 08.01.2013 10:30, schrieb John R. Hudson: > > > I have some time to go through the documentation and I wondered if we > > should change the default document class to article KOMA Script and the > > default fonts to Latin Modern. > > Hi John, > > we already discussed what is useful for what manual. For example the Intro > manual should be as > simple as possible in case KOMA script is not installed and special fonts are > not available. > > The UserGuide, EmbeddedObjects and Math manual need special packages because > their aim is to > describe everything LyX provides or what can be done with LyX. Therefore > their preamble is somewhat > complex. > > The Tutorial is a consensus of the Intro and the UserGuide. > > Latin Modern is already used by most of the documentation files. It is loaded > in the preamble to > assure that it can be compiles with the standard font of Latin Modern is not > available. Therefore it > need not to be loaded in the Document settings->Font section. > > If you have some time to revise the documentation files, I would like to ask > you if you can start > with the Additional manual and continue with the customization manual. > (PLEASE USE CHANGETRACKING!) > These manuals are extremely outdated and my time is currently too limited. > The last days I already > improved these files a bit and would estimate that a complete revision would > take weeks. I therefore > suggest to do it chapter by chapter. It is for these files more important to > update the information > (what can be done, can it now be done more elegant are the linked websites > still there...) If you > have any questions please contact the devel mailing list. Usually the > corresponding developer of a > certain feature will reply soon. > > regards Uwe Hi Uwe Since my last mail to the list, I have completed about two thirds of the UserGuide; my plan was to go on to the Alternatives manual after that and I will then look at Customization. I had been working on the Alternatives manual before I developed cataracts which affected my capacity to work on things. Since then I have kept all the emails to lyx-docs@lists.lyx.org and tried to deal with anything which did not appear to have been addressed so far. I thought it would be useful to work though all the manuals in part to familiarise myself with the manuals as a whole. There should only be one problem about returning the Intro and Tutorial to the article class; at one point I put in a New Page to improve the formatting under KOMA Script. I have left Track changes set in the UserGuide; so you can see whether the changes I am suggesting are helpful. John --
Re: Discussion: document class and fonts for manuals
Am 08.01.2013 10:30, schrieb John R. Hudson: I have some time to go through the documentation and I wondered if we should change the default document class to article KOMA Script and the default fonts to Latin Modern. Hi John, we already discussed what is useful for what manual. For example the Intro manual should be as simple as possible in case KOMA script is not installed and special fonts are not available. The UserGuide, EmbeddedObjects and Math manual need special packages because their aim is to describe everything LyX provides or what can be done with LyX. Therefore their preamble is somewhat complex. The Tutorial is a consensus of the Intro and the UserGuide. Latin Modern is already used by most of the documentation files. It is loaded in the preamble to assure that it can be compiles with the standard font of Latin Modern is not available. Therefore it need not to be loaded in the Document settings->Font section. If you have some time to revise the documentation files, I would like to ask you if you can start with the Additional manual and continue with the customization manual. (PLEASE USE CHANGETRACKING!) These manuals are extremely outdated and my time is currently too limited. The last days I already improved these files a bit and would estimate that a complete revision would take weeks. I therefore suggest to do it chapter by chapter. It is for these files more important to update the information (what can be done, can it now be done more elegant are the linked websites still there...) If you have any questions please contact the devel mailing list. Usually the corresponding developer of a certain feature will reply soon. regards Uwe
Re: Discussion: document and fonts for manuals - not needed?
Am 08.01.2013 23:47, schrieb John R. Hudson: Probably no need for a discussion: I have got to the User's Guide and realised that most manuals already use KOMA Script. So I will bring the manuals that do not into line with those that do. Hello John, what are your plans to do with the documentation? Concerning KOMA, there are reasons to use KOMA for some manuals but there are reasons that KOMA is fr example not used for the intro manual. regards Uwe
Discussion: document and fonts for manuals - not needed?
Hi all Probably no need for a discussion: I have got to the User's Guide and realised that most manuals already use KOMA Script. So I will bring the manuals that do not into line with those that do. John --
Fonts guide
Hi everyone, Is there likely to be any action on bug #269, "Do something with Robin's fonts document"? Robin -- "It takes less effort to condemn than to think." - Emma Goldman Robin Turner IDMYO Bilkent Univeritesi Ankara 06533 Turkey www.bilkent.edu.tr/~robin
Re: fonts
On Mon, May 20, 2002 at 02:01:11AM +0300, Robin wrote: > Is there any reason why my fonts HOWTO isn't the documentation for LyX > 1.2pre5? Does it suck or what? It is merely lack of time. I have a bug open on it. Perhaps Mike could have a look at it for general style issues, if there are any, and correctness http://bugzilla.lyx.org/show_bug.cgi?id=269 regards john -- "It is very difficult to prophesy, especially when it pertains to the future." - Patrick Kurzawe
fonts
Is there any reason why my fonts HOWTO isn't the documentation for LyX 1.2pre5? Does it suck or what? robin
Re: fonts
Here's an updated file, slightly delayed by a bug in 1.2 -- be careful
with cut-and-pasting ERT!
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
TrueType fonts available to conventional word processors, there are in
fact good reasons for this choice.
LyX actually has no fonts of its own; for the screen it uses whatever fonts
are available to the X-window system, and for output it uses the fonts
of the TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly-foun
d fonts available in TeX.
The
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning of this section is a case in point: most TeX distributions
include the
\family typewriter
yinit
\family default
font, so you should see a nice decorated
\begin_inset Quotes eld
\end_inset
L
\begin_inset Quotes erd
\end_inset
at the beginning; some distributions may not, so you won't.
\layout Standard
Another point is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
Nevertheless, you can, with a little Evil Red Text, make LyX produce just
about any font you want, and even design your own fonts.
What follows is a
\begin_inset Quotes eld
\end_inset
quick fix
\noun on
\begin_inset Quotes erd
\end_inset
\noun default
guide; it is no substitute for reading a good book on (La)TeX.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery font
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{pzc}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
pzc
\begin_inset Quotes erd
\end_inset
is the family name for the Zapf Chancery font).
You should be aware, however, that this method may produce strange results
if the font you have selected does not have the sizes or shapes you want
(e.g.
adding emphasis to text has no effect on Zapf Chancery, and choosing the
sans serif or typewriter series will cause it to revert to the standard
font).
\layout Subsubsection
More than one font family in one document
\layout Standard
As I've said, different font
Re: Fonts
Amir Karger wrote:
>
> On Tue, Sep 11, 2001 at 12:43:05PM +0300, Robin Turner wrote:
> > On Tuesday 11 September 2001 02:59, John Levon wrote:
> > >
> > > this sounds like a great idea !
> >
> > How should I submit it? As an attached .lyx doc?
>
> Probably easiest if you just submit a Word file, so everyone will be able to
> read it.
[repeats the incantation against trolls]
Here it is. The first letter is a bit of frivolity which not all readers
may like.
Robin
#LyX 1.2 created this file. For more info see http://www.lyx.org/
\lyxformat 220
\textclass article
\language english
\inputencoding latin5
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\use_natbib 0
\use_numerical_citations 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Subsection
Using different fonts in LyX
\layout Standard
by
\noun on
Robin Turner
\layout Standard
\begin_inset ERT
status Open
\layout Standard
\backslash
newfont{
\backslash
yinit}{yinit scaled
\backslash
magstep1}
\backslash
yinit
\end_inset
\layout Standard
L
\begin_inset ERT
status Open
\layout Standard
\backslash
normalfont
\end_inset
yX currently uses a fairly limited selection of fonts.
While it may come as a disappointment to people used to the thousands of
fonts available to conventional word processors, there are in fact good
reasons for this choice.
LyX has no fonts of its own; for the screen it uses whatever fonts are
available to the X-window system, and for output it uses the fonts of the
TeX setup it is operating with.
The selection of default faults correspond to the most useful and commonly
found fonts available in TeX.
For example, the first letter of this section, uses the Initial (yinit)
font.
You have
\emph on
probably
\emph default
got this in your TeX distribution, so it
\emph on
should
\emph default
come out as a big pretty gothic letter, but if you haven't, it won't.
Another factor is that the profusion of fonts which TrueType brought about
has generally had a bad effect on desktop publishing, leading to documents
with inappropriate, badly-scaled or simply too many fonts.
You should therefore think carefully before using a different default font,
or mixing font families in the same document.
\layout Standard
\noun on
Note
\noun default
: When trying out the various methods here, it's a good idea to make up
a test file containing a variety of headings and character styles, so that
you can see the effect different font commands have; for example, many
fonts will refuse to do headings.
\layout Subsubsection
Changing the default font
\layout Standard
The easiest and most reliable way to change the default font is from within
LyX, through
\family sans
Layout\SpecialChar \menuseparator
Document\SpecialChar \menuseparator
Fonts
\family default
.
The next easiest is to use a package contained in your TeX distribution.
For example, the rather pretty Pandora font family can be accessed simply
by putting
\family typewriter
\backslash
usepackage{pandora}
\family default
in your LaTeX preamble (
\family sans
Layout\SpecialChar \menuseparator
LaTeX\SpecialChar ~
preamble
\family default
).
Similarly,
\family typewriter
\backslash
usepackage{oldgerm}
\family default
in the preamble gives you access to Yannis Haralambous' Old German (Gothisch)
fonts via the specially-defined
\family typewriter
\backslash
gothfamily
\family default
,
\family typewriter
\backslash
swabfamily
\family default
, and
\family typewriter
\backslash
frakfamily
\family default
commands, which you insert in your document (as TeX) to obtain the desired
font (note that nothing will change in your screen display, which considering
the difficulty involved in reading some of these fonts is just as well).
Other useful packages are
\family typewriter
concrete
\family default
, which gives access to both the Concrete Roman and the Euler math fonts,
and
\family typewriter
chancery
\family default
, which gives you the Zapf Chancery fonts.
\layout Standard
A less reliable method is the
\family typewriter
\backslash
familydefault
\family default
command.
If you have a font installed and know its family name, you can put something
like
\layout Quote
\family typewriter
\backslash
renewcommand{
\backslash
familydefault}{rpxppl}
\layout Standard
in the preamble (
\begin_inset Quotes eld
\end_inset
rpxppl
\begin_inset Quotes erd
\end_inset
is the family name for the Palladio fonts).
\layout Standard
You should be aware that these methods may produce strange results if the
font you have selected does not have the sizes or shapes you want (e.g.
adding
Re: Fonts
On Tue, Sep 11, 2001 at 12:43:05PM +0300, Robin Turner wrote: > On Tuesday 11 September 2001 02:59, John Levon wrote: > > > > this sounds like a great idea ! > > How should I submit it? As an attached .lyx doc? Probably easiest if you just submit a Word file, so everyone will be able to read it. -Amir
Re: Fonts
On Tuesday 11 September 2001 02:59, John Levon wrote: > On Mon, Sep 10, 2001 at 06:27:41PM +0300, Robin Turner wrote: > > Would the doc team be interested in a section on using different fonts to > > go in "Extended features"? I have a piece which might be suitable, > > covering changing the default font (to use fonts not available in the > > popup), using more than one font family in the same document and > > installing TeX fonts. > > this sounds like a great idea ! How should I submit it? As an attached .lyx doc? Robin
Re: Fonts
On Mon, Sep 10, 2001 at 06:27:41PM +0300, Robin Turner wrote: > Would the doc team be interested in a section on using different fonts to go > in "Extended features"? I have a piece which might be suitable, covering > changing the default font (to use fonts not available in the popup), using > more than one font family in the same document and installing TeX fonts. this sounds like a great idea ! regards john -- "Since when would the sizeof any kind of pointer be zero ? Have you built a zero-bit CPU ?" - Jeffrey Turner
Fonts
Would the doc team be interested in a section on using different fonts to go in "Extended features"? I have a piece which might be suitable, covering changing the default font (to use fonts not available in the popup), using more than one font family in the same document and installing TeX fonts. Robin
Re: LyX X fonts and the command line
> "Lior" == Lior Silberman <[EMAIL PROTECTED]> writes: Lior> I've since found out about ~/.lyx/doc/LaTeXConfig.lyx, so the Lior> doc subdir should be unique and not cross-linked. I'm reposting Lior> the doc to reflect this. Are there other such problems ? I included your document in Customization.lyx (with description of the environment variable). I think we can leave it like that for now (I hope we'll get read of the generated LaTeXConfig.lyx soon). JMarc
Re: LyX X fonts and the command line
> On Mon, May 29, 2000 at 05:22:47PM +0300, Lior Silberman wrote:
> > Hi,
> > I'm attaching the promised documentation to the -userdir feature.
> > I wasn't sure about something:
> >
> > This feature allows having several personal configuration directories
> >(similar to ~/.lyx). In this case I'd probably like to have the layouts,
> > docs and similar sub-directories in them be symbolic links to ~/.lyx so I
> > have less maintenance to do. However, if the "Options -> Reconfigure"
> > script writes in these directories, and not only in lyxrc, then it may not
> > be a good idea.
> >
> > Could someone comment on this?
> >
>
I've since found out about ~/.lyx/doc/LaTeXConfig.lyx, so the doc subdir
should be unique and not cross-linked. I'm reposting the doc to reflect
this. Are there other such problems ?
Lior.
#LyX 1.1 created this file. For more info see http://www.lyx.org/
\lyxformat 2.16
\textclass article
\language default
\inputencoding latin1
\fontscheme default
\graphics default
\paperfontsize default
\spacing single
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
\paperorientation portrait
\secnumdepth 3
\tocdepth 3
\paragraph_separation indent
\defskip medskip
\quotes_language english
\quotes_times 2
\papercolumns 1
\papersides 1
\paperpagestyle default
\layout Subsection
Running
\latex latex
LyX with multiple configurations
\layout Standard
The configuration freedom of the local configuration directory may not suffice
if you want to have more than one configuration at your disposal.
For example, you may want to be use different key bindings or printer settings
at different times.
You can achieve this by having several such directories.
You then specify which directory to use at run-time.
\layout Standard
Invoking LyX with the command line switch
\family typewriter
-userdir
\family default
\emph on
\emph default
instructs the program to read the configuration from that directory, and
not from the default directory (you can determine the default directory
by running LyX without this switch as described above).
If this directory does not exist, LyX offers to create it for you, just
like it does for the default directory on the first time you run the program.
You can modify the configuration options in this additional
\family typewriter
Userdir
\family default
exactly as you would for the default directory.
These directories are completely independent (but read on).
\layout Standard
Having several configurations also requires more maintenance: if you want
to add a new layout to
\family typewriter
Userdir/layouts
\family default
which you want available from all your configurations, you must add it
to each directory separately.
You can avoid this with the following trick: after LyX creates the additional
directory, most of the subdirectories (see above) are empty.
If you want the new configuration to mirror an existing one, replace the
empty subdirectory with a symbolic link to the matching subdirectory in
the existing configuration.
Take care with the
\family typewriter
\series medium
doc/
\family default
\series default
subirectory, however, since it contains a file written by the configuration
script (also accessible through
\family sans
\bar under
O
\bar default
ptions\SpecialChar \menuseparator
\bar under
R
\bar default
econfigure
\begin_inset LatexCommand \ref{sec:autodetected}
\end_inset
)
\family default
which is configuration-specific.
[
\emph on
Author's Note: Would reconfigure work properly with other cross-referenced
directories? ---
\emph default
ls].
\layout Standard
[
\emph on
Author's Note: Should we document the environment-variable method to change
the userdir? ---
\emph default
ls].
\the_end
Re: LyX X fonts and the command line
Hi, I'm attaching the promised documentation to the -userdir feature. I wasn't sure about something: This feature allows having several personal configuration directories (similar to ~/.lyx). In this case I'd probably like to have the layouts, docs and similar sub-directories in them be symbolic links to ~/.lyx so I have less maintenance to do. However, if the "Options -> Reconfigure" script writes in these directories, and not only in lyxrc, then it may not be a good idea. Could someone comment on this? Lior. On 29 May 2000, Jean-Marc Lasgouttes wrote: > > "Lior" == Lior Silberman <[EMAIL PROTECTED]> writes: > > Lior> BTW If you think it's useful, I canadd a pagaraph somewhere in > Lior> the docs about 'running lyx with multiple configurations'. > > Would you care to submit something? :) > > JMarc > #LyX 1.1 created this file. For more info see http://www.lyx.org/ \lyxformat 2.16 \textclass article \language default \inputencoding latin1 \fontscheme default \graphics default \paperfontsize default \spacing single \papersize Default \paperpackage a4 \use_geometry 0 \use_amsmath 0 \paperorientation portrait \secnumdepth 3 \tocdepth 3 \paragraph_separation indent \defskip medskip \quotes_language english \quotes_times 2 \papercolumns 1 \papersides 1 \paperpagestyle default \layout Subsection Running \latex latex LyX with multiple configurations \layout Standard The configuration freedom of the local configuration directory may not suffice if you want to have more than one configuration at your disposal. For example, you may want to be use different key bindings or printer settings at different times. You can achieve this by having several such directories. You then specify which directory to use at run-time. \layout Standard Invoking LyX with the command line switch \family typewriter -userdir \family default \emph on \emph default instructs the program to read the configuration from that directory, and not from the default directory (you can determine the default directory by running LyX without this switch as described above). If this directory does not exist, LyX offers to create it for you, just like it does for the default directory on the first time you run the program. You can modify the configuration options in this additional \family typewriter Userdir \family default exactly as you would for the default directory. These directories are completely independent (but read on). \layout Standard Having several configurations also requires more maintenance: if you want to add a new layout to \family typewriter Userdir/layouts \family default which you want available from all your configurations, you must add it to each directory separately. You can avoid this with the following trick: after LyX creates the additional directory, most of the subdirectories (see above) are empty. If you want the new configuration to mirror an existing one, replace the empty subdirectory with a symbolic link to the matching subdirectory in the existing configuration. Similarly, running \family sans \bar under O \bar default ptions\SpecialChar \menuseparator \bar under R \bar default econfigure \family default will only update the configuration for the current \family typewriter Userdir \family default . [ \emph on Author's Note: Would reconfigure work properly with these cross-referenced directories? --- \emph default ls]. \layout Standard [ \emph on Author's Note: Should we document the environment-variable method to change the userdir? --- \emph default ls]. \the_end
