bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in /etc/profile.d/lilypond.sh (with fix!)


From: Mats Bengtsson
Subject: Re: Bug in /etc/profile.d/lilypond.sh (with fix!)
Date: Wed, 03 Dec 2003 15:16:07 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

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 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 it isn't.


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 limits.


That's not the only potential problem. It also changes the search order so
that Lilypond's files come first. What if I want to override them?
I set all my environment variables in .bash_profile, so they don't get
reset in every shell. But to override Lilypond's files, I'd have to set
TEXMF in .bashrc or something.

And "people" may not start many nested shells, but scripts may well.
Anyway, it's just plain ugly adding the same path repeatedly.


It will still work even if the same path happens to occur several
times.


I will indeed still work, but, for example, when I run texhash, it tries
to update the lilypond ls-R multiple times.


--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
        Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================





reply via email to

[Prev in Thread] Current Thread [Next in Thread]