Graham Percival wrote Wednesday, May 14, 2008 6:40 AM
Is it worth fussing with spaces in @code? I'm thinking of things
like @code{\include "english.ly"}.
Yes, I think it is.
I tried making a @longcode{} which does @[EMAIL PROTECTED], but that fell
afoul of the inconsistent backslash-in-macros texinfo problem. (\
is fine for pdf, but \\ is required for html output)
Writing @[EMAIL PROTECTED] "english.ly"} would solve that
problem, but at this point I started to wonder if I was obsessing
too much over small details. :|
Another solution is just to include @w{} in the list of commands
for doc helpers, and encourage people to write @[EMAIL PROTECTED]
lilypond command with arguments}}.
I'd go for this solution. We have to use @w{} occasionally in
other circumstances anyway. Not sure it's worth doing this every
time though - it's bad enough in some text to have to place @code{}
everywhere. Might be better to do this only if the command
would otherwise split - ie leave it for one of the last tiding
up actions after all the text is in place (if we ever reach that
point :)
Cheers,
- Graham
Trevor
_______________________________________________
lilypond-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
