Re: Outliner markup command

2016-01-17 Thread Paul Morris
applying newly defined `uncolor-stencil' > Also adding `outliner'-markup-command This looks like a good solution to me. Thanks for looking into it and coming up with a fix! That recursive map function is especially nice. For the name of the markup command, I’d like to suggest \outli

Re: Outliner markup command

2016-01-16 Thread Pierre Perol-Schneider
tencil '(-1 . 1) '(-1 . 1))) >> > >> > \markup { >> > \stencil #my-box-stil >> > \stencil #(stencil-with-color my-box-stil green) >> > \stencil #(stencil-with-color (stencil-with-color my-box-stil green) >> red) >> >

Re: Outliner markup command

2016-01-16 Thread Pierre Perol-Schneider
l > > \stencil #(stencil-with-color my-box-stil green) > > \stencil #(stencil-with-color (stencil-with-color my-box-stil green) > red) > > } > > > > Thinking about it, I came to the conclusion it's desired behaviour. > > Otherwise the following wouldn&

Re: Outliner markup command

2016-01-15 Thread Thomas Morley
ox-stil green) > \stencil #(stencil-with-color (stencil-with-color my-box-stil green) red) > } > > Thinking about it, I came to the conclusion it's desired behaviour. > Otherwise the following wouldn't work: > > \markup \with-color #red { foo \with-color #green bar

Re: Outliner markup command

2016-01-13 Thread Thomas Morley
2016-01-13 16:17 GMT+01:00 Paul Morris : >> On Jan 12, 2016, at 6:09 PM, Thomas Morley wrote: >> >> Though, there might be a bug in `stencil-whiteout-outline', Paul cc-ed. >> >> Look at: >> >> \markup \stencil >> #(stencil-whiteout-outline >> (make-filled-box-stencil '(-1 . 1) '(-1 . 1)) >> 0.5

Re: Outliner markup command

2016-01-13 Thread Pierre Perol-Schneider
Thank you Simon for this clear explanation. Pierre 2016-01-13 20:17 GMT+01:00 Simon Albrecht : > On 13.01.2016 13:24, Pierre Perol-Schneider wrote: > >> Hi David, >> >> 2016-01-12 23:52 GMT+01:00 David Kastrup mailto:d...@gnu.org >> >>: >> >> \override #`(color . ,red) >> >> And yes, I us

Re: Outliner markup command

2016-01-13 Thread Simon Albrecht
On 13.01.2016 13:24, Pierre Perol-Schneider wrote: Hi David, 2016-01-12 23:52 GMT+01:00 David Kastrup >: \override #`(color . ,red) And yes, I use a backward tick here. The forward tick will not cooperate with the comma later. I'm not sure to clearly unders

Re: Outliner markup command

2016-01-13 Thread Paul Morris
> On Jan 12, 2016, at 6:09 PM, Thomas Morley wrote: > > Though, there might be a bug in `stencil-whiteout-outline', Paul cc-ed. > > Look at: > > \markup \stencil > #(stencil-whiteout-outline > (make-filled-box-stencil '(-1 . 1) '(-1 . 1)) > 0.5 > red > 16 > 1) > > \markup \stencil > #(ste

Re: Outliner markup command

2016-01-13 Thread Paul Morris
> On Jan 13, 2016, at 7:45 AM, David Kastrup wrote: > > This is the correct version of the \override #'(color . red) you wrote > which does not work. Whether the above works depends on whether the > following markup actually uses the color property, of course. Indeed, the “\whiteout" markup com

Re: Outliner markup command

2016-01-13 Thread Pierre Perol-Schneider
OK thanks David. 2016-01-13 13:45 GMT+01:00 David Kastrup : > Pierre Perol-Schneider writes: > > > Hi David, > > > > 2016-01-12 23:52 GMT+01:00 David Kastrup : > > > > > >> \override #`(color . ,red) > >> > >> And yes, I use a backward tick here. The forward tick will not > >> cooperate with th

Re: Outliner markup command

2016-01-13 Thread David Kastrup
Pierre Perol-Schneider writes: > Hi David, > > 2016-01-12 23:52 GMT+01:00 David Kastrup : > > >> \override #`(color . ,red) >> >> And yes, I use a backward tick here. The forward tick will not >> cooperate with the comma later. >> > > I'm not sure to clearly understand what I can do here but i'l

Re: Outliner markup command

2016-01-13 Thread Pierre Perol-Schneider
Hi David, 2016-01-12 23:52 GMT+01:00 David Kastrup : > \override #`(color . ,red) > > And yes, I use a backward tick here. The forward tick will not > cooperate with the comma later. > I'm not sure to clearly understand what I can do here but i'll investigate anyhow. Thanks for the tip. Pierre

Re: Outliner markup command

2016-01-13 Thread Pierre Perol-Schneider
Hi Harm, 2016-01-13 0:09 GMT+01:00 Thomas Morley : > You can't hope a markup-command will accept an override for a > property, if said property isn't declared in any way. > Well, I thought it *was *declared since the code description says : "This function works by creating a series of white or

Re: Outliner markup command

2016-01-12 Thread Simon Albrecht
On 13.01.2016 00:09, Thomas Morley wrote: Though, there might be a bug in `stencil-whiteout-outline', Paul cc-ed. Here you are. Look at: \markup \stencil #(stencil-whiteout-outline (make-filled-box-stencil '(-1 . 1) '(-1 . 1)) 0.5 red 16 1) \markup \stencil #(stencil-whiteou

Re: Outliner markup command

2016-01-12 Thread Thomas Morley
2016-01-12 23:05 GMT+01:00 Pierre Perol-Schneider : > Hi Harm, > > 2016-01-12 21:24 GMT+01:00 Thomas Morley : > >> >> I've always found it a little so-so, to define custom markup-commands >> only combining a personal choice of preexisting markup-commands. > > > I fully agree, it's just that my sche

Re: Outliner markup command

2016-01-12 Thread David Kastrup
Thomas Morley writes: > Wow, that was fast. The change was trivial. It's the ramifications that aren't. That's why I would rather leave them to you. There will be odd cases rather certainly. The question is whether the overall behavior appears sensible and that's probably easier to judge emp

Re: Outliner markup command

2016-01-12 Thread David Kastrup
Pierre Perol-Schneider writes: > Hi Harm, > > 2016-01-12 21:24 GMT+01:00 Thomas Morley : > > >> I've always found it a little so-so, to define custom markup-commands >> only combining a personal choice of preexisting markup-commands. >> > > I fully agree, it's just that my scheme knowledge is als

Re: Outliner markup command

2016-01-12 Thread Pierre Perol-Schneider
2016-01-12 21:35 GMT+01:00 Thomas Morley : > You can already put it into LSR: comment out the code, let a > dummy-markup displayed and add [needs LSR upgrade] to the title. It > will then be stored in the unapproved snippets, not searchable, > though. > Yep that was my intention as soon as I'll

Re: Outliner markup command

2016-01-12 Thread Pierre Perol-Schneider
Hi Harm, 2016-01-12 21:24 GMT+01:00 Thomas Morley : > I've always found it a little so-so, to define custom markup-commands > only combining a personal choice of preexisting markup-commands. > I fully agree, it's just that my scheme knowledge is also a little so-so ;) Actually I tried to. Witho

Re: Outliner markup command

2016-01-12 Thread Pierre Perol-Schneider
Hi Simon, 2016-01-12 20:46 GMT+01:00 Simon Albrecht : > Nice idea! You needn’t quote the strings, and #"orange" is at least a > little less convoluted. > Yep ! Ok. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/list

Re: Outliner markup command

2016-01-12 Thread Thomas Morley
2016-01-12 22:08 GMT+01:00 David Kastrup : > Thomas Morley writes: > >> 2016-01-12 15:37 GMT+01:00 Pierre Perol-Schneider >> : >> >> I've always found it a little so-so, to define custom markup-commands >> only combining a personal choice of preexisting markup-commands. >> Wouldn't it be better to

Re: Outliner markup command

2016-01-12 Thread David Kastrup
Thomas Morley writes: > Any chance to directly insert the result of a scheme-function in a > newly created markup? Tracker issue: 4741 (https://sourceforge.net/p/testlilyissues/issues/4741/) Rietveld issue: 285070043 (https://codereview.appspot.com/285070043) Issue description: Allow Scheme fu

Re: Outliner markup command

2016-01-12 Thread David Kastrup
David Kastrup writes: > Thomas Morley writes: > >> Any chance to directly insert the result of a scheme-function in a >> newly created markup? > > I've just written a syntax rule allowing that, with the arguments of the > scheme function being scanned in \notemode. Which is what they are > usua

Re: Outliner markup command

2016-01-12 Thread David Kastrup
Thomas Morley writes: > 2016-01-12 15:37 GMT+01:00 Pierre Perol-Schneider > : > > I've always found it a little so-so, to define custom markup-commands > only combining a personal choice of preexisting markup-commands. > Wouldn't it be better to let it do by a scheme-function? > Though, you can't

Re: Outliner markup command

2016-01-12 Thread Thomas Morley
2016-01-12 18:40 GMT+01:00 Pierre Perol-Schneider : > Hi Trevor, > > Thank you. > Yes, I'll add a snippet for sure, as soon as LSR will work with v2.20. > > Pierre > > 2016-01-12 16:42 GMT+01:00 Trevor Daniels : >> >> Hi Pierre >> >> Very nice! Ideal for those more light-hearted musical items. >>

Re: Outliner markup command

2016-01-12 Thread Thomas Morley
2016-01-12 15:37 GMT+01:00 Pierre Perol-Schneider : > Hi, > > Yesterday night I thought about rewriting this snippet: > http://lsr.di.unimi.it/LSR/Item?id=890 using the new whiteout 'outline' > override and finally discovered a funny side effect: > > \version "2.19.35" > #(set-default-paper-size "a

Re: Outliner markup command

2016-01-12 Thread Simon Albrecht
On 12.01.2016 15:37, Pierre Perol-Schneider wrote: \header { title = \markup\outliner #3 #'"orange" #'"yellow" { Some Music } } Nice idea! You needn’t quote the strings, and #"orange" is at least a little less convoluted. Yours, Simon ___ lilyp

Re: Outliner markup command

2016-01-12 Thread Pierre Perol-Schneider
inal Message - > *From:* Pierre Perol-Schneider > *To:* lilypond-user > *Sent:* Tuesday, January 12, 2016 2:37 PM > *Subject:* Outliner markup command > > Hi, > > Yesterday night I thought about rewriting this snippet: > http://lsr.di.unimi.it/LSR/Item?id=890 using

Re: Outliner markup command

2016-01-12 Thread Trevor Daniels
Hi Pierre Very nice! Ideal for those more light-hearted musical items. LSR? Trevor - Original Message - From: Pierre Perol-Schneider To: lilypond-user Sent: Tuesday, January 12, 2016 2:37 PM Subject: Outliner markup command Hi, Yesterday night I thought about

Outliner markup command

2016-01-12 Thread Pierre Perol-Schneider
Hi, Yesterday night I thought about rewriting this snippet: http://lsr.di.unimi.it/LSR/Item?id=890 using the new whiteout 'outline' override and finally discovered a funny side effect: \version "2.19.35" #(set-default-paper-size "a6") #(define-markup-command (outliner layout props outln-width ou