Re: Chord glissTweak padding

[David Kastrup]

Aaron Hill  writes:

> On 2020-11-02 12:18 pm, Aaron Hill wrote:
>>   #{ \once \override Glissando.after-line-breaking = #proc
>>  <>\glissando #})
>
> You can even simplify that expression using \tweak:
>
>   #{ <>-\tweak after-line-breaking #proc \glissando #}
>
> Not sure if \tweak is cheaper than \once \override.

The bulk of the price of \tweak is prepaid due to the cost of the
Tweak_engraver being mostly independent of actual use.

The significant advantage of \tweak is that its effect is constrained to
the construct in question rather than the timestep in question.  That
makes unexpected side effects much less likely.

-- 
David Kastrup

Re: The Guide to getting Point and Click going with Gvim under Ubuntu 18

[David Wright]

On Mon 02 Nov 2020 at 09:59:45 (+0100), Martín Rincón Botero wrote:

> […] Out of curiosity, do Mac and Windows users have to stick to Frescobaldi 
> for Point & Click? They’re not even mentioned in the Usage Manual.

The code in the footnote of my reply to Andrew implies that, in the
absence of a *EDITOR environment variable, the Windows platform
chooses lilypad, and any other platform chooses emacs. That would
suggest that P works on them too.

> > Debian 10/buster with Xpdf and emacs running on a 2000-vintage
> > Pentium III at 650MHz in 512MB memory took less than a second to
> > open the source at the first click, and thereafter serviced each
> > click in 0.5 secs, just so long as the new target position is in
> > the displayed window
> 
> Wow, that’s old hardware! In my Asus laptop from 2017, Atom takes a while to 
> open the first time. After that, each click takes around 0.5 secs or less I 
> would say. It’s not something of great concern to me, but it’s noticeable, 
> especially after being used to Frescobaldi’s immediate reposition of the 
> cursor. Perhaps it has to do with Atom (not the lightest editor around). Were 
> Atom not so pleasing to the eye, I would probably try with another one to 
> compare speed ;-).

I'm guessing that there are three places where a delay could occur,
and on linux it should be easy to distinguish them. With two xterms,
I started gvim on one (and you'd use atom):

$ strace -f gvim

and on the other I started Xpdf:

$ LYEDITOR=gvim strace -f xpdf my-grand-opera.pdf

When the dust settles, you should see an outpouring of text on
each xterm when the moused is moved over either window.

So hold the mouse steady over a note, then click the button slowly,
and you should see more text appear with ButtonDown and more again
with ButtonUp. As far as P is concerned, it's ButtonUp that's
important, so the first delay is in how fast your finger twitches.¹

So to see where the delay is occurring, move the xterms close
together, then hold the button down over a note and, when all
activitiy has ceased, release it. You can see roughly how long
the communication takes by how quickly atom's xterm reacts
after xpdf's xterm.

Similarly, you can move atom and its xterm close together, and
observe the time difference between atom's xterm reacting and
its cursor moving. With 0.5 secs delay, you should be able to
resolve that somewhere in the chain.

If the delay is between the two xterms' output, I would guess
that changing editor won't make much difference.

¹ I can cheat here, as I have the PrintScreen key defined as a
  25 msec left button press, which is faster than I can click
  with the mouse.

Cheers,
David.

Re: how to give more horizontal space to the voice follower

[Jean Abou Samra]

Le 02/11/2020 à 20:16, Werner LEMBERG a écrit :

Looking up the e-mail archive for 'lilypond-devel' I couldn't find
relevant info.  Do you have a link?

Have a look at
https://lilypond.org/doc/v2.21/Documentation/notation/spanners.fr.html

Apparently some spacing calculations need to be triggeredby hand.

Well, that's exactly the point: I can't find any technical reasoning
for that.  While it certainly is a special case for beams to adjust
the minimum length, other grobs like voice follower lines or
glissandos almost always need it.


Absolutely; I just wanted to make sure you were aware that this
quirk was documented.

Cheers,
Jean

Re: Chord glissTweak padding

[Aaron Hill]

On 2020-11-02 12:18 pm, Aaron Hill wrote:

  #{ \once \override Glissando.after-line-breaking = #proc
 <>\glissando #})


You can even simplify that expression using \tweak:

  #{ <>-\tweak after-line-breaking #proc \glissando #}

Not sure if \tweak is cheaper than \once \override.


-- Aaron Hill

Re: Chord glissTweak padding

[Aaron Hill]

On 2020-11-02 12:18 pm, Aaron Hill wrote:
\glissTweak needs to be able to handle using 
ly:grob-set-nested-property!:



glissTweak =
#(define-music-function
  (parser location lst) (pair?)
  (define (proc grob)
(let ((gliss-count (ly:grob-property grob 'glissando-index)))
  (for-each
   (lambda (x)
 (let ((gliss-nmbr (car x))
   (property-value-alist (cdr x)))
   (if (eq? gliss-nmbr gliss-count)
   (for-each
(lambda (y)
  (let ((prop (car y)) (val (cdr y)))
(or (list? prop) (set! prop (list prop)))
(ly:grob-set-nested-property! grob prop val)))
property-value-alist
   lst)))
  #{ \once \override Glissando.after-line-breaking = #proc
 <>\glissando #})



Hmm... that could be cleaned up to remove the outer loop:


glissTweak =
#(define-music-function
  (parser location lst) (pair?)
  (define (proc grob)
(let ((gliss-idx (ly:grob-property grob 'glissando-index)))
  (for-each
   (lambda (y)
 (let ((prop (car y)) (val (cdr y)))
   (or (list? prop) (set! prop (list prop)))
   (ly:grob-set-nested-property! grob prop val)))
   (ly:assoc-get gliss-idx lst '()
  #{ \once \override Glissando.after-line-breaking = #proc
 <>\glissando #})



-- Aaron Hill

Re: Chord glissTweak padding

[Aaron Hill]

On 2020-11-02 11:48 am, Dimitris Marinakis wrote:
Is it possible to modify this tweak to include padding (left & right) 
for

the individual gliss lines?

[...]


\glissTweak needs to be able to handle using 
ly:grob-set-nested-property!:



glissTweak =
#(define-music-function
  (parser location lst) (pair?)
  (define (proc grob)
(let ((gliss-count (ly:grob-property grob 'glissando-index)))
  (for-each
   (lambda (x)
 (let ((gliss-nmbr (car x))
   (property-value-alist (cdr x)))
   (if (eq? gliss-nmbr gliss-count)
   (for-each
(lambda (y)
  (let ((prop (car y)) (val (cdr y)))
(or (list? prop) (set! prop (list prop)))
(ly:grob-set-nested-property! grob prop val)))
property-value-alist
   lst)))
  #{ \once \override Glissando.after-line-breaking = #proc
 <>\glissando #})


Then you can do something like this:


\glissTweak
  #`((0 . ((style . dashed-line)
  ((bound-details right padding) . 2)
  ((bound-details right arrow) . #t)
  (normalized-endpoints . (0 . -2.1
 (1 . ((stencil . #f)))
 (2 . ((stencil . #f)))
 (3 . ((stencil . #f)))
 (4 . ((style . dashed-line)
   ((bound-details left padding) . 2)
   ((bound-details left arrow) . #t)
   (normalized-endpoints . (0 . -1.5)
2^"\"some other tweaks\""




-- Aaron Hill

Re: how to give more horizontal space to the voice follower

[Thomas Morley]

Am Mo., 2. Nov. 2020 um 18:06 Uhr schrieb Werner LEMBERG :
>
>
> >> >>   \override VoiceFollower.springs-and-rods = 
> >> >> #ly:spanner::set-spacing-rods
> >>
> >> In case there aren't serious reasons against doing it I suggest to
> >> change the default; I would also prepare a patch.
> >
> > I vaguely remember having #ly:spanner::set-spacing-rods the default
> > caused problems with spacing/line-breaks in some cases.
>
> Looking up the e-mail archive for 'lilypond-devel' I couldn't find
> relevant info.  Do you have a link?

Nope, I noticed the problem with a private coding.
Though, I can't remember exactly.

Sorry,
  Harm

Chord glissTweak padding

[Dimitris Marinakis]

Is it possible to modify this tweak to include padding (left & right) for
the individual gliss lines?

#(define (radians->degree radians)
  (/ (* radians 180) PI))

#(define ((gliss-plus-text padding text) grob)
  (let* ((text-stencil (grob-interpret-markup grob text))
 (spanner-stencil (ly:line-spanner::print grob))
 (left-bound-info (ly:grob-property grob 'left-bound-info))
 (y-left (cdar left-bound-info))
 (right-bound-info (ly:grob-property grob 'right-bound-info))
 (y-right (cdar right-bound-info))
 (slant (if (> y-right y-left) 1 -1))
 (spanner-stencil-x-length
(interval-length (ly:stencil-extent spanner-stencil X)))
 (spanner-stencil-y-length
(interval-length (ly:stencil-extent spanner-stencil Y)))
 (alpha
(radians->degree
  (atan (/ spanner-stencil-y-length
spanner-stencil-x-length
 (spanner-center-X
(interval-center (ly:stencil-extent spanner-stencil X)))
 (label-center-X (interval-center (ly:stencil-extent text-stencil
X
  (ly:stencil-combine-at-edge
spanner-stencil
Y UP
(ly:stencil-translate
  (ly:stencil-rotate text-stencil (* slant alpha) 0 0)
  (cons (- spanner-center-X label-center-X) 0))
(+ (* -0.5 spanner-stencil-y-length) padding

glissTweak =
#(define-music-function (parser location lst)(pair?)
#{
   \once \override Glissando #'after-line-breaking =
  #(lambda (grob)
(let ((gliss-count (ly:grob-property grob 'glissando-index)))
(map (lambda (x)
  (let ((gliss-nmbr (car x))
(property-value-alist (cdr x)))
(if (eq? gliss-nmbr gliss-count)
  (map
(lambda (y) (ly:grob-set-property! grob (car y) (cdr
y)))
property-value-alist)
  #f)))
; $lst))) % for Version "2.14.2"
  lst)))
   $(make-music 'EventChord 'elements (list (make-music
'GlissandoEvent)))
#})

tweakedGliss = {
\once \override Glissando #'minimum-length = #8
\once \override Glissando #'springs-and-rods =
  #ly:spanner::set-spacing-rods
}

\relative c' {
\override TextScript #'font-size = #-2

2\glissando^"\"no tweaks\""


\tweakedGliss
\glissTweak
  #`((0 . ((color . ,red)
   (normalized-endpoints . (0 . 0.8))
   (stencil . ,(gliss-plus-text -1.8
 (markup #:italic #:fontsize -8
"gliss.")
 (1 . ((style . zigzag)))
 (2 . ((style . trill)
   (color . (0.5 0.5 0.5
 (3 . ((style . dashed-line)))
 (4 . ((stencil . ,(gliss-plus-text 0
 (markup #:italic #:fontsize -8 "gliss.")))
   (normalized-endpoints . (0 . 2.7))
   (color . ,green
2^"\"some tweaks\""


\once \override Glissando #'(bound-details right arrow) = ##t
\glissTweak
  #`((0 . ((style . dashed-line)
   (normalized-endpoints . (0 . -2.1
 (1 . ((stencil . #f)))
 (2 . ((stencil . #f)))
 (3 . ((stencil . #f)))
 (4 . ((style . dashed-line)
   (normalized-endpoints . (0 . -1.5)
2^"\"some other tweaks\""


}

Re: how to give more horizontal space to the voice follower

[Werner LEMBERG]

>> Looking up the e-mail archive for 'lilypond-devel' I couldn't find
>> relevant info.  Do you have a link?
>
> Have a look at
> https://lilypond.org/doc/v2.21/Documentation/notation/spanners.fr.html
> 
> Apparently some spacing calculations need to be triggeredby hand.

Well, that's exactly the point: I can't find any technical reasoning
for that.  While it certainly is a special case for beams to adjust
the minimum length, other grobs like voice follower lines or
glissandos almost always need it.


Werner

Re: how to give more horizontal space to the voice follower

[Jean Abou Samra]

Looking up the e-mail archive for 'lilypond-devel' I couldn't find
relevant info.  Do you have a link?

Have a look at 
https://lilypond.org/doc/v2.21/Documentation/notation/spanners.fr.html


Apparently some spacing calculations need to be triggeredby hand.

Jean

Re: how to give more horizontal space to the voice follower

[Werner LEMBERG]

>> >>   \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods
>>
>> In case there aren't serious reasons against doing it I suggest to
>> change the default; I would also prepare a patch.
> 
> I vaguely remember having #ly:spanner::set-spacing-rods the default
> caused problems with spacing/line-breaks in some cases.

Looking up the e-mail archive for 'lilypond-devel' I couldn't find
relevant info.  Do you have a link?

> I'd test very thoroughly.

Yeah, it's seems that one or more regression tests would be necessary.


Werner

Re: piece starting with acciaccatura problem

[jh]

Thanks you, I thought I remembered that this had come up before but 
didn't remember a solution.  THis is easy enough to execute.  Thank you 
for the timely response.

Jay

On 2020-11-02 09:32, Lukas-Fabian Moser wrote:

Hi,

Am 02.11.20 um 17:18 schrieb jh:
here's my small example of the problem I think it's been addressed 
before but have no idea how to find the solution.  Please give me a 
link or clue to find how to defeat this.  Jay


That's LilyPond's most famous bug: If a piece starts with grace notes,
they have to be in all voices (and of the same length). Otherwise,
funny things of the sort you experienced will happen.

So, add \grace s8. in the left hand right after \clef bass. (You can
also try to insert it _before_ the \clef; the resulting change might
make it clear what's going on here.)

Lukas

Re: piece starting with acciaccatura problem

[Lukas-Fabian Moser]

Hi,

Am 02.11.20 um 17:18 schrieb jh:
here's my small example of the problem I think it's been addressed 
before but have no idea how to find the solution.  Please give me a 
link or clue to find how to defeat this.  Jay


That's LilyPond's most famous bug: If a piece starts with grace notes, 
they have to be in all voices (and of the same length). Otherwise, funny 
things of the sort you experienced will happen.


So, add \grace s8. in the left hand right after \clef bass. (You can 
also try to insert it _before_ the \clef; the resulting change might 
make it clear what's going on here.)


Lukas

piece starting with acciaccatura problem

[jh]

here's my small example of the problem I think it's been addressed 
before but have no idea how to find the solution.  Please give me a link 
or clue to find how to defeat this.  Jay

\version "2.18.2"
\header {
  title = "31 Oct Hallows"
  composer = "Jay Hamilton"
copyright = \markup { \tiny \override #'(baseline-skip . 0.5)
\center-column
{  "CC lic 2.5 some rights reserved Jay Hamilton 2020"
"see http://creativecommons.org/licenses/by-nd/2.5/;
   } }
   }

  % }
#(ly:set-option 'delete-intermediate-files #t)
#(set-default-paper-size "letter" )
 #(set-global-staff-size 23)

  \paper
 {
  ragged-bottom = ##f and
  ragged-last-bottom = ##t
  indent = 15
  short-indent = 15
  right-margin = 30
  top-margin = 15
  bottom-margin = 15
 }
upper  = \relative c'{
\key c \major
\time 4/4 \tempo "largo" 4 = 48
 \accidentalStyle "forget"
\override Staff.TimeSignature #' style = #' ()
\override Score.BarNumber #'break-visibility = #end-of-line-invisible
\override BreathingSign #'font-size = #5
% \set Staff.instrumentName = #"Voice1"
% \set Staff.shortInstrumentName = #"V-1"
\clef treble
\acciaccatura {es'32 d es8}
d8 c bes16 g8. c8 bes a c
}
melody = \relative c{
\key c \major
\time 4/4
 \accidentalStyle "forget"
\override Staff.TimeSignature #' style = #' ()
\override Score.BarNumber #'break-visibility = #end-of-line-invisible
\override BreathingSign #'font-size = #5
% \set Staff.instrumentName = #"Voice1"
% \set Staff.shortInstrumentName = #"V-1"
\clef bass
2

}
\score {<<
\new Staff \upper
\new Staff \melody



\layout {
\context {
\Staff \RemoveEmptyStaves
}
 }
\midi {}
}

--
Thank you Sound & Silence POB 4833 Seattle, Wa 98194 206-328-7694
www.soundand.com

I am looking for 2-3 dancers various abilities/disciplines for a piece
Called The Box it was scheduled for November  but we know how that has
gone. However I am interested in making videos of the moves and having
dancers work on them and the music before we can get into the same
room... Paid rehearsals and the door divided evenly by participants.
Spread the word please.

31 Oct Hallows.pdf
Description: Adobe PDF document

Re: \bracketize?

[田村淳]

Hello Lukas and Harm,

> 2020/11/02 19:50、Thomas Morley のメール:
> 
> Am So., 1. Nov. 2020 um 16:58 Uhr schrieb Lukas-Fabian Moser :
>> 
>> Hi Jun,
>> 
>> Am 01.11.20 um 14:07 schrieb 田村淳:
>>> Hello,
>>> 
>>> I’m looking for a “bracket” version of “\parenthesize” function to
>>> enclose an articulation or ornamentation mark within a pair of square
>>> brackets. I’d like to use parenthesis and brackets to indicate two
>>> different types of editorial additions. I achieved the same for
>>> dynamics marks by slightly modifying the LSR code “Creating "real"
>>> parenthesized dynamics”
>>> http://lsr.di.unimi.it/LSR/Item?id=382
>>> http://lsr.di.unimi.it/LSR/Snippet?id=382
>>> Is there an easy way to create “\bracketize” function?
>>> 
>>> Thanks in advance and best regards.
>> 
>> It's not ideal since the X-extent is hardcoded, but as a starting point:
>> 
>> \version "2.20"
>> 
>> bracketify =
>>   \tweak ParenthesesItem.stencil #ly:text-interface::print
>>   \tweak ParenthesesItem.font-size -3.7
>>   \tweak ParenthesesItem.text \markup \general-align #Y #CENTER {
>> \hspace #0.6  \center-align \line { [ \hspace #1 ] } }
>>   \parenthesize \etc
>> 
>> \relative {
>>   c'4 \bracketify d \parenthesize e f
>>   e\bracketify --
>> }
>> 
>> Lukas
>> 
>> 
> 
> Here my own take:
> 
> #(define-public (parentheses-item::calc-bracket-stencils grob)
>  (let* ((parent (ly:grob-parent grob Y))
> (y-extent (ly:grob-extent parent parent Y))
> (details (ly:grob-property grob 'details))
> (thick (assoc-get 'bracket-thickness details 0.1))
> (bracket-vertical-padding
>   (assoc-get 'bracket-vertical-padding details 0.1))
> (bracket-protrusion
>   (assoc-get 'bracket-protrusion details 0.25))
> (pad-y-extent (interval-widen y-extent bracket-vertical-padding))
> (lp
>   (ly:stencil-aligned-to
> (ly:stencil-aligned-to
>   (ly:bracket Y pad-y-extent thick bracket-protrusion)
>   Y CENTER)
> X RIGHT))
> (rp
>   (ly:stencil-aligned-to
> (ly:stencil-aligned-to
>   (ly:bracket Y pad-y-extent thick (- bracket-protrusion))
>   Y CENTER)
> X LEFT)))
>(list lp rp)))
> 
> 
> bracketify =
>   \tweak ParenthesesItem.stencils #parentheses-item::calc-bracket-stencils
>   %% \tweak ParenthesesItem.padding #0
>   %% \tweak ParenthesesItem.details.bracket-vertical-padding #1
>   %% \tweak ParenthesesItem.details.bracket-thickness #1
>   %% \tweak ParenthesesItem.details.bracket-protrusion #0.5
>   \parenthesize \etc
> 
> \relative {
>   c'4 \bracketify d \parenthesize e f\bracketify -.
>   e\bracketify -\upbow
> }
> 
> Cheers,
>  Harm

Thanks for your snippets!

Harm’s snippet works great for me as I’ve been especially looking for a 
bracketified trill.

Thanks again and best regards,

Jun

#(define-public (parentheses-item::calc-bracket-stencils grob)
   (let* ((parent (ly:grob-parent grob Y))
  (y-extent (ly:grob-extent parent parent Y))
  (details (ly:grob-property grob 'details))
  (thick (assoc-get 'bracket-thickness details 0.1))
  (bracket-vertical-padding
   (assoc-get 'bracket-vertical-padding details 0.1))
  (bracket-protrusion
   (assoc-get 'bracket-protrusion details 0.25))
  (pad-y-extent (interval-widen y-extent bracket-vertical-padding))
  (lp
   (ly:stencil-aligned-to
(ly:stencil-aligned-to
 (ly:bracket Y pad-y-extent thick bracket-protrusion)
 Y CENTER)
X RIGHT))
  (rp
   (ly:stencil-aligned-to
(ly:stencil-aligned-to
 (ly:bracket Y pad-y-extent thick (- bracket-protrusion))
 Y CENTER)
X LEFT)))
 (list lp rp)))

bracketify =
\tweak ParenthesesItem.stencils #parentheses-item::calc-bracket-stencils
% \tweak ParenthesesItem.padding #0
% \tweak ParenthesesItem.details.bracket-vertical-padding #0
\tweak ParenthesesItem.details.bracket-thickness #0.2
% \tweak ParenthesesItem.details.bracket-protrusion #0.5
\parenthesize \etc

\relative {
  c'4 \bracketify d \parenthesize e f\bracketify -.
  e\bracketify -\upbow
  d\bracketify\trill
  c\bracketify\prall
  b\bracketify\turn
  a1\bracketify\fermata
}

Re: \bracketize?

[Thomas Morley]

Am So., 1. Nov. 2020 um 16:58 Uhr schrieb Lukas-Fabian Moser :
>
> Hi Jun,
>
> Am 01.11.20 um 14:07 schrieb 田村淳:
> > Hello,
> >
> > I’m looking for a “bracket” version of “\parenthesize” function to
> > enclose an articulation or ornamentation mark within a pair of square
> > brackets. I’d like to use parenthesis and brackets to indicate two
> > different types of editorial additions. I achieved the same for
> > dynamics marks by slightly modifying the LSR code “Creating "real"
> > parenthesized dynamics”
> > http://lsr.di.unimi.it/LSR/Item?id=382
> > http://lsr.di.unimi.it/LSR/Snippet?id=382
> > Is there an easy way to create “\bracketize” function?
> >
> > Thanks in advance and best regards.
>
> It's not ideal since the X-extent is hardcoded, but as a starting point:
>
> \version "2.20"
>
> bracketify =
>\tweak ParenthesesItem.stencil #ly:text-interface::print
>\tweak ParenthesesItem.font-size -3.7
>\tweak ParenthesesItem.text \markup \general-align #Y #CENTER {
>  \hspace #0.6  \center-align \line { [ \hspace #1 ] } }
>\parenthesize \etc
>
> \relative {
>c'4 \bracketify d \parenthesize e f
>e\bracketify --
> }
>
> Lukas
>
>

Here my own take:

#(define-public (parentheses-item::calc-bracket-stencils grob)
  (let* ((parent (ly:grob-parent grob Y))
 (y-extent (ly:grob-extent parent parent Y))
 (details (ly:grob-property grob 'details))
 (thick (assoc-get 'bracket-thickness details 0.1))
 (bracket-vertical-padding
   (assoc-get 'bracket-vertical-padding details 0.1))
 (bracket-protrusion
   (assoc-get 'bracket-protrusion details 0.25))
 (pad-y-extent (interval-widen y-extent bracket-vertical-padding))
 (lp
   (ly:stencil-aligned-to
 (ly:stencil-aligned-to
   (ly:bracket Y pad-y-extent thick bracket-protrusion)
   Y CENTER)
 X RIGHT))
 (rp
   (ly:stencil-aligned-to
 (ly:stencil-aligned-to
   (ly:bracket Y pad-y-extent thick (- bracket-protrusion))
   Y CENTER)
 X LEFT)))
(list lp rp)))


bracketify =
   \tweak ParenthesesItem.stencils #parentheses-item::calc-bracket-stencils
   %% \tweak ParenthesesItem.padding #0
   %% \tweak ParenthesesItem.details.bracket-vertical-padding #1
   %% \tweak ParenthesesItem.details.bracket-thickness #1
   %% \tweak ParenthesesItem.details.bracket-protrusion #0.5
   \parenthesize \etc

\relative {
   c'4 \bracketify d \parenthesize e f\bracketify -.
   e\bracketify -\upbow
}

Cheers,
  Harm

Re: LSR 1119 Force clef change in alternatives

[Thomas Morley]

Am Mo., 2. Nov. 2020 um 11:32 Uhr schrieb Pierre Perol-Schneider
:
>
> Done! Thanks for the reminder Harm.
> Cheers
> Pierre
>
> Le ven. 30 oct. 2020 à 22:19, Thomas Morley  a 
> écrit :
>>
>> To the author (Pierre?) of
>> lsr.di.unimi.it/LSR/Item?u=1=1119
>>
>> Many thanks for your snippet, though, please add a description to it. ;)
>>
>> Thanks,
>>   Harm
>>

Hi Pierre,

approved as
http://lsr.di.unimi.it/LSR/Item?id=1119
Should be searchable soon (likely tomorrow).

Thanks,
  Harm

Re: how to give more horizontal space to the voice follower

[Thomas Morley]

Am Mo., 2. Nov. 2020 um 10:21 Uhr schrieb Werner LEMBERG :
>
>
> >>> Why doesn't the `VoiceFollower` grob obey the `minimum-length`
> >>> property (inspite of supporting the `spanner-interface`)?  What am
> >>> I missing?
> >>
> >> add
> >>
> >>   \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods
>
> What's actually the reason to not have this set by default?  Ditto for
> glissando lines.  My experience is that it is almost always necessary
> increase the length of both grobs in real-world scores.
>
> In case there aren't serious reasons against doing it I suggest to
> change the default; I would also prepare a patch.
>
>
> Werner

I vaguely remember having #ly:spanner::set-spacing-rods the default
caused problems with spacing/line-breaks in some cases.
I'd test very thoroughly.

Cheers,
  Harm

Re: LSR 1119 Force clef change in alternatives

[Pierre Perol-Schneider]

 Ok Aaron.
Cheers,
Pierre

Le ven. 30 oct. 2020 à 23:45, Aaron Hill  a
écrit :

> On 2020-10-30 2:19 pm, Thomas Morley wrote:
> > To the author (Pierre?) of
> > lsr.di.unimi.it/LSR/Item?u=1=1119
> >
> > Many thanks for your snippet, though, please add a description to it.
> > ;)
>
> Would this work better to avoid the hidden note showing up in MIDI?
>
> 
>\grace s4
>\once \override Staff.Clef.extra-spacing-width = #'(-1 . 0)
>\clef bass
> 
>
> Seeing as the grace note affects spacing, I added a suitable spacing
> modifier.
>
>
>
> -- Aaron Hill
>
>

Re: LSR 1119 Force clef change in alternatives

[Pierre Perol-Schneider]

Done! Thanks for the reminder Harm.
Cheers
Pierre

Le ven. 30 oct. 2020 à 22:19, Thomas Morley  a
écrit :

> To the author (Pierre?) of
> lsr.di.unimi.it/LSR/Item?u=1=1119
>
> Many thanks for your snippet, though, please add a description to it. ;)
>
> Thanks,
>   Harm
>
>

Re: how to give more horizontal space to the voice follower

[Werner LEMBERG]

>>> Why doesn't the `VoiceFollower` grob obey the `minimum-length`
>>> property (inspite of supporting the `spanner-interface`)?  What am
>>> I missing?
>>
>> add
>>
>>   \override VoiceFollower.springs-and-rods = #ly:spanner::set-spacing-rods

What's actually the reason to not have this set by default?  Ditto for
glissando lines.  My experience is that it is almost always necessary
increase the length of both grobs in real-world scores.

In case there aren't serious reasons against doing it I suggest to
change the default; I would also prepare a patch.


Werner

Re: The Guide to getting Point and Click going with Gvim under Ubuntu 18

[Martín Rincón Botero]

Hi David,
> I see the problem, but I think that solution is unwise as it leaves
> a redundant file in the user's home directory, which they may fear
> removing.

Oh, I see. I didn’t know that file could be safely removed.
> This script then has to be maintained, and it also makes it less obvious
> how to adjust the process for any differences between systems. I think
> the process is mysterious enough without hiding it any more

Right. I forgot that the steps for Fedora are slightly different. Out of 
curiosity, do Mac and Windows users have to stick to Frescobaldi for Point & 
Click? They’re not even mentioned in the Usage Manual.
> Debian 10/buster with Xpdf and emacs running on a 2000-vintage
> Pentium III at 650MHz in 512MB memory took less than a second to
> open the source at the first click, and thereafter serviced each
> click in 0.5 secs, just so long as the new target position is in
> the displayed window

Wow, that’s old hardware! In my Asus laptop from 2017, Atom takes a while to 
open the first time. After that, each click takes around 0.5 secs or less I 
would say. It’s not something of great concern to me, but it’s noticeable, 
especially after being used to Frescobaldi’s immediate reposition of the 
cursor. Perhaps it has to do with Atom (not the lightest editor around). Were 
Atom not so pleasing to the eye, I would probably try with another one to 
compare speed ;-).

www.martinrinconbotero.com
On 2. Nov 2020, 03:28 +0100, lilypond-user@gnu.org, wrote:
>
> I see the problem, but I think that solution is unwise as it leaves
> a redundant file in the user's home directory, which they may fear
> removing.

Re: problem with hacklily

[Paul Scott]

It opened fine with Firefox on my Linux machine and opened on my iMac in 
Safari but gave me a message that the "song" was locked because it was 
opened in another tab.


Stay safe,

Paul

On Nov 2, 2020, at 12:52 AM, Stefan Thomas 
 wrote:


Dear community,
I wanted to save a file in hacklily (https://www.hacklily.org/ 
).

Unfortunately I can't do this, I always get

TypeError: e.sent map is not a function.

I should mention that I use the firefox browser.
Has someone an idea what could be wrong?
Thanks,
Stefan