Reuben Thomas <[EMAIL PROTECTED]> writes:
>> But only if you start a second login shell, and you shouldn't be doing that.
>
> Sadly I don't have to do that. RedHat in their infinite wisdom run the
> scripts in /etc/profile.d from /etc/bashrc if they haven't already been
> run by /etc/profile.
The
On Thu, 4 Dec 2003, Jan Nieuwenhuizen wrote:
> Reuben Thomas <[EMAIL PROTECTED]> writes:
>
> >> But only if you start a second login shell, and you shouldn't be doing that.
> >
> > Sadly I don't have to do that. RedHat in their infinite wisdom run the
> > scripts in /etc/profile.d from /etc/bashrc
> But only if you start a second login shell, and you shouldn't be doing that.
Sadly I don't have to do that. RedHat in their infinite wisdom run the
scripts in /etc/profile.d from /etc/bashrc if they haven't already been
run by /etc/profile. I presume they have at least a plausible reason,
since
Reuben Thomas <[EMAIL PROTECTED]> writes:
> This isn't quite right, as every time you start a shell inside another
> one, TEXMF gets another copy of the path shoved on to the front.
But only if you start a second login shell, and you shouldn't be doing that.
Jan.
--
Jan Nieuwenhuizen <[EMAIL P
Sorry, I didn't read your suggestion carefully enough.
I have included the patch in CVS (both for lilypond-profile and
lilypond-login).
/Mats
Reuben Thomas wrote:
With your patch, the script will not work for people who already
have the TEXMF variable set for other reasons.
It will and it doe
> With your patch, the script will not work for people who already
> have the TEXMF variable set for other reasons.
It will and it does! That's the whole point of the patch. When my code
is run in a shell that already has TEXMF set, it checks whether the
Lilypond path is in it, and only adds it if
With your patch, the script will not work for people who already
have the TEXMF variable set for other reasons.
I cannot see that the current solution is any major problem, since
it should not occur very often that people start so many shells
inside each other that the variable length breaks any li
The Lilypond RPM contains the following stanza:
# Add the installation directory to the teTeX system tree,
# see Documentation/misc/fontinstallation
TEXMF="{$datadir,"`kpsexpand \\$TEXMF`"}"
export TEXMF
This isn't quite right, as every time you start a shell insi
