Re: Invisible notes, Scheme contexts

[Mats Bengtsson]

Why not approach the problem the other way around and modify the
frontend of LilyPond so that
\command "string"
is always treated internally as
\command #"string"

I think this provides a cleaner solution, at least for the end user.

  /Mats

> > I wonder whether this should be changed too. This would mean that
> >
> >   \clef alto
> >   \clef "alto"
> >
> > becomes
> >
> >   \clef #"alto"
> >
> > or
> >
> >   \clef #'alto
> >
> > This will simplify the syntax a bit, at the expense ease of entry.
> >
> > What do you think?
> >    
>
> I think that would be good. One of the confusing things with lilypond
> is the mixture of context properties, grob properties, builtin commands
> and scheme functions, etc... In this particular case, alto is clearly a
> symbol and should be written 'alto in scheme and thus #'alto in
> lilypond, imo.
>