On Mon, 20 Nov 2023 at 05:15, Abe Raher wrote:
>
> p.s. This story ended oddly.
>
> I uninstalled ghostscript and then installed ghostscript 10.02.0.
>
> I pinned that version.
>
> Still got the error ...
>
> Uninstalled lilypond.
>
> Reinstalled lilypond – this required unpinning ghostscript.
>
On 20 Nov 2023, at 04:02, Abe Raher wrote:p.s. This story ended oddly.I uninstalled ghostscript and then installed ghostscript 10.02.0.I pinned that version.Still got the error ...Uninstalled lilypond.Reinstalled lilypond – this required unpinning ghostscript.Now it's all working. Odd because
p.s. This story ended oddly.
I uninstalled ghostscript and then installed ghostscript 10.02.0.
I pinned that version.
Still got the error ...
Uninstalled lilypond.
Reinstalled lilypond – this required unpinning ghostscript.
Now it's all working. Odd because we're back to the latest
Hello again list,
Is it possible to configure the bar number engraver so that *in addition to*
its regular behaviour, whatever that may be defined as*, it will also print
a bar number after a multi-measure rest?
Thank you.
* I usually go with
\set Score.barNumberVisibility =
Updating to the latest version fixed the issue, and also the unwanted
extra space. Problem was just Debian shipping a very old version for
some reason.
Thank you for your help.
On Mon, 20 Nov 2023 at 00:12, William Rehwinkel
wrote:
>
> Dear Robert,
>
> in the future, please take care that the
On Mon, 20 Nov 2023 at 00:12, William Rehwinkel
wrote:
>
> Dear Robert,
>
> in the future, please take care that the minimal working example does
> not contain any undefined symbols that cause errors. Here, simply adding
> "strike = \fermata" at the beginning of the file alleviated all these
>
Dear Robert,
in the future, please take care that the minimal working example does
not contain any undefined symbols that cause errors. Here, simply adding
"strike = \fermata" at the beginning of the file alleviated all these
errors, however.
After using convert-ly and rendering (using
Hi people. I'm trying to reproduce the formatting from a tune that
started out in ABC notation, which is formatted with line breaks
around phrases instead of bars. It is working as intended, except for
an empty bar that's showing up after the first repeat sign, and I have
no idea what's causing
Am So., 19. Nov. 2023 um 15:30 Uhr schrieb Michael Gerdau :
>
> Hi lilyponders!
>
> the attached fairly short script creates 4x the aforementioned error. It
> seems to be created by the combined
>\tweak Parentheses.font-size #2 \parenthesize
>
> The resulting score looks basically fine
We are proud to announce the release of GNU LilyPond 2.24.3. LilyPond
is a music engraving program devoted to producing the highest-quality
sheet music possible. It brings the aesthetics of traditionally
engraved music to computer printouts.
This version contains a number of fixes since the
Hi lilyponders!
the attached fairly short script creates 4x the aforementioned error. It
seems to be created by the combined
\tweak Parentheses.font-size #2 \parenthesize
The resulting score looks basically fine (AFAICT) but I guess this error
should not occur anyway.
This happens both
11 matches
Mail list logo