On Sat, Mar 13, 2021 at 05:19:49PM +0100, Robin Bannister wrote:
> Hallo there
>
> I noticed this while trying to make an MWE for a different problem.
>
> Maybe it counts as a limitation rather than a bug?
Hi Robin,
Thank you for the report. I don't think LilyPond guarantees a particular
order
> On 8 Mar 2021, at 18:22, Joe O'Farrell wrote:
>
>> On 8 Mar 2021, at 17:04, Hans Åberg wrote:
>>
>> The app should have a way to handle that.
>
> Apparently not - at least, not through the UI; Preferences tab is greyed out.
> I can try digging through the source code, but as you say, this
> On 8 Mar 2021, at 17:04, Hans Åberg wrote:
>
> The app should have a way to handle that.
Apparently not - at least, not through the UI; Preferences tab is greyed out. I
can try digging through the source code, but as you say, this should be a
simple setting *within* LP.
Time to fire up
;>> Apologies if this has been raised before (though I did look!) but there
>>> seems to be a problem with the LilyPond text editor on Mac whereby
>>> apostrophes are replaced by a “curly” version which isn’t recognised by the
>>> compiler, triggering a “not a note name
by the compiler,
> triggering a “not a note name error”. Tried re-installing, but as you can
> see, even the built-in demo fails:
These are called text substitutions, and can be changed at System Preferences →
Keyboard → Text, and should be possible to be turned off within the text
editor. For exampl
On Fri, Mar 5, 2021 at 5:29 AM bb wrote:
>
> \version "2.20.0"
> \relative c'' {\repeat volta 2 { f1 ( | }
>\alternative { {f2) r2}
> { f1) } } }
>
> No slur with the second alternative, warning that slur cannot be ended
>
> Warnung: slur kann nicht beendet werden
Thanks Jonas,
I have opened issue #6103
jostle
On 4/3/21 6:36 am, Jonas Hahnfeld wrote:
Am Donnerstag, dem 25.02.2021 um 14:32 +1100 schrieb
jos...@jostlesoft.com:
% The following source causes a segmentation fault
% in versions 2.20.0 and a local build from the latest master (2.23.1)
You probably should post this to the lilypond-list, not the bug list.
--
Knute Snortum
On Thu, Mar 4, 2021 at 7:08 AM Peter Anglea wrote:
>
> Hello, I wanted to make the LilyPond community aware of a real-world use
> case. I’m not sure if this is the kind of thing you would like to link from
Am Donnerstag, dem 25.02.2021 um 14:32 +1100 schrieb
jos...@jostlesoft.com:
> % The following source causes a segmentation fault
>
> % in versions 2.20.0 and a local build from the latest master (2.23.1)
>
> \version "2.20.0"
> \language "english"
>
> << { a2 b2 } \\ { \tweak X-offset #2 f'1 ~
Am Do., 25. Feb. 2021 um 04:32 Uhr schrieb :
>
> % The following source causes a segmentation fault
>
> % in versions 2.20.0 and a local build from the latest master (2.23.1)
>
> \version "2.20.0"
> \language "english"
>
> << { a2 b2 } \\ { \tweak X-offset #2 f'1 ~ f'1 } >>
>
>
Le 28/02/2021 à 15:53, Dan Eble a écrit :
The performance length is 4 whole notes, but the third part has only
half that. This is not what the image on the LSR means.
There is no \repeat music in the third staff, so why should there be
a volta bracket?
2.23 is handling this input more
On Feb 28, 2021, at 08:50, Jean-Charles Malahieude wrote:
>
> Revising the French translation of repeats.itely, I notice that the volta
> bracket doesn't appear in the third staff of the snippet with the master
> branch.
>
> Just compare the two versions of the online documentation of
nd@gnu.org
Sent: Wed, Feb 24, 2021 2:25 pm
Subject: Re: Incorrectly Formatted Tables, web.pdf
Hi Jonathan,
Am Dienstag, dem 23.02.2021 um 20:32 + schrieb Jonathan Levi via
bug-lilypond:
> Sir/Madam:
> I recently downloaded Lilypond v2.23, and with it the big documentation
> manual
>> I recently downloaded Lilypond v2.23, and with it the big
>> documentation manual, web.pdf.
>
> I think web.pdf is not really a priority with respect to formatting,
> as the name suggests you should just view the web page at
> lilypond.org.
+1
Werner
Hi Jonathan,
Am Dienstag, dem 23.02.2021 um 20:32 + schrieb Jonathan Levi via
bug-lilypond:
> Sir/Madam:
> I recently downloaded Lilypond v2.23, and with it the big documentation
> manual, web.pdf.
I think web.pdf is not really a priority with respect to formatting, as
the name suggests you
Am Dienstag, dem 23.02.2021 um 20:53 +0530 schrieb Ankush Laxman:
> Hi,
>
> I use a 64-bit Windows 10 machine. I downloaded the latest version of the
> Lilypond installation file for Windows from the Lilypond website (
> http://lilypond.org/windows.html). When I try to compile the test.ly file
>
On 2/17/21, 12:21 PM, "Arusekk" wrote:
> This statement seems a little bit strange to me. I didn't think we had a
> lilypond editing app on Linux -- only on Windows and MacOS. How are you
> using lilypond when it is "not told to lay out"? Are you using
> Frescobaldi? Are
Dnia środa, 17 lutego 2021 20:15:22 CET Jonas Hahnfeld pisze:
> Patch up at https://gitlab.com/lilypond/lilypond/-/merge_requests/655 ,
> this makes the given example work under Asan on my system. It would be
> great if you could test on your end (as far as I understand, you
> already compiled
> This statement seems a little bit strange to me. I didn't think we had a
> lilypond editing app on Linux -- only on Windows and MacOS. How are you
> using lilypond when it is "not told to lay out"? Are you using
> Frescobaldi? Are you using Denemo? Are you using Emacs? I would be
>
Am Mittwoch, dem 17.02.2021 um 18:16 +0100 schrieb Jonas Hahnfeld via
bug-lilypond:
> Am Mittwoch, dem 17.02.2021 um 00:00 +0100 schrieb Arusekk:
> > W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze:
> > > Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet),
> > > so you'll
On 2/16/21, 4:00 PM, "Arusekk" wrote:
On my box lilypond crashes every single time I command it to produce
PDFs (never does if not told to lay out), so I think I can provide much
help, maybe core files, or recorded execution from GDB (never tried to
do it before, though).
Am Mittwoch, dem 17.02.2021 um 00:00 +0100 schrieb Arusekk:
> W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze:
> > Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet),
> > so you'll definitely see worse performance (mostly slower startup) and
> > might run into occasional issues,
W dniu 16.02.2021 o 18:33, Jonas Hahnfeld pisze:
Usual disclaimer that LilyPond doesn't fully support Guile 2.2 (yet),
so you'll definitely see worse performance (mostly slower startup) and
might run into occasional issues, like this one. Guile 1.8 should be
the safer choice for now (if you
Am Dienstag, dem 16.02.2021 um 15:44 +0100 schrieb Arusekk:
> Hello lilypond crew!
>
> Reporting the bug here, since I saw on the bug link that you prefer mail
> over GitLab issues.
>
> When trying to process any file with \layout{} directive, lilypond
> crashes (Segmentation fault / address
> Inkscape works very well to convert PDFs to SVG, but if we expect
> our users to do that, then it's debatable whether we should have an
> SVG backend at all.
I agree. However, my SVG knowledge is very small; this means I'm not
qualified to make any decisions.
> (I mean this seriously: the
On Tue, 16 Feb 2021 at 08:44, Werner LEMBERG wrote:
>
>
> > How about hosting the fonts on www.lilypond.org and referencing them
> > in the @font-face definition?
>
> I think this is not a good idea.
I agree that hosting fonts would be a headache: everyone's svg
documents would suddenly depend
> How about hosting the fonts on www.lilypond.org and referencing them
> in the @font-face definition?
I think this is not a good idea.
* LilyPond fonts change from version to version, quite often in a
backwards-incompatible way. Hosting them for SVG access would
enforce us to completely
How about hosting the fonts on www.lilypond.org and referencing them in
the @font-face definition?
Johannes
Am 15.02.2021 um 21:06 schrieb Werner LEMBERG:
IMHO, this is as good (or as bad) as a default as 'serif'. If you
want SVG images to be similar to, say, PDF output, you have
* to
>> IMHO, this is as good (or as bad) as a default as 'serif'. If you
>> want SVG images to be similar to, say, PDF output, you have
>>
>>* to exactly specify which font you want to use for text, and
>>* to convert glyphs to paths, for example, by postprocessing
>> LilyPond's output
On Feb 15, 2021, at 04:44, Thomas Morley wrote:
>
> Here the ".|:"-bar-line is split into "|" at line-end and ".|:" at
> line-begin, but the volta-hook is not allowed for "|".
>
> This is the situation, as far as I can tell.
> The printed outcome is always the same since 2.12.3, although the
>
On Feb 14, 2021, at 23:26, Jürgen Reuter wrote:
>
> Hi Dan and all others,
>
> yes, the second, more compact / dense version definitely looks _much_ better!
> I would be happy if you could commit your change!
https://gitlab.com/lilypond/lilypond/-/issues/6098
Am 15.02.2021 um 10:15 schrieb Michael Käppler:
Am 14.02.2021 um 22:27 schrieb Dan Eble:
As I read Behind Bars, p.237, the bracket for volta 2 should not turn
down at the end in this case. Either way, it's strange that the
outcome depends on line breaking. If someone is willing to second
Upvoted. Maybe it should even be the default to embed the fonts (and
only those) that are actually used in the SVG with an option to turn
that feature off.
Johannes
Am 14.02.2021 um 20:30 schrieb Jean Abou Samra:
Could we possibly offer the option to embed the
fonts inside of the SVG file or
Am Mo., 15. Feb. 2021 um 09:35 Uhr schrieb Jonas Hahnfeld via
bug-lilypond :
>
> Am Sonntag, dem 14.02.2021 um 16:27 -0500 schrieb Dan Eble:
> > As I read Behind Bars, p.237, the bracket for volta 2 should not turn down
> > at the end in this case. Either way, it's strange that the outcome
Am 14.02.2021 um 22:27 schrieb Dan Eble:
As I read Behind Bars, p.237, the bracket for volta 2 should not turn down at
the end in this case. Either way, it's strange that the outcome depends on
line breaking. If someone is willing to second this, I am willing to
investigate it.
Seconded. I
Hi Dan and all others,
yes, the second, more compact / dense version definitely looks _much_
better!
I would be happy if you could commit your change!
Thank you,
Jürgen
On Sat, Feb 13, 2021 at 6:03 PM Dan Eble wrote:
Jürgen and all,
I've attached two images of the
Am Sonntag, dem 14.02.2021 um 16:27 -0500 schrieb Dan Eble:
> As I read Behind Bars, p.237, the bracket for volta 2 should not turn down at
> the end in this case. Either way, it's strange that the outcome depends on
> line breaking. If someone is willing to second this, I am willing to
>
Le 14/02/2021 à 19:48, Werner LEMBERG a écrit :
With 2.18, I see this instead:
IMHO, this is as good (or as bad) as a default as 'serif'. If you
want SVG images to be similar to, say, PDF output, you have
* to exactly specify which font you want to use for text, and
* to
> But what is the difference between _\markup and -\markup?
Alas, this is missing in the notation index.[*]
In general, if you use `-` before an object (attached to a note),
LilyPond uses a vertical default position. If you use `^` or `_`
instead, the object's vertical position is forced to be
Johannes Feulner writes:
> But what is the difference between _\markup and -\markup?
>
> Looking at the examples on
> http://lilypond.org/doc/v2.22/Documentation/notation/formatting-text I
> cannot see a difference.
_\markup is essentially the same as
-\withMusicProperty #'direction #DOWN
> With 2.18, I see this instead:
>
> font-family="Century Schoolbook L"
> font-weight="bold"
> font-size="6.9848"
> text-anchor="start"
> fill="currentColor">
>
>
>
IMHO, this is as good (or as bad) as a default as 'serif'. If you
want SVG images to be
Am Sonntag, dem 14.02.2021 um 18:25 +0100 schrieb Jean Abou Samra:
> Hello,
>
> Le 14/02/2021 à 16:59, Johannes Feulner a écrit :
> > Hi Aron,
> >
> > the \center-column issue seems to be a problem of the SVG backend. I
> > compiled LilyPond from master and use a custom backend based on
> >
Hello,
Le 14/02/2021 à 16:59, Johannes Feulner a écrit :
Hi Aron,
the \center-column issue seems to be a problem of the SVG backend. I
compiled LilyPond from master and use a custom backend based on
LilyPond's SVG backend. However, the pictures were made with
LilyPond's standard SVG
But what is the difference between _\markup and -\markup?
Looking at the examples on
http://lilypond.org/doc/v2.22/Documentation/notation/formatting-text I
cannot see a difference.
Johannes
The examples on
Am 14.02.2021 um 17:27 schrieb Werner LEMBERG:
I had seen the "-" operator before
Thanks,
and on
http://lilypond.org/doc/v2.22/Documentation/notation/the-tweak-command
the -\tweak is well documented.
Johannes
Am 14.02.2021 um 17:27 schrieb Werner LEMBERG:
I had seen the "-" operator before but could not find it in
LilyPond's docs.
If you look into the index, you can
> I had seen the "-" operator before but could not find it in
> LilyPond's docs.
If you look into the index, you can find it in the notation reference
(NR):
http://lilypond.org/doc/v2.23/Documentation/notation/expressive-marks-attached-to-notes#index-_002d
Werner
Hi Aron,
the \center-column issue seems to be a problem of the SVG backend. I
compiled LilyPond from master and use a custom backend based on
LilyPond's SVG backend. However, the pictures were made with LilyPond's
standard SVG backend. I've now used the PDF backend, it is not affected.
On 2021-02-14 7:08 am, Johannes Feulner wrote:
Hi there,
\center-column is broken. In 2.18 it was still OK. The lines of a
\center-column are supposed to be centered under each other. This is
at least with 2.23.1 not any longer the case. Please, see attached
pictures. The "" is clearly not
> Probable reason: The fullname property (Vorzeigename) of the fonts
> is set to Untitled-1, it should be the same as the name property:
>
> The following two changes fixed the problem for me: [...]
Thanks for the patch, which is now registered as a merge request.
Am Samstag, dem 13.02.2021 um 14:58 + schrieb James:
> On Sat, 2021-02-13 at 13:29 +0100, Johannes Feulner wrote:
> > HI there,
> >
> > updating from LilyPond version 2.19.53 to 2.23.1 I found unexpected
> > non-fatal error messages in LilyPonds output whenever a music
> > function
> > is
On Sat, 2021-02-13 at 13:29 +0100, Johannes Feulner wrote:
> HI there,
>
> updating from LilyPond version 2.19.53 to 2.23.1 I found unexpected
> non-fatal error messages in LilyPonds output whenever a music
> function
> is defined:
>
> Analysieren...
> Programmierfehler: Parsed object should
Le 13/02/2021 à 13:29, Johannes Feulner a écrit :
HI there,
updating from LilyPond version 2.19.53 to 2.23.1 I found unexpected
non-fatal error messages in LilyPonds output whenever a music function
is defined:
Analysieren...
Programmierfehler: Parsed object should be dead #Music((void .
Hello Johannes,
On Sat, 2021-02-13 at 14:24 +0100, Johannes Feulner wrote:
> Hi James,
>
> thanks for advancing my issue.
>
> The attached picture got lost in the mail response from the bug list
> and
> is not present in the issue tracker either.
>
> Can I do something for pictures to survive
Johannes Feulner writes:
> HI there,
>
> updating from LilyPond version 2.19.53 to 2.23.1 I found unexpected
> non-fatal error messages in LilyPonds output whenever a music function
> is defined:
>
> Analysieren...
> Programmierfehler: Parsed object should be dead # Music((void . #t))((name .
Hi James,
thanks for advancing my issue.
The attached picture got lost in the mail response from the bug list and
is not present in the issue tracker either.
Can I do something for pictures to survive in future postings, or are
attachments simply not supported?
Cheers,
Johannes
--
On Sat, 2021-02-13 at 12:30 +0100, Johannes Feulner wrote:
> Hi there,
>
>
>
> updating from LilyPond 2.19.53 to 2.23.1 I found, that my Java
>
> application does not find emmentaler fonts anymore.
>
>
>
> Probable reason: The fullname property (Vorzeigename) of the fonts
> is
>
> set to
On Wed, 2021-01-27 at 14:31 +0100, Robin Bannister wrote:
> Hallo again
>
>
> In the meantime it has occurred to me that moving the gratuitous
> magstep
> scaling from baseline-skip over to thickness is perhaps not the
> answer.
>
> Since the triangle is applied mainly as a glyph it should not
Am Montag, dem 08.02.2021 um 15:53 -0500 schrieb Nate Whetsell:
> Hi there,
>
> Thank you for all your work on LilyPond!
>
> It appears to be impossible to use a Melody_engraver in a Voice that also
> includes a CueVoice. Here’s a LilyPond example that illustrates the issue:
>
> ```
> \version
Am Samstag, dem 30.01.2021 um 02:39 -0500 schrieb James B. Wilkinson:
> I had a file claiming to be version 2.18 and opened it in Lilypond 2.22 on a
> MacBook Pro running Mavericks. When I chose "Update syntax” from the Compile
> menu, lilylib.py threw errors indicating that Python 2 was running
Hallo again
In the meantime it has occurred to me that moving the gratuitous magstep
scaling from baseline-skip over to thickness is perhaps not the answer.
Since the triangle is applied mainly as a glyph it should not respond to
overrides on those two properties. Consider squashing a
Am Sa., 23. Jan. 2021 um 17:44 Uhr schrieb Nate Whetsell
:
>
> Hi there,
>
> Thank you for all your work on LilyPond!
>
> The syntax for \revert-ing certain properties appears to have changed after
> LilyPond 2.18, which makes the “Altering the length of beamed stems” example
> in the
>> `convert-ly` is a python script. For Windows, rename the file
>>
>> c:\Program Files (x86)\usr\bin\convert-ly
>>
>> to
>>
>> convert-ly.py
>>
>> Then Windows will know to run the python interpreter on this file.
>>
>> NOTE: This script works as is on Linux because the first line of the
> `convert-ly` is a python script. For Windows, rename the file
>
> c:\Program Files (x86)\usr\bin\convert-ly
>
> to
>
> convert-ly.py
>
> Then Windows will know to run the python interpreter on this file.
>
> NOTE: This script works as is on Linux because the first line of the
> script
Hello
On 29/11/2020 17:40, Thomas Morley wrote:
Hi,
the following code
{
\tempo 4 = 60
\override TupletBracket.after-line-breaking =
#(lambda (grob)
(format #t "\nstyle is: '~a" (ly:grob-property grob 'style)))
\override TupletBracket.style = #'dashed-line
\tuplet 3/2 {
Hello
On 10/01/2021 13:44, Thomas Morley wrote:
Hi,
at https://lilypond.org/macos-x.html
the images
./Documentation/pictures/Learning_Macos_welcome.png
./Documentation/pictures/Learning_Macos_pdf_output.png
are not longer correct.
The first one is intended to show the code for the scale
> On 12 Jan 2021, at 11:48, Györgyi Deák wrote:
>
> Which I did, but the Mac won't let me use it saying: “LilyPond cannot be
> opened because the developer cannot be verified."
Try to open it by going into the Finder, using the pop-up menu on the app icon,
item "Open"; if it works, this not
Hello,
On 27/12/2020 08:52, Thomas Morley wrote:
the initial example works at least since 2.8.0 (yes, I've a working 2.8.0)
A long time...
Tbh, I couldn't figure why it works before 2.19.21, though, if it
doesn't anymore, it should be documented either as it is done for
\relative already or in
Am Montag, dem 28.12.2020 um 21:53 +0100 schrieb Federico Bruni:
>
> Il giorno mer, dic 23 2020 at 15:05:57 +0100, Malte Meyn
> ha scritto:
> > Hi list,
> >
> > someone asked me whether LilyPond could have a feature that announces
> > new released versions. I don’t think that this is
Hello,
On 29/12/2020 01:31, Freeman Gilmore wrote:
LilyPond Internals Reference, 2.2.58 key_engraver
keyAlterationOrder(list)
It should read: "… *step *is a number from 0 to 6 and *alter *from
-2 (flat) to 2 (sharp)."
(Not -2 (sharp) to 2 (flat).)
Thank you, ƒg
On 2020-12-28 6:18 pm, Aaron Hill wrote:
On 2020-12-28 5:31 pm, Freeman Gilmore wrote:
LilyPond Internals Reference, 2.2.58 key_engraver
keyAlterationOrder(list)
It should read: "… *step *is a number from 0 to 6 and *alter
*from
-2 (flat) to 2 (sharp)."
(Not -2
On 2020-12-28 5:31 pm, Freeman Gilmore wrote:
LilyPond Internals Reference, 2.2.58 key_engraver
keyAlterationOrder(list)
It should read: "… *step *is a number from 0 to 6 and *alter
*from
-2 (flat) to 2 (sharp)."
(Not -2 (sharp) to 2 (flat).)
What version of the docs
Il giorno mer, dic 23 2020 at 15:05:57 +0100, Malte Meyn
ha scritto:
Hi list,
someone asked me whether LilyPond could have a feature that announces
new released versions. I don’t think that this is desirable but
what about the info-lilypond mailing list promoted at
Am Sa., 26. Dez. 2020 um 20:46 Uhr schrieb Dan Eble :
>
> On Dec 26, 2020, at 13:29, Thomas Morley wrote:
> >
> > Hi,
> >
> > the following code gives bad output.
> >
> > %% Start
> > \version "2.20.0"
> >
> > one = { e''2 \tag #'score f'' \tag #'part fis'' g''1 }
> > two = { e''2 d'' g'1 }
> >
>
On Dec 26, 2020, at 13:29, Thomas Morley wrote:
>
> Hi,
>
> the following code gives bad output.
>
> %% Start
> \version "2.20.0"
>
> one = { e''2 \tag #'score f'' \tag #'part fis'' g''1 }
> two = { e''2 d'' g'1 }
>
> \removeWithTag #'score \partCombine \one \two
> %% end
>
> it looks like
> On Dec 22, 2020, at 14:59, Dan Eble wrote:
>
> I guess that it is undesirable for these bends to cross the barlines. If
> someone validates my judgment, I'll create a ticket and try to improve it.
> —
> Dan
https://gitlab.com/lilypond/lilypond/-/issues/6074
—
Dan
Am So., 13. Dez. 2020 um 16:56 Uhr schrieb James Lowe :
>
> On 13/12/2020 15:29, Jonas Hahnfeld via bug-lilypond wrote:
> > Hi all, Harm,
> >
> > Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley:
> >> Hopefully somebody with more knowledge, chimes in.
> > Could you create a GitLab
On 05/12/2020 11:16, Klaus Blum wrote:
Dear List members,
Hello,
In the “Easier editing” page [1], OOoLilyPond is listed in the “Other
programs
no longer being actively developed” section but I think that it is
active
again. Is this considered as a documentation bug?
On 13/12/2020 15:29, Jonas Hahnfeld via bug-lilypond wrote:
Hi all, Harm,
Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley:
Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear :
The part of the slur before the line break is badly shaped when another
staff has a clef
Hi all, Harm,
Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley:
> Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear
> :
> >
> > The part of the slur before the line break is badly shaped when another
> > staff has a clef change.
> >
> > \version "2.20.0"
> >
> > <<
> >
Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear :
>
> The part of the slur before the line break is badly shaped when another
> staff has a clef change.
>
> \version "2.20.0"
>
> <<
>\new Staff {
> R1*2
> r2 r4 r8 r16 r32 e''32( |
> \break
> d''8) r r4 r2 |
>
Am Mittwoch, dem 09.12.2020 um 22:16 +0100 schrieb Mats Bengtsson:
> Hi,
>
> I just tried a larger score in 2.21.81 and found a regression bug
> compared to 2.20.0, that's illustrated in the following example:
>
> \fixed c'{
> e4 8. 16 \afterGrace e2 {d16 e } | % Works fine
> f4 4 r2 |
> e4 8.
On Dec 6, 2020, at 06:39, Jonas Hahnfeld wrote:
>
> (https://gitlab.com/lilypond/lilypond/-/merge_requests/540), but I
> think this means we should not release the stable version 2.22.0
> without the fix and an additional 2.21.82. A bit unfortunate, but
> better now than discovered by users.
+1
Am Mittwoch, dem 02.12.2020 um 06:40 + schrieb James Lowe:
> On 01/12/2020 21:42, Lukas-Fabian Moser wrote:
> > Hi Harm,
> >
> > > avoid-slur is the correct method:
> > >
> > > %#(ly:set-option 'debug-skylines #t)
> > >
> > > \score {
> > > {
> > > \time 12/8
> > > \relative c'
On 01/12/2020 21:42, Lukas-Fabian Moser wrote:
Hi Harm,
avoid-slur is the correct method:
%#(ly:set-option 'debug-skylines #t)
\score {
{
\time 12/8
\relative c' {
a8 b\( c a b c d e f d e f
g a b g a b c2.
\once \override Script.avoid-slur = #'inside
I did a git bisect on this (and confirmed the result by checking that reverting
the change removes the problem):
905ba822ef656b06b1cc4f0ca33960c9c is the first bad commit
commit 2c2908c905ba822ef656b06b1cc4f0ca33960c9c
Author: Malte Meyn
Date: Sun Sep 29 10:10:35 2019 +0200
Issue 5563:
On Thu, Nov 26, 2020 at 12:27 PM Jonas Hahnfeld wrote:
> Am Donnerstag, dem 26.11.2020 um 11:39 -0500 schrieb Trevor Bača:
> > On Tue, Nov 24, 2020 at 6:57 PM Aaron Hill
> wrote:
> >
> > > On 2020-11-24 3:44 pm, Trevor Bača wrote:
> > > > Hi,
> > > >
> > > > ### BEGIN ###
> > > >
> > > >
Am Donnerstag, dem 26.11.2020 um 11:39 -0500 schrieb Trevor Bača:
> On Tue, Nov 24, 2020 at 6:57 PM Aaron Hill wrote:
>
> > On 2020-11-24 3:44 pm, Trevor Bača wrote:
> > > Hi,
> > >
> > > ### BEGIN ###
> > >
> > > \version "2.21.80"
> > >
> > > \markup { \note #"4.." #UP }
> > >
> > > ###
On Tue, Nov 24, 2020 at 6:57 PM Aaron Hill wrote:
> On 2020-11-24 3:44 pm, Trevor Bača wrote:
> > Hi,
> >
> > ### BEGIN ###
> >
> > \version "2.21.80"
> >
> > \markup { \note #"4.." #UP }
> >
> > ### END ###
> >
> > GNU LilyPond 2.21.80
> > Processing `test.ly'
> > Parsing...
> > test.ly:3:17:
Trevor Bača writes:
> Hi,
>
> ### BEGIN ###
>
> \version "2.21.80"
>
> \markup { \note #"4.." #UP }
>
> ### END ###
>
> GNU LilyPond 2.21.80
> Processing `test.ly'
> Parsing...
> test.ly:3:17: error: wrong type for argument 1. Expecting duration, found
> "4.."
> \markup { \note
>
On 2020-11-24 3:44 pm, Trevor Bača wrote:
Hi,
### BEGIN ###
\version "2.21.80"
\markup { \note #"4.." #UP }
### END ###
GNU LilyPond 2.21.80
Processing `test.ly'
Parsing...
test.ly:3:17: error: wrong type for argument 1. Expecting duration,
found
"4.."
\markup { \note
Il giorno gio, nov 19 2020 at 16:58:31 -0500, Trevor Bača
ha scritto:
(minimum-distance . 12) % errant comment causes crash
You should use `;` to add a comment in a Scheme block, so it doesn't
look like a bug to me.
v2.20 did not produce an error, but the documentation already
> On 19 Nov 2020, at 21:17, Trevor Bača wrote:
>
> ### BEGIN ###
>
> \version "2.20.0"
> \include "-"
>
> \new Staff
> {
>c'4
> }
>
> ### END ###
>
> Hangs during parsing:
>
> GNU LilyPond 2.20.0
> Processing `test.ly'
> Parsing...
> < hangs forever >
>
> Presumably the (spurious)
Am Do., 29. Okt. 2020 um 18:18 Uhr schrieb Johannes Feulner
:
>
> I suggest to update code and picture of the snippet "Adding Links to
> objects".
>
> Changes:
>
> * Update link URLs to a more current version of the documentation
>
> * Fix link for accidental
>
> #(define (add-link url-strg)
>
Am 28.10.2020 um 20:08 schrieb Graham King:
I think you're right. I reported this about a year ago, but I think it was a
really busy time for the developers and it fell through the cracks. There's a
little more detail at
I think you're right. I reported this about a year ago, but I think it was a
really busy time for the developers and it fell through the cracks. There's a
little more detail at
https://lists.gnu.org/archive/html/bug-lilypond/2019-10/msg00031.html
-- Graham
> On 28 Oct 2020, at 15:20,
Am 28.10.2020 um 15:25 schrieb Johannes Feulner:
Instead of "Zusammenstoßf" it should be "Zusammenstoß"
Fixed in 'translation'. Thanks for reporting!
Michael
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Hello Jean and Jonas,
Filed
https://gitlab.com/lilypond/lilypond/-/issues/6055
Many thanks,
mattfong
On Thu, Oct 15, 2020 at 3:16 PM Matthew Fong wrote:
> Hello Jean and Jonas,
>
> I appreciate the directions. I will work through the directions and file
> the bug!
>
>
> Many thanks,
>
Hello Jean and Jonas,
I appreciate the directions. I will work through the directions and file
the bug!
Many thanks,
mattfong
On Thu, Oct 15, 2020 at 1:58 PM Jonas Hahnfeld wrote:
> Am Donnerstag, den 15.10.2020, 21:39 +0200 schrieb Jean Abou Samra:
>
> Hello Werner,
>
>
> What is the proper
Le 15/10/2020 à 22:58, Jonas Hahnfeld a écrit :
Am Donnerstag, den 15.10.2020, 21:39 +0200 schrieb Jean Abou Samra:
Hello Werner,
What is the proper process to file this as a bug?
Many thanks,
mattfong
Go to
https://gitlab.com/lilypond/lilypond/-/issues
You will need a GitLab account, and
Am Donnerstag, den 15.10.2020, 21:39 +0200 schrieb Jean Abou Samra:
>
>
>
> Hello Werner,
>
> What is the proper process to file this as a bug?
>
> Many thanks,
> mattfong
> Go to
>
> https://gitlab.com/lilypond/lilypond/-/issues
>
> You will need a GitLab account, and appropriate
801 - 900 of 28975 matches
Mail list logo
