lilypond-devel
[Top][All Lists]
Advanced

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

Re: Documentation fix for markup keywords.


From: Mark Polesky
Subject: Re: Documentation fix for markup keywords.
Date: Sat, 17 Apr 2010 10:13:12 -0700 (PDT)

David Kastrup wrote:
> lilypond --eval '(top-repl)' /dev/null
> guile> (help markup-command-keyword)

Ah, I remember seeing this discussed on the mailing list,
but it looks like this exact approach is not mentioned in
the docs (and it should IMO).  Probably in CG 9.6 "Debugging
LilyPond", and perhaps a tiny reference to it in AU 1.2
"Command-line usage".

Also, I see you've shortened --evaluate to --eval.  This
isn't commonly allowed, is it?  Is that a bug in the build
process?  I mean, lilypond allows this type of thing:

$ lilypond --versio

while other programs are stricter with such abbreviations.
For example, both bash and gimp have a `--version' option,
but neither will accept `--versio'.  I assume this is hardly
worth addressing (is it?), but if nothing else, you should
keep to the standard options if you document this.  Besides,
in this case you can use `-e', which is even shorter than
`--eval'.  Feel free to respond to this specific topic with
a renamed subject header.

- Mark


      




reply via email to

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