Werner:
> > I have been using this trick to avoid these awkward English
> > numerals...  (/verse.1/ instead of /verseOne/, /verse.2/, etc.)  but
> > never tried this more sophisticated use.
> > 
> > verse.1 = {...} — used as \verse.1
> > 
> > It does create a single variable which refers to a structured Lisp
> > object (an object with multiple slots), instead of distinct
> > variables, but for the user, this does not change anything in the
> > syntax itself.
> > 
> > Unfortunately, this feature is very hard to find in the
> > documentation.  It would be nice to give this information in the
> > main page explaining the syntax of variable names.
> 
> Where in the NR would you expect such documentation?  Could you maybe
> write something that I can add?

A suitable place might be after line 605 in
Documentation/en/notation/input.itely. An additional
paragraph before "@end itemize" could be the place.

Current wording is:

///////////
@cindex variable
A variable, such as
@example
foo = @{ c4 d e d @}
@end example

This can be used later on in the file by entering @code{\foo}.
The name of a variable should not contain (ASCII) numbers,
multiple underscores, multiple dashes or space characters.
All other characters Unicode provides are allowed, for example
Latin, Greek, Chinese or Cyrillic.  Non-adjacent single
underscores and dashes are allowed, too.
In other words, variable names like @code{HornIII} or
@code{???XII} work.

Any combination of characters is allowed if the variable name
is enclosed in double quotation marks.  In this case backslashes
and double quotation marks need to be escaped with
backslashes (not that you actually should use them).
Examples: @code{"foo bar"}, @code{"a-b-c"}, @code{"Horn 3"}.

@end itemize

The following example shows three things that may be entered at
top level.

@example
\layout @{
  % Don't justify the output
  ragged-right = ##t
@}

\header @{
   title = "Do-re-mi"
@}

@{ c'4 d' e2 @}
@end example


At any point in a file, any of the following lexical instructions can
be entered:
///////////

Regards,
/Karl Hammar



Reply via email to