>
> With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs: first
> is without the offending font installed, the second is the temporary file
> produced when the font is present.
>
Thanks, but I am more interested in the log than the PDF for this one.
On 2023-05-26 02:24, Jean Abou Samra wrote:
Good that you can reproduce again. Now, can you try the patch with
FcPatternPrint and send the log? (No need for FC_DEBUG or --verbose or
--ps this time.)
With lilypond 2.25.6 and your second patch applied, here are 2 .PDFs:
first is without
Le jeudi 25 mai 2023 à 19:06 -0600, Colin Campbell a écrit :
> I believe we now have a Bingo!
>
> I d/l and built lilypond 2.25.5 from the website, and ran it against the
> test file; it ran successfully.
>
> I re-installed the fonts-noto-color-emoji package, and ran lilypo
Le mercredi 24 mai 2023 à 20:31 -0600, Colin Campbell a écrit :
> Applied this on top of your previous patch; let me know if you want it
> done differently.
>
> Again, no problems applying, compiling lilypond, nor compiling the test
> file.
>
> Resulting .PDF attached
Sorry for not being
On 2023-05-23 14:38, Jean Abou Samra wrote:
Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit :
So Pango is apparently requesting a font with colored glyphs from Fontconfig...
Speaking of which, I would also be interested in the output with
```
diff --git
On 2023-05-23 13:28, Jean Abou Samra wrote:
Colin: it's really hard to debug this remotely (we might have to resort to VNC
or such, I'm afraid...) but there is one simple thing I would be interested in:
if you apply this patch, recompile LilyPond and redo the test, what happens?
```
diff
Le mercredi 24 mai 2023 à 09:08 +, Werner LEMBERG a écrit :
> > So Pango is apparently requesting a font with colored glyphs from
> > Fontconfig...
>
> A bug?
Probably.
So far, I've been unable to understand where this happens; "git grep FC_COLOR"
yields no results in the Pango source
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
A bug?
Werner
Le dimanche 21 mai 2023 à 22:38 +0200, Peter Häring a écrit :
> % percent sign interferes with inline clef.
> % There is extra space for the clef,
> % but the percent sign is centered .
> % It should be positioned with the same padding
> % to the left bar line as the others.
> % Or: it should be
Le mardi 23 mai 2023 à 22:08 +0200, Jean Abou Samra a écrit :
> So Pango is apparently requesting a font with colored glyphs from
> Fontconfig...
Speaking of which, I would also be interested in the output with
```
diff --git a/lily/all-font-metrics.cc b/lily/all-font-metrics.cc
index
Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit :
> Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
>
> > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> > is a LilyPond or a Pango issue).
>
> I'm rather sure it's a Pango or Fontconfig
Le mardi 23 mai 2023 à 21:15 +0200, Jean Abou Samra a écrit :
> Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
>
> > Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> > is a LilyPond or a Pango issue).
>
> I'm rather sure it's a Pango or Fontconfig
Le lundi 22 mai 2023 à 08:07 +, Werner LEMBERG a écrit :
> Regarding (2) I'm not sure where exactly the problem lies (i.e., whether it
> is a LilyPond or a Pango issue).
I'm rather sure it's a Pango or Fontconfig issue.
Based on the fact that we use Pango's FreeType backend, which is not
> Following your suggestion, Werner, I tried the test file with the
> cairo back end, and it worked as expected.
Great, please send me the created PDF for further analysis – just to
be sure :-)
> I then deleted the Noto Color Emoji font (synaptic also deleted
> texlive fonts extra links), and
On 2023-05-22 02:07, Werner LEMBERG wrote:
(1) You have the font 'Noto Color Emoji' installed on your system (the
new one, with scalable glyphs using the 'COLR' v1 format). Say
`fc-list | less` to find out where it is located. This font
format is not supported by GhostScript
Colin,
>> All this comes about as I'm thinking of getting back to
>> some documentation work, and wanted to compile docs locally. I'll
>> still keep that goal in mind.
>>
>> If you can still reproduce the problem after this cleaning, could
>> you run
>>
>> ```
>> FC_DEBUG=2025
(Adding back the bug list)
Le samedi 20 mai 2023 à 17:51 -0600, Colin Campbell a écrit :
>
> I redid git bisect today, doing everything on the command line (I used
> Frescobaldi last night). Each time, I ran "
>
> ```
> colin@Calvin:/Work/lilypond/lilypond$ cd build
>
Thank you! I simply replaced font-lock-reference-face with
font-lock-constant-face in
/usr/share/emacs/site-list/lilypond-font-lock.el and it works!
Awesome!
Stéphane SOPPERA writes:
> [1. text/plain]
> Hi Jonas,
>
> The documentation of font-lock-reference-face reads:
>
>> This variable is
Hi Jonas,
The documentation of font-lock-reference-face reads:
This variable is an alias for ‘font-lock-constant-face’.
This variable is obsolete since 20.3;
use ‘font-lock-constant-face’ instead.
Probably introduced at or before Emacs version 19.29.
So I guess you could try
Thank you very much.
Is there a temporary fix, i could try? I don't look forward to downgrade
to emacs 28.
Jonas
Jean Abou Samra writes:
> [[PGP Signed Part:Undecided]]
> 1. ( ) text/plain (*) text/html
>
> Thanks, filed as https://gitlab.com/lilypond/lilypond/-/issues/6609
Le vendredi 19 mai 2023 à 23:00 -0600, Colin Campbell a écrit :
> The result of git bisect:
>
> 1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit
> commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095
> Author: Jonas Hahnfeld
> Date: Mon Apr 3 22:57:26 2023 +0200
>
> Doc: Avoid
The result of git bisect:
1db87a2537d6d5ef6631cfbda63954c0a6ee095 is the first bad commit
commit d1db87a2537d6d5ef6631cfbda63954c0a6ee095
Author: Jonas Hahnfeld
Date: Mon Apr 3 22:57:26 2023 +0200
Doc: Avoid full stop in node names
This propagates the changes from commit c245707e4f to
On 2023-05-19 15:43, Jean Abou Samra wrote:
Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit :
Can you try to find which commit introduced the problem for you, using 'git
bisect'?
Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu
23.04 VM and compiled
Le vendredi 19 mai 2023 à 21:00 +0200, Jean Abou Samra a écrit :
> Can you try to find which commit introduced the problem for you, using 'git
> bisect'?
Alternatively: what's your Ubuntu version? I just installed a fresh Ubuntu
23.04 VM and compiled LilyPond in it but I cannot reproduce the
Thanks, filed as https://gitlab.com/lilypond/lilypond/-/issues/6609
Best
Jean
signature.asc
Description: This is a digitally signed message part
Le vendredi 19 mai 2023 à 12:26 -0600, Colin Campbell a écrit :
>
> On 2023-05-19 11:03, Jean Abou Samra wrote:
> > \version "2.25.5"
> >
> > #(define-markup-command (db layout props arg) (markup?)
> > (let ((stil (interpret-markup layout props arg)))
> > (pretty-print (ly:stencil-expr
On 2023-05-19 11:03, Jean Abou Samra wrote:
\version "2.25.5"
#(define-markup-command (db layout props arg) (markup?)
(let ((stil (interpret-markup layout props arg)))
(pretty-print (ly:stencil-expr stil))
stil))
\markup \db abc
Terminal output:
###
Le vendredi 19 mai 2023 à 09:43 -0600, Colin Campbell a écrit :
> > Of all the errors you posted, which one is it now?
> ```
> colin@Calvin:/Work$ lilypond Non-Musical.ly
> GNU LilyPond 2.25.5 (running Guile 2.2)
> Processing `Non-Musical.ly'
> Parsing...
> Interpreting music...
On 2023-05-18 23:30, Jean Abou Samra wrote
Thanks, Werner, for the suggestion. I just tried it, and lilypond still errors
as before.
Of all the errors you posted, which one is it now?
colin@Calvin:/Work$ lilypond Non-Musical.ly
GNU LilyPond 2.25.5 (running Guile 2.2)
Processing
> Thanks, Werner, for the suggestion. I just tried it, and lilypond still
> errors as before.
Of all the errors you posted, which one is it now?
On 2023-05-18 22:09, Werner LEMBERG wrote:
ran make successfully, got carried away and may have shot myself in
the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Thanks,
> ran make successfully, got carried away and may have shot myself in
> the foot by running sudo make install.
You should actually do
```
make bytecode
sudo make install-bytecode
```
Without installing the Guile bytecode, LilyPond is slooow.
Werner
On 2023-05-18 21:07, Colin Campbell wrote:
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory
and start a fresh build.
Deleted /build,
mkdir build,
cd build
On 2023-05-18 01:55, Jean Abou Samra wrote:
I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
Deleted /build,
mkdir build,
cd build
ran make successfully, got carried away and
Wonderful, thank you!
\--
Gwyn Ciesla
she/her/hers
\
in your fear, seek only peace
in your fear, seek only love
\-d. bowie
Sent from Proton Mail mobile
\ Original Message
On May 18, 2023, 12:53 PM, Jean Abou
Le jeudi 18 mai 2023 à 11:27 +0200, Jean Abou Samra a écrit :
> Gwyn, is it convenient for you to test patches? I think I see what this is
> caused by, but I cannot reproduce the bug in a local build (knowing what
> exact compiler flags are used in Fedora's builds
> might help).
> I'd like to
Gwyn, is it convenient for you to test patches? I think I see what this is
caused by, but I cannot reproduce the bug in a local build (knowing what exact
compiler flags are used in Fedora's builds might help).
I'd like to know if this fixes it:
```
diff --git a/lily/all-font-metrics-scheme.cc
> I'm going nuclear tomorrow: delete my clone, and start over.
No need to be *that* nuclear, you can just remove the build directory and start
a fresh build.
> Le 18 mai 2023 à 05:49, Colin Campbell a écrit :
>
> Attached console output. I'll do a git pull and recompile a bit later, and
> report what happens. Note that the same test file when compiled using
> Frescobaldi as a front end, produces the following output:
>
>
> Starting lilypond
On 2023-05-17 18:25, Jean Abou Samra wrote:
Could you please run with `lilypond --verbose` and send the output?
Thanks,
Jean
Now lilypond blows up in make:
colin@Calvin:/Work/lilypond/lilypond/build$ make -j3 SILENT=1
PythonUI_Init()
PythonUI_Init()
PythonUI_Init()
Attached console output. I'll do a git pull and recompile a bit later,
and report what happens. Note that the same test file when compiled
using Frescobaldi as a front end, produces the following output:
Starting lilypond 2.25.5 [Non-Musical.ly]...
programming error: unknown context mod tag
Le mercredi 17 mai 2023 à 17:48 -0600, Colin Campbell a écrit :
> Happens to me on Ubuntu as well:
I don't think that's the same bug. Regarding this:
> Fontconfig error: No writable cache directories
This error popped up at some point during the current cycle before being fixed
shortly
Happens to me on Ubuntu as well:
&&
colin@Calvin:/Work$ lilypond Non-Musical.ly
GNU LilyPond 2.25.5 (running Guile 2.2)
Fontconfig error: No writable cache directories
Processing `Non-Musical.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Le mercredi 17 mai 2023 à 20:02 +, Gwyn Ciesla via bug-lilypond a écrit :
> Attaching reproducer.
>
> From Fedora bug:
>
> When I attempt to build a score using a PianoStaff or GrandStaff (which
> contains more than one sub-staff), lilypond crashes.
>
> Reproducible: Always
>
> Steps to
Le lundi 01 mai 2023 à 20:19 -0400, Connor Harris a écrit :
> I've discovered a bizarre bug (originally in LilyPond 2.22.1, confirmed in
> all versions up through 2.23.13 with reason to suspect that the underlying
> issue may still exist in later versions) with vertical spacing of lyrics.
> Under
> Thanks for reporting. Werner, can you take a look please? It appears
> that 4494a12ec8d3408981b26f4dc4040e2f985da06f breaks `convert-ly -`
> to read stdin (on Windows).
https://gitlab.com/lilypond/lilypond/-/merge_requests/1948
Werner
Le jeudi 13 avril 2023 à 20:30 +0200, Craig Fearing a écrit :
> In the attached, fairly minimized file:
>
> \version "2.18.2"
>
> \layout {
> \context { \Lyrics \override LyricText #'font-size = #1.8 }
> }
>
> If I try to update to 2.25.*3* (using the tool in Frescobaldi 3.1.3)
> How did you install your self-compiled LilyPond? I would expect make install
> to install into /usr/local/bin/, not into /usr/bin/.
I'm on ArchLinux and I tweak the lilypond-git aur package to pull from
my own local repository.
https://aur.archlinux.org/packages/lilypond-git
--
Pierre-Luc
Le samedi 08 avril 2023 à 11:30 -0400, Pierre-Luc Gauthier a écrit :
> I've just compiled 3123dcf1 and I running /usr/bin/convert-ly returns :
>
> Traceback (most recent call last):
> File "/usr/bin/convert-ly", line 82, in
> import convertrules
> ModuleNotFoundError: No module named
Le samedi 08 avril 2023 à 18:39 +0100, Gilberto Agostinho via bug-lilypond a
écrit :
> Hi all,
>
> I've came across a strange bug with \autoChange which was not present in
> version 2.22.2 but is present in version 2.24.1 (and was probably
> introduced somewhere in between these two
[https://gitlab.com/lilypond/lilypond/-/issues/6565](https://gitlab.com/lilypond/lilypond/-/issues/6565)
signature.asc
Description: This is a digitally signed message part
Le lundi 03 avril 2023 à 21:32 +0200, David Kastrup a écrit :
>
> dak@lola:/usr/local/tmp/lilypond$ lilypond scheme-sandbox
> GNU LilyPond 2.25.0 (running Guile 2.2)
> Processing `/usr/local/share/lilypond/2.25.0/ly/scheme-sandbox.ly'
> Parsing...
> GNU Guile 2.2.7
> Copyright (C)
On Mon, 2023-03-27 at 18:06 -0500, Jason Yip via bug-lilypond wrote:
> Hi, I'm following the steps listed at
> https://lilypond.org/doc/v2.25/Documentation/contributor/introduction-to-issues
>
> to get started.
>
> My gitlab id: ljyip
Note that these instructions are for issue *triage*, ie
On Mar 29, 2023, at 18:04, Grant Diffey wrote:
>
> I do wonder if there's a way to make the horizontal spacing.. 'nicer' but
> it's certainly functional for all my purposes as is.
My biggest questions about this use case surround the layout changes that are
baked into gregorian.ly, for
Werner,
I think the remaining question is how common is this as a style? (I find
many examples in books but few online :) and does that warrant adding an
additional staff type?
I'm very happy with the outcome here. My thanks to all involved,
particularly Dan.
I do wonder if there's a way to
Thankyou dan
Either of those would be acceptable..
\version "2.24.1"
\include "gregorian.ly"
ancientmusic = {
\clef "vaticana-do3"
\[ d8 \pes \melisma f \melismaEnd \] d \[ d \flexa \melisma c \melismaEnd
\]
f g \[ f \flexa \melisma g \pes a \melismaEnd \] a4
\finalis
\[ e8 \pes
On 2023-03-28 20:45, Jean Abou Samra wrote:
(CCing Jason Yip, who may be interested in this as part of this GSoC
application on the auto-beaming project.)
Yes, I had that in mind, but since the main topic of the GSoC was beam
subdivisions I hope that you Jason can find a suitable
>> However none of the staff types dan suggested will do what I could
>> previously do. Gregorian divisiones not supported on modern staffs
>> is a reasonable closure for this as a bug however I've previously
>> been able to use the gregorian divisions on a 'normal staff' so
>> from my pov this
On Mar 28, 2023, at 16:36, Grant Diffey wrote:
>
> Sure,
>
> However none of the staff types dan suggested will do what I could previously
> do. Gregorian divisiones not supported on modern staffs is a reasonable
> closure for this as a bug however I've previously been able to use the
>
Sure,
However none of the staff types dan suggested will do what I could
previously do. Gregorian divisiones not supported on modern staffs is a
reasonable closure for this as a bug however I've previously been able to
use the gregorian divisions on a 'normal staff' so from my pov this is a
Le mercredi 29 mars 2023 à 07:18 +1100, Grant Diffey a écrit :
> To clarify I'm transcribing vaticana using a 'modern' staff and beaming for
> melisma none of the staff types support modern beamed 8th notes. this is the
> convention in the church music I'm scoring (vaticana original) + modern
>
(CCing Jason Yip, who may be interested in this as part of this GSoC
application on the auto-beaming project.)
Le mardi 28 mars 2023 à 14:50 +0200, Mats Bengtsson a écrit :
> Hi,
>
> I know that there are several old bug reports on auto-beaming, but I've
> come across a couple of
On Mar 28, 2023, at 03:02, Jean Abou Samra wrote:
> Le mardi 28 mars 2023 à 12:54 +1100, Grant Diffey a écrit :
>> The following example:
>> \include "gregorian.ly"
>> { c' \divisioMaior d' \finalis }
>> Renders 'correctly' in 2.22 (using hacklily)
>> and incorrectly on my debian machine with
Le mardi 28 mars 2023 à 12:54 +1100, Grant Diffey a écrit :
> The following example:
>
> \include "gregorian.ly"
> { c' \divisioMaior d' \finalis }
>
> Renders 'correctly' in 2.22 (using hacklily)
> and incorrectly on my debian machine with Lilypond 2.24
Dan?
signature.asc
Description:
Jason,
Le lundi 27 mars 2023 à 22:35 -0500, Jason Yip via bug-lilypond a écrit :
> In NR 3.2.1 "Structure of a score", 2 references to the `\book` command
> are not in a `@code{}` command in the 2nd last paragraph.
>
>
> diff --git a/Documentation/en/notation/input.itely
>
Le lundi 27 mars 2023 à 18:06 -0500, Jason Yip via bug-lilypond a écrit :
> Hi, I'm following the steps listed at
> [https://lilypond.org/doc/v2.25/Documentation/contributor/introduction-to-issues](https://lilypond.org/doc/v2.25/Documentation/contributor/introduction-to-issues)
>
> to get
I just tested this on my machine, and this didn't seem to happen. The
rest was rendered with a line above and below, which I think is how it
is supposed to be drawn, similarly to half and whole rests.
-William
On 3/23/23 14:39, thysupremematrix--- via bug-lilypond wrote:
Code:
\version
Le dimanche 05 mars 2023 à 23:38 -0700, Alexandre Loomis a écrit :
> In Notation Reference 5.3.4 - the \tweak command, the sentence
>
> "Tweaking a whole chord *does not do anything *since its music event only
> acts as a container, and all layout objects are created from events inside
> of
Le mardi 28 février 2023 à 12:41 +0100, Simon Albrecht a écrit :
> Hello everyone,
>
> Melody_engraver readily sets different stem directions either side of a
> tie. I don’t think it should do that.
>
> %
> \version "2.25.2"
>
> \layout {
> \context {
>
Le lundi 27 février 2023 à 15:25 +0200, Valter Maasalo a écrit :
> Figured bass brackets should go around the figures, not below them. This
> happens when the figures are not on their own line in a FiguredBass context,
> but in a Staff.
>
>
>
>
> \version "2.25.1"
> \figuremode {
>
Le vendredi 10 février 2023 à 16:16 -0800, Saul Tobin a écrit :
> Just want to follow up — is there an issue tracked for this one? Thanks
Sorry for the long delay. I just did a round of issue-opening, this one is now
https://gitlab.com/lilypond/lilypond/-/issues/6551
signature.asc
Description:
Le mardi 29 novembre 2022 à 23:42 +, Dominic Irving a écrit :
> %{
> The positions property of the slur is in units of staff-spaces,
> but this calculation should be scaled according to the current
> 'magnifyStaff' value.
>
> Expected behaviour: the scores all
On 17/03/2023 16:26, David Kastrup wrote:
That is not a minimal example. Try
\new Staff \with { \consists "Custos_engraver" } { 1 }
Of course, I should have thought of that.
Best, Simon
Hi Jean,
On 17/03/2023 16:38, Jean Abou Samra wrote:
Thanks, but you already reported that bug about a year ago.
Thanks for digging that up/remembering. I did search the issue database
for ‘custos crash’ (or ‘crash custos’ maybe), but despite the label
“Crash” issue 6327 didn’t show up.
Le vendredi 17 mars 2023 à 16:12 +0100, Simon Albrecht a écrit :
> Hello everyone,
>
> found this while creating a minimal example. The following code crashes
> on both 2.24.0 and 2.25.2:
>
>
> \version "2.24.0"
>
> \new Staff \with {
> \consists Custos_engraver
> }
Simon Albrecht writes:
> Hello everyone,
>
> found this while creating a minimal example. The following code
> crashes on both 2.24.0 and 2.25.2:
>
>
> \version "2.24.0"
>
> \new Staff \with {
> \consists Custos_engraver
> } { 1 \break r1 1 }
>
>
> Not sure
samarutuk via bug-lilypond writes:
> Hi, the margins must also fit the printer specifications. If you
> choose e.g. 2 mm for top, bottom, left or right, many printers will
> not be able to print that, because there is a minimum margin depending
> on the printer. Acrobat will then adjust the
Il giorno ven 3 mar 2023 alle 11:45:08 +0100, Jean Abou Samra
ha scritto:
Le vendredi 03 mars 2023 à 11:26 +0100, Ruben du Pon a écrit :
That may be the case, but as I said when I print straight from
Frescobaldi the score doesn't fit the page (the bottom staff is
mostly missing) and when
Hi, the margins must also fit the printer specifications. If you choose
e.g. 2 mm for top, bottom, left or right, many printers will not be able
to print that, because there is a minimum margin depending on the
printer. Acrobat will then adjust the document to fit the printer (89%
in your
> Le 3 mars 2023 à 11:45, Jean Abou Samra a écrit :
>
>
>>
>> Le vendredi 03 mars 2023 à 11:26 +0100, Ruben du Pon a écrit :
>>
>> That may be the case, but as I said when I print straight from Frescobaldi
>> the score doesn't fit the page (the bottom staff is mostly missing) and when
Le vendredi 03 mars 2023 à 11:26 +0100, Ruben du Pon a écrit :
> That may be the case, but as I said when I print straight from Frescobaldi
> the score doesn't fit the page (the bottom staff is mostly missing) and when
> I open it in acrobat reader it fits at 89%, so something is off about the
That may be the case, but as I said when I print straight from Frescobaldi
the score doesn't fit the page (the bottom staff is mostly missing) and
when I open it in acrobat reader it fits at 89%, so something is off about
the paper size.
Op vr 3 mrt. 2023 11:13 schreef Jean Abou Samra :
>
(Please keep the list CCed)
Le vendredi 03 mars 2023 à 11:08 +0100, Ruben du Pon a écrit :
> I am using Frescobaldi. If I print straight from there the score doesn't fit
> the paper. If I open the pdf in Acrobat Reader and print with the 'fitting'
> setting it adjusts to 89%. If I print at 100%
Le vendredi 03 mars 2023 à 10:31 +0100, Ruben du Pon a écrit :
> Hi!
> I just made a score using Lilypond.
> However, when printing I need to print the pdf at 90% scale to fit it to
> standard A4 paper.
> According to the documentation A4 should be the standard paper size, and I
> did
Gould illustrates this happening for beamed quavers (page 64), but doesn't
address this exact case of crotchets that I can find.
Paul
From: Simon Albrecht
To: Lilypond bug list
Sent: 28/02/2023 11:41
Subject: Melody_engraver and tied notes
Hello everyone,
Thanks, gentlemen, for the impressively rapid response/fix. It does,
indeed, seem to function correctly. Sorry I misunderstood the
"officialness" of snippets but I'm definitely grateful to have the
function again.
I do the engraving of the scores we use in our village chorale and
really
Am Di., 14. Feb. 2023 um 22:06 Uhr schrieb Jean Abou Samra :
>
> Le mardi 14 février 2023 à 19:55 +0100, Craig Fearing a écrit :
> > The attached file is a minimized version of an official snippet.
> >
> > If run as version 2.25.*0* it compiles perfectly.
> >
> > If run as version 2.25.*1* it
Le mardi 14 février 2023 à 19:55 +0100, Craig Fearing a écrit :
> The attached file is a minimized version of an official snippet.
>
> If run as version 2.25.*0* it compiles perfectly.
>
> If run as version 2.25.*1* it fails.
The snippet comes from LSR and is not tagged as a doc snippet,
Just want to follow up — is there an issue tracked for this one? Thanks
On Tue, Feb 7, 2023 at 9:00 AM Saul Tobin
wrote:
> Thanks!
>
> On Sun, Feb 5, 2023, 2:37 PM Jean Abou Samra wrote:
>
>> On 05/02/2023 22:13, Saul Tobin wrote:
>> > \version "2.24.0"
>> >
>> > \paper {
>> > ragged-bottom
Thanks!
On Sun, Feb 5, 2023, 2:37 PM Jean Abou Samra wrote:
> On 05/02/2023 22:13, Saul Tobin wrote:
> > \version "2.24.0"
> >
> > \paper {
> > ragged-bottom = ##t
> > }
> >
> > \layout {
> > \context {
> > \Score
> > \override Glissando.breakable = ##t
> > \override
On 05/02/2023 22:13, Saul Tobin wrote:
> \version "2.24.0"
>
> \paper {
> ragged-bottom = ##t
> }
>
> \layout {
> \context {
> \Score
> \override Glissando.breakable = ##t
> \override Glissando.after-line-breaking = ##t
> }
> }
>
> global = {
> s1
> \pageBreak
> s1
> }
(CC'ing Alen Šiljak, the author of the weinberg-drums-style)
On Wed, 2023-02-01 at 10:09 -0800, Stu McKenzie wrote:
> I'm referring to the web page
> https://lilypond.org/doc/v2.24/Documentation/changes/ where it is stated
> that
> "The drum notation style weinberg-drums-style was added. It is
On 01/02/2023 11:12, Jean Abou Samra wrote:
> Saul,
>
>
>> Le 1 févr. 2023 à 04:16, Saul Tobin a écrit :
>>
>> The fourth example engraver here:
>> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example
>>
>> Running this code in 2.24 crashes on
Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin
:
>
> The fourth example engraver here:
> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example
>
> Running this code in 2.24 crashes on initializing the engraver with In
> procedure
> Le 1 févr. 2023 à 11:23, Thomas Morley a écrit :
>
> Am Mi., 1. Feb. 2023 um 04:16 Uhr schrieb Saul Tobin
> :
>>
>> The fourth example engraver here:
>> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example
>>
>> Running this code in 2.24
Saul,
> Le 1 févr. 2023 à 04:16, Saul Tobin a écrit :
>
> The fourth example engraver here:
> https://extending-lilypond.readthedocs.io/en/latest/extending/translation.html#fourth-engraver-example
>
> Running this code in 2.24 crashes on initializing the engraver with In
> procedure
On 30/01/2023 05:36, David Zelinsky wrote:
> Is there any benefit in adding a regression test? It compiles
> correctly, it's just the warning that is bogus. Is this detected in
> regressing testing?
Yes, the log is captured for each test. If the log
differs in a "make check" run, it will be
Am Mi., 25. Jan. 2023 um 17:54 Uhr schrieb David Kastrup :
>
> Stu McKenzie writes:
>
> > There seems to have been various reports of bugs when the first note
> > is a grace note, but this bug has been in many LilyPond versions to
> > date.
> >
> > When the first note of a drum score has a grace
Stu McKenzie writes:
> There seems to have been various reports of bugs when the first note
> is a grace note, but this bug has been in many LilyPond versions to
> date.
>
> When the first note of a drum score has a grace note, LilyPond outputs
> the default note, rather than the custom
On 25/01/2023 15:10, Michael Käppler wrote:
> Hi all,
> I'm posting to bug-lilypond instead of opening an issue in the tracker,
> because
> I'm not sure if the behaviour is somehow intended or a bug.
> Consider the following example:
>
> \version "2.24.0"
> {
> \time 2/4
> d''8 r e''4 |
> (
201 - 300 of 28975 matches
Mail list logo
