Re: accessing markup properties via \tweak?

2024-06-20 Thread Valentin Petzel
Am Donnerstag, 20. Juni 2024, 07:02:48 MESZ schrieb Werner LEMBERG: > Folks, > > > is it possible to access markup properties like `baseline-skip` via > \tweak? It is often necessary to define a markup command that gets in > turn wrapped into a music function, and for such situations a > tweak-l

Re: accessing markup properties via \tweak?

2024-06-20 Thread Werner LEMBERG
Hello David, >> is it possible to access markup properties like `baseline-skip` via >> \tweak? > > Have you tried? Well, yes, but ... > Check out the following example where I just add a few lines in > front of what you wrote: ... it didn't occur to me to go this route. Thanks a lot! Rega

Re: accessing markup properties via \tweak?

2024-06-20 Thread Werner LEMBERG
>> In the example below, I want to set the markup property `bar` as a >> tweak to influence `\foo`. > > you could of course do something like > > %%% > #(define-markup-command (foo-markup layout props) () >#:properties ((bar #f) (details '())) >(interpret-markup > layout props > #

Re: accessing markup properties via \tweak?

2024-06-20 Thread David Kastrup
Werner LEMBERG writes: > Hello David, > > >>> is it possible to access markup properties like `baseline-skip` via >>> \tweak? >> >> Have you tried? > > Well, yes, but ... > >> Check out the following example where I just add a few lines in >> front of what you wrote: > > ... it didn't occur to m

Re: accessing markup properties via \tweak?

2024-06-20 Thread Valentin Petzel
> > Ah, yes, I forgot that it is possible to extend the `props` alist. > Thanks a lot! > > > Werner This is not exactly extending the probs, but passing additional parameters in details. It would be great to generally have a grob property like grob.default-properties or something, and add

Re: accessing markup properties via \tweak?

2024-06-20 Thread Werner LEMBERG
>> Ah, yes, I forgot that it is possible to extend the `props` alist. >> Thanks a lot! > > This is not exactly extending the probs, but passing additional > parameters in details. Yep, I answered too quickly and was too lazy to correct myself :-) > It would be great to generally have a grob pr

LSR typo: plz correct

2024-06-20 Thread Simon Albrecht
Hello everyone, I’m hoping to address someone with the necessary privileges to edit the title of LSR snippet 1017: s/there/their https://lsr.di.unimi.it/LSR/Item?id=1017 Thanks in advance Simon

Re: LSR typo: plz correct

2024-06-20 Thread Jean Abou Samra
> I’m hoping to address someone with the necessary privileges to edit the > title of LSR snippet 1017: s/there/their > > https://lsr.di.unimi.it/LSR/Item?id=1017 Done signature.asc Description: This is a digitally signed message part

Re: LSR typo: plz correct

2024-06-20 Thread Simon Albrecht
On 20.06.24 14:41, Jean Abou Samra wrote: Done Thanks!

RE: re-use a melody by removing

2024-06-20 Thread peter--- via LilyPond user discussion
Greetings, Thank you, Kieren and Simon. When I created a minimal sample, I used a poor example and the two easy solutions you suggested would be perfect. I REALLY want to be able to re-use a melody while selectively altering parts of it. Here are two more possibilities --

Re: re-use a melody by removing

2024-06-20 Thread Kieren MacMillan
Hi Peter, > I REALLY want to be able to re-use a melody while selectively altering parts > of it. I think you should consider using tags: %%% SNIPPET BEGINS \version "2.24.3" melody = { c'2 -\tag #'violin -\downbow g'2 -\tag #'violin -\upbow es'2. d'4 | c' es' d' c' | b d' g2 } { \

RE: re-use a melody by removing

2024-06-20 Thread peter--- via LilyPond user discussion
Tags! is the solution I was looking for. I don't know whether I appreciate more: -- Lilypond -- or the community I find here. They're both wonderful. Thank you. I will read the manual 3.4.2. I will read the manual. LSR = The LilyPond Snippet Repository (LSR) https://lilypond.org/doc/v2.

Re: re-use a melody by removing

2024-06-20 Thread Simon Albrecht
On 20.06.24 19:31, Kieren MacMillan wrote: turning a melody in a minor key into a major key. There’s a function out there somewhere to do that — search the LSR, etc. Depending on what you’re trying to do it might be worth using tags for this as well. Unless of course you’re going to need this

Adjust line spacing in markup column for fingerings

2024-06-20 Thread Fennel
Hi all, Getting this behavior when trying to put fingerings in column format on chords: \version "2.24.3" \relative c'' { \set fingeringOrientations = #'(left) } I’d like the 1 to be much closer to the 2. Does anyone know the correct property to adjust to make this happen / where in the docs

Re: Adjust line spacing in markup column for fingerings

2024-06-20 Thread Curt McDowell
baseline-skip seems to do the job: || Found here: LilyPond snippets: Tweaks and overrides Regards, Curt On 6/20/2024 5:00 PM, Fennel wrote: Hi all, Getting this behavior when trying to put fingerings in column form

Re: re-use a melody by removing

2024-06-20 Thread Kieren MacMillan
Hi Simon, > Depending on what you’re trying to do it might be worth using tags for this > as well. Unless of course you’re going to need this transformation a lot. I was thinking about tags, but hating the concept… Found this, which seems like it might do the trick (though Jean probably has a