Re: can the leading \markup command be eliminated in a new markup command?

Hi David, > Don't be too fast. I've created > […] > So you can replace the definition > > cue = > #(define-event-function (text) (markup?) > #{ ^\markup \bold #text #}) > > with > > cue = ^\markup \bold \etc YES! I tried that first (before my original post), and it didn’t work. Thank you so

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi David, > >> You either define an event function or a markup command. […] >> One is the markup, the other is a text script post event. Markups can >> be used in a variety of circumstances (as text scripts, as lyrics, as >> part of

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, > You either define an event function or a markup command. […] > One is the markup, the other is a text script post event. Markups can > be used in a variety of circumstances (as text scripts, as lyrics, as > part of other markup, as tempo strings, as mark texts and so on). Text >

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi David, > >>> Is there any technical reason not to make *every* markup function work >>> like this? >> >> There are markup commands and event functions and they are in different >> name spaces. > > Sorry for pushing for more

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, >> Is there any technical reason not to make *every* markup function work >> like this? > > There are markup commands and event functions and they are in different > name spaces. Sorry for pushing for more clarity/understanding, but: is it [in terms of behaviour] that the

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi David, > >> %%% SNIPPET BEGINS >> \version "2.19.80" >> >> cue = >> #(define-event-function (text) (markup?) >> #{ ^\markup \bold #text #}) >> >> { c''\cue "This is the cue." } >> %%% SNIPPET ENDS >> >> If you don't want to bake

Re: can the leading \markup command be eliminated in a new markup command?

Hi David, > %%% SNIPPET BEGINS > \version "2.19.80" > > cue = > #(define-event-function (text) (markup?) > #{ ^\markup \bold #text #}) > > { c''\cue "This is the cue." } > %%% SNIPPET ENDS > > If you don't want to bake the direction in, use - instead of ^ . Thanks for that! Is there any

Re: can the leading \markup command be eliminated in a new markup command?

Kieren MacMillan writes: > Hi all, > > Sorry if this is a silly question… but can this function be modified such > that the user can use > > { c''^\cue #"This is the cue." } > > instead of > > { c''^\markup \cue #"This is the cue." } > %%% SNIPPET BEGINS

can the leading \markup command be eliminated in a new markup command?

Hi all, Sorry if this is a silly question… but can this function be modified such that the user can use { c''^\cue #"This is the cue." } instead of { c''^\markup \cue #"This is the cue." } ?? Thanks, Kieren. %%% SNIPPET BEGINS \version "2.19.80" #(define-markup-command (cue