Karl Hammar <[EMAIL PROTECTED]> writes:
> Why not make a global.ly with:
> %clefae = { \clef "treble_8" }
> clefae = { \clef bass }
>
> And in the score you do something like Score.01.ly:
> ...
> \include "global.ly"
> \include "Music.01.ly"
> ...
>\new Lyrics \lyricsto vspAA \lspAA
>
> Mats Bengtsson <[EMAIL PROTECTED]> writes:
>
> >>>I see some cases where this would be clearly a win. Few weeks ago, a
> >>>singer asked me to change all alto clefs to treble clefs in a
> >>>voice+piano reduction score. Just redefining the \clef music function
> >>>would have made that really ea
Han-Wen Nienhuys writes:
> 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 th
Mats Bengtsson <[EMAIL PROTECTED]> writes:
>>>I see some cases where this would be clearly a win. Few weeks ago, a
>>>singer asked me to change all alto clefs to treble clefs in a
>>>voice+piano reduction score. Just redefining the \clef music function
>>>would have made that really easy and quick
I see some cases where this would be clearly a win. Few weeks ago, a
singer asked me to change all alto clefs to treble clefs in a
voice+piano reduction score. Just redefining the \clef music function
would have made that really easy and quick.
A query replace alto -> treble is probably
Nicolas Sceaux <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> > I wonder whether this should be changed too. This would mean that
> >
> >\clef alto
> >\clef "alto"
> >
> > becomes
> >
> >\clef #"alto"
> >
> > or
> >
> >\clef #'alto
> >
> > This will
Han-Wen Nienhuys writes:
> 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
On 12/13/05, Nicolas Sceaux <[EMAIL PROTECTED]> wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
>
> > I wonder whether this should be changed too. This would mean that
> >
> >\clef alto
> >\clef "alto"
> >
> > becomes
> >
> >\clef #"alto"
> >
> > or
> >
> >\clef #'alto
> >
> >
On Tuesday 13 December 2005 22.27, Nicolas Sceaux wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> > I wonder whether this should be changed too. This would mean that
> >
> >\clef alto
> >\clef "alto"
> >
> > becomes
> >
> >\clef #"alto"
> >
> > or
> >
> >\clef #'alto
> >
> >
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 woul
Please keep this discussion on the list.
this is fixed in any recent 2.7 release. I also comitted a bugfix for 2.6.
Don Blaheta wrote:
But these don't work, they just change the error message, which is now:
:1:40: error: syntax error, unexpected STRING_IDENTIFIER, expecting
LYRICS_STRING or
On Tue, 13 Dec 2005 12:59:00 +0100
Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> Erik Sandberg wrote:
> >>I can't figure out how to convert between Scheme strings and the
> >>lilypond-native things that look like strings but seem to be
> >>something else (often a LYRICS_STRING, though not in this
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> 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 th
Erik Sandberg wrote:
I can't figure out how to convert between Scheme strings and the
lilypond-native things that look like strings but seem to be something
else (often a LYRICS_STRING, though not in this case).
functions can only take scheme strings as parameters
(\bar and other commands aren
On Tuesday 13 December 2005 10.55, Don Blaheta wrote:
> Quoth Han-Wen Nienhuys:
> > Don Blaheta wrote:
> > > 2) Is there a Scheme function to retrieve the _current_ context? It
> > > looks like all the functions require a context as an argument.
> >
> > What do you mean by "current" ? Where do you
Don Blaheta wrote:
Quoth Han-Wen Nienhuys:
Don Blaheta wrote:
2) Is there a Scheme function to retrieve the _current_ context? It
looks like all the functions require a context as an argument.
What do you mean by "current" ? Where do you need it ?
The context that is enclosing the point
Quoth Han-Wen Nienhuys:
> Don Blaheta wrote:
> > 2) Is there a Scheme function to retrieve the _current_ context? It
> > looks like all the functions require a context as an argument.
>
> What do you mean by "current" ? Where do you need it ?
The context that is enclosing the point where the Sch
Don Blaheta wrote:
Two unrelated questions.
1) Is there anything I can make that is totally invisible, yet will
count as a note to hang a lyric on? s1 won't do because \lyricsto
ignores it as well.
2) Is there a Scheme function to retrieve the _current_ context? It
looks like all the function
Two unrelated questions.
1) Is there anything I can make that is totally invisible, yet will
count as a note to hang a lyric on? s1 won't do because \lyricsto
ignores it as well.
2) Is there a Scheme function to retrieve the _current_ context? It
looks like all the functions require a context a
19 matches
Mail list logo
