Re: Policy for posts from non-members

[Mark Knoop]

At 23:36 on 21 Feb 2023, Jean Abou Samra wrote:
> Hi,

> I've not been an admin of this list for very long, yet I'm already
> weary of telling people who post without being subscribed to the list
> that they should subscribe in order to avoid each of their messages
> being manually approved. I wonder what you (meaning everyone, but
> especially Mark, the other admin) would think about changing the list
> configuration to reject post from non-members instead of holding them
> on moderation, with a message such as

> “Welcome to the lilypond-user mailing list. We apologize, but in order
> to prevent spam, we need you to subscribe to the list before you post.
> Please fill out the subscription form on
> [https://lists.gnu.org/mailman/listinfo/lilypond-user](https://lists.gnu.org/mailman/listinfo/lilypond-user).

> Once you are subscribed, you will receive all posts to the list, so
> you can help out other people as well. However, if you only wish to
> interact with this list infrequently, you may disable mail
> subscription in your membership preferences after you have subscribed.

> If you believe you are already subscribed to the list, it probably
> means that you accidentally posted from a different email address than
> the one you are subscribed with.

> If you have any question or encounter problems, feel free to contact
> the list admins at lilypond-user-ow...@gnu.org”

> On the plus side, this means that instead of delaying the message
> until Mark or me looks at it, the feedback will come instantly.

> Jean

Thanks Jean, I support this proposal.


--
Mark Knoop

Re: Policy for posts from non-members

[Werner LEMBERG]

> And joining is actually pretty serious friction for some people - the
> more lists I join, the more likely I am to abandon attempts to help if
> I'm required to register.

I second that concern.  Being the maintainer of the FreeType mailing
lists, I face exactly the same problem.  Usually, I simply enable
messages in the queue.  If I have to do this too often, I tell people
to subscribe.

It seems, however, that the amount of new users is much larger for
LilyPond than for FreeType...

> That said, I'm very sympathetic to wanting people to join.

Yes, joining is a *must* in the long run.  Only this guarantees spam
protection (not always, but in most cases).


Werner

Re: Policy for posts from non-members

[Andrew Bernard]

Wording is perfect.

Andrew


On 22/02/2023 9:36 am, Jean Abou Samra wrote:


“Welcome to the lilypond-user mailing list. We apologize, but in order 
to prevent spam, we need you to subscribe to the list before you post. 
Please fill out the subscription form on 
https://lists.gnu.org/mailman/listinfo/lilypond-user.


...

Re: Policy for posts from non-members

[Abraham Lee]

On Tue, Feb 21, 2023 at 7:57 PM Ralph Palmer 
wrote:

>
>
> On Tue, Feb 21, 2023, 2:37 PM Jean Abou Samra  wrote:
>
>> Hi,
>>
>>
>> “Welcome to the lilypond-user mailing list. We apologize, but in order to
>> prevent spam, we need you to subscribe to the list before you post. Please
>> fill out the subscription form on
>> https://lists.gnu.org/mailman/listinfo/lilypond-user.
>>
>> Once you are subscribed, you will receive all posts to the list, so you
>> can help out other people as well. However, if you only wish to interact
>> with this list infrequently, you may disable mail subscription in your
>> membership preferences after you have subscribed.
>>
>> If you believe you are already subscribed to the list, it probably means
>> that you accidentally posted from a different email address than the one
>> you are subscribed with.
>>
>> If you have any question or encounter problems, feel free to contact the
>> list admins at lilypond-user-ow...@gnu.org”
>>
>> On the plus side, this means that instead of delaying the message until
>> Mark or me looks at it, the feedback will come instantly.
>>
>> Jean
>>
>> This sounds appropriate to me, Jean.
> Ralph
>

I second this. Very respectfully and instructively worded. This should
definitely take some load off your plate.

Best,
Abraham

>

Re: Policy for posts from non-members

[Ralph Palmer]

On Tue, Feb 21, 2023, 2:37 PM Jean Abou Samra  wrote:

> Hi,
>
>
> “Welcome to the lilypond-user mailing list. We apologize, but in order to
> prevent spam, we need you to subscribe to the list before you post. Please
> fill out the subscription form on
> https://lists.gnu.org/mailman/listinfo/lilypond-user.
>
> Once you are subscribed, you will receive all posts to the list, so you
> can help out other people as well. However, if you only wish to interact
> with this list infrequently, you may disable mail subscription in your
> membership preferences after you have subscribed.
>
> If you believe you are already subscribed to the list, it probably means
> that you accidentally posted from a different email address than the one
> you are subscribed with.
>
> If you have any question or encounter problems, feel free to contact the
> list admins at lilypond-user-ow...@gnu.org”
>
> On the plus side, this means that instead of delaying the message until
> Mark or me looks at it, the feedback will come instantly.
>
> Jean
>
> This sounds appropriate to me, Jean.
Ralph

>
>

Re: Policy for posts from non-members

[Andrew Bernard]

Hi Wols,

After my post I was just waiting for you to chime in with that. :-) :-)

As to friction, I think it's just that most people are just simply 
unaware, rather than having ideological issues (the latter is _not_ 
directed at you).


All the best from Down Under!

Andrew Bernard

On 22/02/2023 10:50 am, Wol wrote:

On 21/02/2023 23:20, Andrew Bernard wrote:
[Of course the moment I post people will provide proof of lists that 
do not need joining, but seriously, most lists do. Also, services 
such as Reddit require registration. It's a very basic concept.]


:-) I believe pretty much all kernel.org lists don't require joining.

Re: Policy for posts from non-members

[Wol]

On 21/02/2023 23:20, Andrew Bernard wrote:
[Of course the moment I post people will provide proof of lists that do 
not need joining, but seriously, most lists do. Also, services such as 
Reddit require registration. It's a very basic concept.]


:-) I believe pretty much all kernel.org lists don't require joining.

And joining is actually pretty serious friction for some people - the 
more lists I join, the more likely I am to abandon attempts to help if 
I'm required to register.


That said, I'm very sympathetic to wanting people to join.

Certainly an automated response saying "you'll get a quicker response if 
you subscribe", but I'm not sure whether forcing people to subscribe is 
a good idea.


(Like I've seen plenty of lists ruined by aggressively trying to prevent 
off-topic posts - all too often the unintended consequence is the loss 
of on-topic posts too ...)


Cheers,
Wol

Re: Policy for posts from non-members

[William Rehwinkel]

I think this is a good idea, and I would pick either silently rejecting 
unsubscribed messages or automatically replying with the message that 
Jean wrote (both options would happen automatically with no admin input 
to be clear). Even though mailing lists have been around for a long 
time, as others have posted here, so you would expect newcomers to know 
the expectation to subscribe, I think that as the years go by there are 
more and more people who are not familiar with how mailing lists 
operate, such as younger people who are more used to things like 
discord, google groups or other social media.



On 2/21/23 17:36, Jean Abou Samra wrote:

Hi,

I've not been an admin of this list for very long, yet I'm already weary 
of telling people who post without being subscribed to the list that 
they should subscribe in order to avoid each of their messages being 
manually approved. I wonder what you (meaning everyone, but especially 
Mark, the other admin) would think about changing the list configuration 
to reject post from non-members instead of holding them on moderation, 
with a message such as


“Welcome to the lilypond-user mailing list. We apologize, but in order 
to prevent spam, we need you to subscribe to the list before you post. 
Please fill out the subscription form on 
https://lists.gnu.org/mailman/listinfo/lilypond-user 
.


Once you are subscribed, you will receive all posts to the list, so you 
can help out other people as well. However, if you only wish to interact 
with this list infrequently, you may disable mail subscription in your 
membership preferences after you have subscribed.


If you believe you are already subscribed to the list, it probably means 
that you accidentally posted from a different email address than the one 
you are subscribed with.


If you have any question or encounter problems, feel free to contact the 
list admins at lilypond-user-ow...@gnu.org”


On the plus side, this means that instead of delaying the message until 
Mark or me looks at it, the feedback will come instantly.


Jean



--
+ -- +
|William Rehwinkel - Oberlin College and |
|   Conservatory '24 |
|  will...@williamrehwinkel.net  |
| PGP key:   |
| https://williamrehwinkel.net/static/pubkey.txt |
+ -- +


OpenPGP_signature
Description: OpenPGP digital signature

Re: Policy for posts from non-members

[Jean Abou Samra]

Le mardi 21 février 2023 à 23:54 +0100, David Kastrup a écrit :
> Maybe it's possible to prepare a stock message that you just need to  
> checkmark?  That would go a long way towards being less weary.  A  
> different tradeoff.


Personally, I'm a bit uneasy with sending canned responses as
if they were newly written. If I'm sending similar replies, I
might as well do that automatically.

The disadvantage is that the newcomer maybe doesn't have the feeling of
being individually cared for by a human person if it's an automatic response.
I would usually write a word of welcome when replying to a question from a 
newcomer,
though.


signature.asc
Description: This is a digitally signed message part

Re: Policy for posts from non-members

[Andrew Bernard]

Dear me, mailing lists have been around for half as century or more. If 
people do not understand that it is normal to subscribe to a list to 
participate there's something wrong. Just reject the posts. That's very 
standard, and that is why the list software supports that option. Jean 
you already spend a huge amount of time helping people on the list, the 
administrivia of dealing with people who can't be bothered to spend a 
minute to sign up is not worth your time. If you don't make this change 
you will just be doing this useless task forever.


[Of course the moment I post people will provide proof of lists that do 
not need joining, but seriously, most lists do. Also, services such as 
Reddit require registration. It's a very basic concept.]


Andrew


On 22/02/2023 9:36 am, Jean Abou Samra wrote:


Hi,

I've not been an admin of this list for very long, yet I'm already 
weary of telling people who post without being subscribed to the list 
that they should subscribe in order to avoid each of their messages 
being manually approved.

Re: Policy for posts from non-members

[David Kastrup]

Jean Abou Samra  writes:

> Hi,
>
> I've not been an admin of this list for very long, yet I'm already
> weary of telling people who post without being subscribed to the list
> that they should subscribe in order to avoid each of their messages
> being manually approved.

Maybe it's possible to prepare a stock message that you just need to
checkmark?  That would go a long way towards being less weary.  A
different tradeoff.

-- 
David Kastrup

Re: Policy for posts from non-members

[Jean Abou Samra]

Le mardi 21 février 2023 à 14:46 -0800, Mark Stephen Mrotek a écrit :
> Jean Abou Samra,  
>    
> Why am I mentioned in your e-mail?  
> Thank you for your kind attention. 

You're not :-) The Mark being mentioned is Mark Knoop.

Best,

Jean


signature.asc
Description: This is a digitally signed message part

RE: Policy for posts from non-members

[Mark Stephen Mrotek]

Jean Abou Samra,

 

Why am I mentioned in your e-mail?

Thank you for your kind attention.

 

Mark

 

From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Jean 
Abou Samra
Sent: Tuesday, February 21, 2023 2:36 PM
To: lilypond-user 
Cc: mark 
Subject: Policy for posts from non-members

 

Hi,

I've not been an admin of this list for very long, yet I'm already weary of 
telling people who post without being subscribed to the list that they should 
subscribe in order to avoid each of their messages being manually approved. I 
wonder what you (meaning everyone, but especially Mark, the other admin) would 
think about changing the list configuration to reject post from non-members 
instead of holding them on moderation, with a message such as

“Welcome to the lilypond-user mailing list. We apologize, but in order to 
prevent spam, we need you to subscribe to the list before you post. Please fill 
out the subscription form on 
https://lists.gnu.org/mailman/listinfo/lilypond-user.

Once you are subscribed, you will receive all posts to the list, so you can 
help out other people as well. However, if you only wish to interact with this 
list infrequently, you may disable mail subscription in your membership 
preferences after you have subscribed.

If you believe you are already subscribed to the list, it probably means that 
you accidentally posted from a different email address than the one you are 
subscribed with.

If you have any question or encounter problems, feel free to contact the list 
admins at lilypond-user-ow...@gnu.org  ”

On the plus side, this means that instead of delaying the message until Mark or 
me looks at it, the feedback will come instantly.

Jean

Re: Policy for posts from non-members

[David M. Boothe, CAS]

That's a common sense approach. And your auto-reply is very courteous.

dB

On Tue, Feb 21, 2023, 5:37 PM Jean Abou Samra  wrote:

> Hi,
>
> I've not been an admin of this list for very long, yet I'm already weary
> of telling people who post without being subscribed to the list that they
> should subscribe in order to avoid each of their messages being manually
> approved. I wonder what you (meaning everyone, but especially Mark, the
> other admin) would think about changing the list configuration to reject
> post from non-members instead of holding them on moderation, with a message
> such as
>
> “Welcome to the lilypond-user mailing list. We apologize, but in order to
> prevent spam, we need you to subscribe to the list before you post. Please
> fill out the subscription form on
> https://lists.gnu.org/mailman/listinfo/lilypond-user.
>
> Once you are subscribed, you will receive all posts to the list, so you
> can help out other people as well. However, if you only wish to interact
> with this list infrequently, you may disable mail subscription in your
> membership preferences after you have subscribed.
>
> If you believe you are already subscribed to the list, it probably means
> that you accidentally posted from a different email address than the one
> you are subscribed with.
>
> If you have any question or encounter problems, feel free to contact the
> list admins at lilypond-user-ow...@gnu.org”
>
> On the plus side, this means that instead of delaying the message until
> Mark or me looks at it, the feedback will come instantly.
>
> Jean
>

Policy for posts from non-members

[Jean Abou Samra]

Hi,

I've not been an admin of this list for very long, yet I'm already weary of 
telling people who post without being subscribed to the list that they should 
subscribe in order to avoid each of their messages being manually approved. I 
wonder what you (meaning everyone, but especially Mark, the other admin) would 
think about changing the list configuration to reject post from non-members 
instead of holding them on moderation, with a message such as

“Welcome to the lilypond-user mailing list. We apologize, but in order to 
prevent spam, we need you to subscribe to the list before you post. Please fill 
out the subscription form on 
[https://lists.gnu.org/mailman/listinfo/lilypond-user](https://lists.gnu.org/mailman/listinfo/lilypond-user).

Once you are subscribed, you will receive all posts to the list, so you can 
help out other people as well. However, if you only wish to interact with this 
list infrequently, you may disable mail subscription in your membership 
preferences after you have subscribed.

If you believe you are already subscribed to the list, it probably means that 
you accidentally posted from a different email address than the one you are 
subscribed with.

If you have any question or encounter problems, feel free to contact the list 
admins at lilypond-user-ow...@gnu.org”

On the plus side, this means that instead of delaying the message until Mark or 
me looks at it, the feedback will come instantly.

Jean


signature.asc
Description: This is a digitally signed message part

RE: spurious second treble clef sign, what did I do wrong this time?

[Mark Stephen Mrotek]

Kenneth,

1) Move Tempo to rh_one;
2) Change all "grace" to "acciaccatura".
See attachment.

Mark

-Original Message-
From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org 
[mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of 
Kenneth Wolcott
Sent: Tuesday, February 21, 2023 12:34 PM
To: Leo Correia de Verdier 
Cc: Lily Pond 
Subject: Re: spurious second treble clef sign, what did I do wrong this time?

Hi Leo;

  Thanks again for your help.

  I have the "\grace s8." now in all three of the voices that do not have the 
"\acciaccatura", yet the problem persists.

  I'm not sure how I would insert the "\grace s8." into my \global variable.  
I'm sure that is obvious, but I don't grok it.

  I have attached my current Lilypond source, pdf output from Lilypond and the 
original pdf file.

Thanks,
Ken

On Tue, Feb 21, 2023 at 1:36 AM Leo Correia de Verdier 
 wrote:
>
> Now that I am at the computer and have seen the .ly file I would recommend 
> having them in the \global variable. (As you inferred, but just to be clear 
> for anyone else reading this thread, it should be \grace s8. in my first mail 
> in this thread).
>
> > 21 feb. 2023 kl. 10:03 skrev Leo Correia de Verdier 
> > :
> >
> > It’s needed in any voice that contains a \clef \time , \mark or anything 
> > such.
> >
> >> 21 feb. 2023 kl. 08:58 skrev Kenneth Wolcott :
> >>
> >> Thank you, Leo.
> >>
> >> I already had "\grace {s16*3} s1" in the second lh voice, 
> >> apparently needed in the the second rh voice?
> >>
> >> Thanks,
> >> Ken
> >>
> >>> On Mon, Feb 20, 2023 at 11:42 PM Leo Correia de Verdier 
> >>>  wrote:
> >>>
> >>> I haven’t been able to open your  .ly file since   I’m on the telephone, 
> >>> but that should be an issue 34. Add s8. right after the clef and time 
> >>> signature in the right hand, so that the grace note timing matches 
> >>> between the different staves and voices and the extra clefs and time 
> >>> signatures will disappear.
> >>>
> >>> HTH
> >>> /Leo
> >>>
> > 21 feb. 2023 kl. 08:33 skrev Kenneth Wolcott :
> 
>  Hi;
> 
>  I'm engraving a piece of music arranged for Piano that (later) 
>  has polyphony in the right hand and left hand.
> 
>  This is Lilypond 2.24.1 on MacOS.
> 
>  There is a spurious second treble clef (and spurious time 
>  signature) in the first bar of the right hand (upper) staff.
> 
>  What am I doing wrong that causes this?
> 
>  I am attaching the example pdf which I am engraving from, my 
>  Lilypond source and the pdf Lilypond creates.
> 
>  Thanks,
>  Ken Wolcott
>  
>  
>  
>
\version "2.24.1"

% Tchaikovsky: Marche Slave

\header {
  title = "Marche Slave"
  composer = "Tchaikovsky"
  arranger = "from 8notes.com"
}

global = {
  \language "english"
  \time 4/4
  \key c \major
  
}

\paper {
  ragged-last-bottom = ##f
  markup-system-spacing.padding = 3
}

\layout {
  system-count = 4
}

% mBreak = { \break }
mBreak = { }

rh_one = {
  \global
  \clef treble
  \tempo "Moderato in modo di marcia funebre"
  \acciaccatura { s8. } R1  | % m01
  R1  | % m02
  R1  | % m03
  R1  | % m04
  e'2 ds'4(c'8 b)| % m05

  \bar "|."
}

rh_two = {
  \global
  \clef treble
  \acciaccatura { s8. } s1  | % m01
  s1  | % m02
  s1  | % m03

  \bar "|."
}

piano_dynamics = {
  \global
  s8\pp s2. s8  | % m01
  s1| % m02
  s1| % m03
  s1| % m04
  s1| % m05

}

lh_one = {
  \global
  \clef bass
  \acciaccatura { e,16 fs, gs, } \repeat tremolo 8 { a,32 a,, }  a,8 r r4  | % m01
  \acciaccatura { e,16 fs, gs, } \repeat tremolo 8 { a,32 a,, }  a,8 r r4  | % m02
  \acciaccatura { e,16 fs, gs, } 4 q q q   | % m03
  \acciaccatura { e,16 fs, gs, } 4 q q q   | % m04
  4 q | % m05

  \bar "|."
}

lh_two = {
  \global
  \clef bass
  \acciaccatura { s8. } s1  | % m01
  s1  | % m02
  s1  | % m03
  s1  | % m04
  s1 | % m05

  \bar "|."
}

\score {
  \new PianoStaff \with { instrumentName = "Piano" } <<
\new Staff <<
  \new Voice = "1" { \voiceOne \rh_one }
  \new Voice = "2" { \voiceTwo \rh_two }
>>
\new Dynamics \piano_dynamics
\new Staff <<
  \new Voice = "1" { \voiceOne \lh_one }
  \new Voice = "2" { \voiceTwo \lh_two }
>>
  >>
  \layout {}
}

\score {
  <<
\new Staff <<
  \set Staff.midiInstrument = "acoustic grand"
  \set Staff.midiExpression=#0.6
  \new Voice = "1" { \voiceOne \rh_one }
  \new Voice = "2" { \voiceTwo \rh_two }
>>
\new Dynamics \piano_dynamics
\new Staff <<
  \set Staff.midiInstrument = "acoustic grand"
  \set Staff.midiExpression=#0.6
  \new Voice = "1" { \voiceOne \lh_one }
  \new Voice = "2" { \voiceTwo \lh_two }
>>
  >>
  \midi {
\tempo 4=110
  }
}

Re: spurious second treble clef sign, what did I do wrong this time?

[Kenneth Wolcott]

Ah!!! Got it.

Thanks to you all.

Ken

On Tue, Feb 21, 2023 at 12:52 PM Mats Bengtsson
 wrote:
>
>
> On 2023-02-21 21:33, Kenneth Wolcott wrote:
>
> Hi Leo;
>
>   Thanks again for your help.
>
>   I have the "\grace s8." now in all three of the voices that do not
> have the "\acciaccatura", yet the problem persists.
>
>   I'm not sure how I would insert the "\grace s8." into my \global
> variable.  I'm sure that is obvious, but I don't grok it.
>
>   I have attached my current Lilypond source, pdf output from Lilypond
> and the original pdf file.
>
> Thanks,
> Ken
>
> If you look carefully, you will see that it's no longer the clef, but the 
> time signature that's duplicated. The reason is that you have included the 
> time signature setting in your \global variable and that you have included 
> the \global variable into your \piano_dynamics variable, without a matching 
> \grace{s8.}. Since there's no reason to include \global in \piano_dynamics, 
> it's easiest to simply remove it there. Otherwise add \grace {s8.} there as 
> well.
>
>/Mats

Re: spurious second treble clef sign, what did I do wrong this time?

[Mats Bengtsson]

  
  


On 2023-02-21 21:33, Kenneth Wolcott
  wrote:


  Hi Leo;

  Thanks again for your help.

  I have the "\grace s8." now in all three of the voices that do not
have the "\acciaccatura", yet the problem persists.

  I'm not sure how I would insert the "\grace s8." into my \global
variable.  I'm sure that is obvious, but I don't grok it.

  I have attached my current Lilypond source, pdf output from Lilypond
and the original pdf file.

Thanks,
Ken


If you look carefully, you will see that it's no longer the clef,
  but the time signature that's duplicated. The reason is that you
  have included the time signature setting in your \global variable
  and that you have included the \global variable into your
  \piano_dynamics variable, without a matching \grace{s8.}. Since
  there's no reason to include \global in \piano_dynamics, it's
  easiest to simply remove it there. Otherwise add \grace {s8.}
  there as well. 

   /Mats

  

Re: move chords closer to notes

[Jean Abou Samra]

Le mardi 21 février 2023 à 14:01 +0100, mi...@orbelanet.com a écrit :
> Oh, I'm so sorry!
> 
> My problem is not relationed with lilypond directly.
> 
> Is just a neovim mapping problem with .ly files, that convert cc to cis  
> (to easyly write sharps and flats).

Instead of that, you probably want to do something like

```
\version "2.24.0"

#(ly:parser-set-note-names
  `((c . ,#{ c #})
(cc . ,#{ cis #})
(d . ,#{ d #})
;; etc...
;; add all notes in your notation
))

\fixed c' {
  c cc d
}
```

to define your own input language.


signature.asc
Description: This is a digitally signed message part

Re: swing eighths in

[Jean Abou Samra]

Le mardi 21 février 2023 à 10:10 -0800, Donald J. Stewart a écrit :
> I'd like to set something similar to 'eighth note = triplet' (attached tempo  
> marking)
> 
> I see 'Beat Change' under Directives -> Markings -> Tempi and Metronome marks
> 
> But for some reason I get an 'unable to typeset' warning when I attempt to 
> use  
> this.
> 
> I'm sure there's a simple solution that I'm just overlooking...



Hello,

So you know, your message was manually approved because you are not a list 
subscriber. Please fix this by subscribing on 
https://lists.gnu.org/mailman/listinfo/lilypond-user (you may choose not to 
receive list messages). Thanks.

I'm not sure what editor you are using. An editor will merely help you to 
insert common commands, but no editor knows about every possible LilyPond 
command.

If you search for “swing” in LilyPond's [documentation 
index](https://lilypond.org/doc/v2.24/Documentation/notation/lilypond-index.html),
 you will land on the description of the `\rhythm` command, with an example 
that looks pretty much like your picture.

Regards,

Jean


signature.asc
Description: This is a digitally signed message part

swing eighths in

[Donald J. Stewart]

I'd like to set something similar to 'eighth note = triplet' (attached tempo 
marking)

I see 'Beat Change' under Directives -> Markings -> Tempi and Metronome marks

But for some reason I get an 'unable to typeset' warning when I attempt to use 
this.

I'm sure there's a simple solution that I'm just overlooking...


_
D on aldJ S  t   e wa   rt
   s ou   n  d-  X

Re: change format of bookOutputSuffix

[Mark Knoop]

At 09:36 on 21 Feb 2023, Kieren MacMillan wrote:
> Hi all,

> What’s the simplest way to modify the format of \bookOutputSuffix? For
> example, say I want the trailing hyphen to be an underscore — i.e.,
> currently I get

>   MyPiece-suffix.pdf

> and I want

>   MyPiece_suffix.pdf

> Do I have to [locate and] rebuild the music function, or is there an
> easy parameter I don’t know about?

It seems to be hard-coded in the function get-outfile-name (lily-library.scm).

--
Mark Knoop

Re: change format of bookOutputSuffix

[Kieren MacMillan]

Hi Jean,

> It's coded in get-outfile-name in scm/lily-library.scm. It doesn't provide an 
> easy knob to change the separator, and set!-ing an internal function would be 
> really icky (subject to breaking without replacement in future versions). I 
> think the best way is to just use \bookOutputName "MyPiece_suffix" without a 
> \bookOutputSuffix at all.

I feared that might be the answer!
Thanks… that’s what I’ve been doing, so I’ll just continue with that.

Best,
Kieren.

Re: change format of bookOutputSuffix

[Jean Abou Samra]

Le mardi 21 février 2023 à 09:36 -0500, Kieren MacMillan a écrit :
> Hi all,
> 
> What’s the simplest way to modify the format of \bookOutputSuffix? For 
> example, say I want the trailing hyphen to be an underscore — i.e., currently 
> I get
> 
>   MyPiece-suffix.pdf
> 
> and I want
> 
>   MyPiece_suffix.pdf
> 
> Do I have to [locate and] rebuild the music function, or is there an easy 
> parameter I don’t know about?


It's coded in `get-outfile-name` in `scm/lily-library.scm`. It doesn't provide 
an easy knob to change the separator, and `set!`-ing an internal function would 
be really icky (subject to breaking without replacement in future versions). I 
think the best way is to just use `\bookOutputName "MyPiece_suffix"` without a 
`\bookOutputSuffix` at all.


signature.asc
Description: This is a digitally signed message part

change format of bookOutputSuffix

[Kieren MacMillan]

Hi all, 

What’s the simplest way to modify the format of \bookOutputSuffix? For example, 
say I want the trailing hyphen to be an underscore — i.e., currently I get

  MyPiece-suffix.pdf

and I want

  MyPiece_suffix.pdf

Do I have to [locate and] rebuild the music function, or is there an easy 
parameter I don’t know about?

Thanks!
Kieren.

Re: move chords closer to notes

[mikel]

Oh, I'm so sorry!

My problem is not relationed with lilypond directly.

Is just a neovim mapping problem with .ly files, that convert cc to cis 
(to easyly write sharps and flats). Then when a compile next line:

\accepts ChordNames
is modified in:
 \acisepts ChordNames

and compilation break off!

I solve it and now work like I want.

Thanks very mutch for your time!

El 2023-02-21 13:43, Jean Abou Samra escribió:

Le mardi 21 février 2023 à 13:35 +0100, mi...@orbelanet.com a écrit
:


Yes, sorry, I see the typo just now.

My lilypond version is 2.24.0.


Did you really compile the snippet unmodified, or did you insert it in
the context of a larger score?

Re: move chords closer to notes

[Jean Abou Samra]

Le mardi 21 février 2023 à 13:35 +0100, mi...@orbelanet.com a écrit :
> Yes, sorry, I see the typo just now.
> 
> My lilypond version is 2.24.0.


Did you really compile the snippet unmodified, or did you insert it in the 
context of a larger score?


signature.asc
Description: This is a digitally signed message part

Re: move chords closer to notes

[mikel]

Yes, sorry, I see the typo just now.

My lilypond version is 2.24.0.

El 2023-02-21 13:13, Jean Abou Samra escribió:

Le mardi 21 février 2023 à 13:03 +0100, Jean Abou Samra a écrit :


Le mardi 21 février 2023 à 12:41 +0100, mi...@orbelanet.com a
écrit :


Thanks a lot for your response! It looks good in the image you
sent, but for some reason it doesn't work
for me.The next line does not allow me to compile the file, it
does not
accept it:
\remove Axis_group_engraver


(Resend, I got bounces from the list, not sure why.)


Well, you had a typo in the list address (“llilypond”) so your
message above didn't reach the list either.

What version are you using?

Re: move chords closer to notes

[Jean Abou Samra]

Le mardi 21 février 2023 à 13:03 +0100, Jean Abou Samra a écrit :
> Le mardi 21 février 2023 à 12:41 +0100, mi...@orbelanet.com a écrit :
> 
> > Thanks a lot for your response!
> > It looks good in the image you sent, but for some reason it doesn't work  
> > for me.The next line does not allow me to compile the file, it does not  
> > accept it:  
> >    \remove Axis_group_engraver
> 
> 
> (Resend, I got bounces from the list, not sure why.)


Well, you had a typo in the list address (“llilypond”) so your message above 
didn't reach the list either.

What version are you using?



signature.asc
Description: This is a digitally signed message part

Re: spurious second treble clef sign, what did I do wrong this time?

[Leo Correia de Verdier]

Now that I am at the computer and have seen the .ly file I would recommend 
having them in the \global variable. (As you inferred, but just to be clear for 
anyone else reading this thread, it should be \grace s8. in my first mail in 
this thread).

> 21 feb. 2023 kl. 10:03 skrev Leo Correia de Verdier 
> :
> 
> It’s needed in any voice that contains a \clef \time , \mark or anything 
> such. 
> 
>> 21 feb. 2023 kl. 08:58 skrev Kenneth Wolcott :
>> 
>> Thank you, Leo.
>> 
>> I already had "\grace {s16*3} s1" in the second lh voice, apparently
>> needed in the the second rh voice?
>> 
>> Thanks,
>> Ken
>> 
>>> On Mon, Feb 20, 2023 at 11:42 PM Leo Correia de Verdier
>>>  wrote:
>>> 
>>> I haven’t been able to open your  .ly file since   I’m on the telephone, 
>>> but that should be an issue 34. Add s8. right after the clef and time 
>>> signature in the right hand, so that the grace note timing matches between 
>>> the different staves and voices and the extra clefs and time signatures 
>>> will disappear.
>>> 
>>> HTH
>>> /Leo
>>> 
> 21 feb. 2023 kl. 08:33 skrev Kenneth Wolcott :
 
 Hi;
 
 I'm engraving a piece of music arranged for Piano that (later) has
 polyphony in the right hand and left hand.
 
 This is Lilypond 2.24.1 on MacOS.
 
 There is a spurious second treble clef (and spurious time signature)
 in the first bar of the right hand (upper) staff.
 
 What am I doing wrong that causes this?
 
 I am attaching the example pdf which I am engraving from, my
 Lilypond source and the pdf Lilypond creates.
 
 Thanks,
 Ken Wolcott
 
 
 

Re: spurious second treble clef sign, what did I do wrong this time?

[Leo Correia de Verdier]

It’s needed in any voice that contains a \clef \time , \mark or anything such. 

> 21 feb. 2023 kl. 08:58 skrev Kenneth Wolcott :
> 
> Thank you, Leo.
> 
> I already had "\grace {s16*3} s1" in the second lh voice, apparently
> needed in the the second rh voice?
> 
> Thanks,
> Ken
> 
>> On Mon, Feb 20, 2023 at 11:42 PM Leo Correia de Verdier
>>  wrote:
>> 
>> I haven’t been able to open your  .ly file since   I’m on the telephone, but 
>> that should be an issue 34. Add s8. right after the clef and time signature 
>> in the right hand, so that the grace note timing matches between the 
>> different staves and voices and the extra clefs and time signatures will 
>> disappear.
>> 
>> HTH
>> /Leo
>> 
 21 feb. 2023 kl. 08:33 skrev Kenneth Wolcott :
>>> 
>>> Hi;
>>> 
>>> I'm engraving a piece of music arranged for Piano that (later) has
>>> polyphony in the right hand and left hand.
>>> 
>>> This is Lilypond 2.24.1 on MacOS.
>>> 
>>> There is a spurious second treble clef (and spurious time signature)
>>> in the first bar of the right hand (upper) staff.
>>> 
>>> What am I doing wrong that causes this?
>>> 
>>> I am attaching the example pdf which I am engraving from, my
>>> Lilypond source and the pdf Lilypond creates.
>>> 
>>> Thanks,
>>> Ken Wolcott
>>> 
>>> 
>>>