On Sun, Mar 07, 2004 at 03:03:30PM +0100, Matthias Kilian wrote:
[Letters and digits in identifiers]
> If there's no other reason for disallowing digits than to keep
> parser/scanner, I could try to write a patch.
Quick hack alert! The patch below appears to work. However, it applies
only to scann
Since installation of info files into a separate directory
(/usr/local/info/lilypond/), calling
info lilypond
no longer works. This is *very* bad. I use texinfo CVS version
2004-02-28.
Saying `info' alone gives the following menu entries:
* GNU LilyPond: (./lilypond/lilypond). The GNU
[CVS 2004-03-07 15:58 MET]
Compare /prallmordent with /upmordent: The vertical slash is
too short in the latter glyph.
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Mon, 01 Mar 2004 20:43:55 +0100, Nicolas a dit :
>> try #(top-repl)
> there is a place for an emacs command that would launch that, with I/Os in a
> buffer with ilisp-mode or so, which would enable symbol completion...
The following command definition should do it (requires ilisp):
(defun
Hi,
are there any reasons to restrict identifiers in LilyPond to contain only
letters? IMO, it would be nice to at least also allow digits. That would
make it easier to write large pieces by defining small chuncs of music:
Part1Voice1 = \notes {...}
Part1Voice2 = \notes {...}
...
At least for a
Dear proofreaders,
I have just committed some documentation file shuffling patches to
CVS, so if you are making corrections, please make a diff, and reapply
the changes to current CVS HEAD.
Thanks!
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_
On Sat, Mar 06, 2004 at 12:44:13AM +0100, Matthias Kilian wrote:
> introducing "exotic" dependencies like makeinfo CVS, there should be
> also workarounds that make LilyPond (and it's documenation) compile with
> standard versions (i.e. good-old makeinfo-4.5 or 4.6).
Please forget what I wrote. Us
