> Regarding this sentence - in a man page it simply does not make
> sense, even if I'm not a native speaker either.
Ah, yes, you are right, I didn't think about the transformation to a
man page. I agree, the sentence should be massaged by `help2man`.
Funnily, even `help2man.1` has
```
--help
t is not what GNU programs like `rm`, `ls`, or `dir`
> >> do. I'm not going to change it for this reason.
> >
> > Ok. This again is a limitation of help2man.
>
> No, it is not – in this case I'm simply following what prominent GNU
> programs do (since
>
> Ok. This again is a limitation of help2man.
No, it is not – in this case I'm simply following what prominent GNU
programs do (since LilyPond is a GNU project, too). I'm not a native
speaker (ich bin Wiener :-) and I trust that the US-maintainers of
those packages know what they do.
Werner
Hello Werner,
Am Mon, Oct 07, 2024 at 05:41:39AM + schrieb Werner LEMBERG:
> > Man page: abc2ly.1
> > Issue 1: abc2ly → B
>
> I presume that you are talking about `abc2ly` not printed as bold in
> the `DESCRIPTION` section of the man page.
Yes.
> We are using `help2man` (version 1.47.4, but
r this issue), and this is what we get.
> Issue 2: The link is no longer correct?
> http://abcnotation.com/wiki/abc:standard
This is already fixed in the development version of LilyPond.
> Man page: abc2ly.1
> Issue:this help → a help screen
>
> "show this help and e
Dear lilypond maintainer,
the manpage-l10n project maintains a large number of translations of
man pages both from a large variety of sources (including lilypond) as
well for a large variety of target languages.
During their work translators notice different possible issues in the
original
Source: lilypond
Version: 2.24.1-2
Severity: minor
X-Debbugs-Cc: bug-lilypond@gnu.org
Dear Maintainer,
on https://manpages.debian.org/testing/lilypond/abc2ly.1.en.html is a
reference to the abc standard applicable for this software. The related
sentence is
"abc2ly converts ABC music files
Thank you- good points, RE backups and copyrights.
Similar punishment!
Sent with Proton Mail secure email.
On Sunday, March 3rd, 2024 at 12:00 PM, bug-lilypond-requ...@gnu.org
wrote:
> Send bug-lilypond mailing list submissions to
> bug-lilypond@gnu.org
>
> To subscribe or uns
Cameron Crowe via bug-lilypond writes:
> Just a thought--not a bug.
>
> lilypond-book refuses to overwrite a main source file, but happily
> overwrites secondary source files included into the main source
> file. Irritating if you use the .tex extension for included chapters
>
Just a thought--not a bug.
lilypond-book refuses to overwrite a main source file, but happily overwrites
secondary source files included into the main source file. Irritating if you
use the .tex extension for included chapters of a musicological document and
even just accidentally call
> lilypond-book accepts --loglevel=WARN, but not --loglevel=WARNING.
>
> I think WARN is for lilypond, not lilypond-book (according to the
> documentation), so maybe just misdocumented?
Indeed, it is incorrectly documented; it should be 'WARN' everywhere.
Note that th
lilypond-book accepts --loglevel=WARN, but not --loglevel=WARNING.
I think WARN is for lilypond, not lilypond-book (according to the
documentation), so maybe just misdocumented?
Using 2.24.3
Thank you,
C
>> lilypond-book --loglevel=WARN book.lytex
> lilypond-book: error: file
Dear Lilypond team,
Using GNU LilyPond 2.24.1 (running Guile 2.2), the following example seems to
generate a note visibility bug:
\version "2.24.1"
\language "english"
\book {
\score {
\new Staff = "LH" \with { printPartCombineTexts = ##f } {
\t
This is now
https://gitlab.com/lilypond/lilypond/-/issues/6691
Am 26.01.2024 um 20:32 schrieb Werner LEMBERG:
I would like to hear your opinions on this one:
snip
\version "2.25.10"
{ \acciaccatura { c'8 } d'4 }
{ \appoggiatura { c'8 } d'4 }
%%
Hi Knute,
no worries.
I think this list is exactly the right place to discuss, whether some
behaviour
should be considered a bug or not.
That was the reason I wrote here in the first place.
Otherwise I simply would have opened an issue on GitLab.
Michael
Am 26.01.2024 um 21:05 schrieb Knute Sn
On Fri, Jan 26, 2024 at 11:53 AM Werner LEMBERG wrote:
>
> >> > The hyperlinks of both the acciaccatura and the appoggiatura
> >> > slurs point to ly/grace-init.ly, which is kind of logical, but
> >> > also confusing from a user perspective.
> >>
> >> I think this a bug, so please open an issue.
>> > The hyperlinks of both the acciaccatura and the appoggiatura
>> > slurs point to ly/grace-init.ly, which is kind of logical, but
>> > also confusing from a user perspective.
>>
>> I think this a bug, so please open an issue.
>
> I apologise.
Why?
Werner
I apologise.
--
Knute Snortum
On Fri, Jan 26, 2024 at 11:33 AM Werner LEMBERG wrote:
>
> > I would like to hear your opinions on this one:
> >
> > snip
> > \version "2.25.10"
> >
> > { \acciaccatura { c'8 } d'4 }
> > { \appoggiatura { c'8 } d'4 }
> >
> >
> >
> I would like to hear your opinions on this one:
>
> snip
> \version "2.25.10"
>
> { \acciaccatura { c'8 } d'4 }
> { \appoggiatura { c'8 } d'4 }
>
>
> The hyperlinks of both the acciaccatura and the appoggiatura slurs
> point to ly/grace-init.ly, which is kin
Hi Michael,
These sorts of questions should go to another list,
lilypond-u...@gnu.org
This list is only for reporting bugs.
--
Knute Snortum
On Fri, Jan 26, 2024 at 5:48 AM Michael Käppler via bug-lilypond <
bug-lilypond@gnu.org> wrote:
> Hi all,
> I would like to hear your
Hi all,
I would like to hear your opinions on this one:
snip
\version "2.25.10"
{ \acciaccatura { c'8 } d'4 }
{ \appoggiatura { c'8 } d'4 }
The hyperlinks of both the acciaccatura and the appoggiatura slurs point
to ly/grace-init.ly, which is kind of logical, b
> Am 16.01.2024 um 12:37 schrieb Werner LEMBERG :
>
. . .
>
> You can ignore all of them, they are not relevant, AFAIK. The only
> issue with the 'lilypond' and 'lilypond-devel' bundles from MacPorts
> is what Jean has mentioned:
>
> https://tra
ons if necessary.
> I installed MacPorts which had some issues (beyond your control) to
> use that installer, and it appears I've finished, but the list of
> notes is extensive and I thought I'd share that with you. [...]
You can ignore all of them, they are not relevant, AFAIK
ut which are important and which are just
> notes.
Can you share the issues you've had with the official installation
instructions please?
The MacPorts package is not only out of our control, but also
broken (it's missing fonts), and they haven't fixed it in
almost a year (sigh). If
layer for GNU libidn.
libpsl has the following notes:
libpsl API documentation is provided by the port 'libpsl-docs'.
lilypond has the following notes:
Pre-installation note for 'mactex' variant:
MacTeX or another external TeXLive distribution gets used for
> Also, I'm pretty sure that the intent of FcChar8* in Fontconfig is
> to represent UTF-8 so this is probably worthy of a bug report to the
> Fontconfig people?
Indeed. To do so it would be helpful to check the output of `fc-list`
(ideally with proper patterns to make the result more similar to
> I can confirm that replacing
>
> scm_write_line (ly_string2scm (str), port);
>
> with
>
> scm_c_write (port, str.c_str (), str.length ());
>
> fixes the issue on my end. I’d be happy to make a merge request for
> this.
I've updated
https://gitlab.com/lily
I can confirm that replacing
scm_write_line (ly_string2scm (str), port);
with
scm_c_write (port, str.c_str (), str.length ());
fixes the issue on my end. I’d be happy to make a merge request for this.
> On Jan 13, 2024, at 6:19 PM, Jean Abou Samra wrote:
>
>> I don't have the time to check t
> I don't have the time to check this but is there not a way to simply write
> bytes to (current-error-port) in Guile?
Like scm_c_write
< https://www.gnu.org/software/guile/manual/html_node/Using-Ports-from-C.html >
?
signature.asc
Description: This is a digitally signed message part
Le vendredi 12 janvier 2024 à 06:08 +, Werner LEMBERG a écrit :
> How shall we proceed?
I don't have the time to check this but is there not a way to simply write bytes
to (current-error-port) in Guile? IIRC, all Guile ports can be used in both
binary and text ways.
Also, I'm pretty sure that
Le mardi 09 janvier 2024 à 12:43 -0500, Nate Whetsell a écrit :
> I’m starting to think this may be a bug in Guile.
Well, Guile's encoding handling is quite bug-ridden.
signature.asc
Description: This is a digitally signed message part
> Can you make your example code generic and report it to the Guile people?
Done.
> How shall we proceed?
Because this issue occurs with a macOS system font, it it likely to impact most
(possibly all) LilyPond users on macOS. Consequently, it may be necessary to
revert
be a bug in Guile.
Can you make your example code generic and report it to the Guile
people?
> When I use a conversion strategy of 'substitute, the conversion
> works as expected (with a � where the encoding issue occurs). When
> I use the default strategy ('error, presumabl
Thanks for making the merge request. Unfortunately, it didn’t fix the issue,
although it really seems like it should have. I’m starting to think this may be
a bug in Guile.
With the patch applied, running `lilypond -dshow-available-fonts` outputs:
GNU LilyPond 2.25.12 (running Guile 3.0)
ERROR
> On macOS Ventura v13.6.3 (and almost certainly other versions), the
> string produced when using -dshow-available-fonts need not be
> encoded as UTF-8.
Thanks, should be fixed with this MR:
https://gitlab.com/lilypond/lilypond/-/merge_requests/2231
Out of interest: Which font s
Hi there,
At commit c3f2dddaa2b16231bc2f786fba7421f03f7da7af
<https://gitlab.com/lilypond/lilypond/-/commit/c3f2dddaa2b16231bc2f786fba7421f03f7da7af>,
All_font_metrics::display_fonts was changed
<https://gitlab.com/lilypond/lilypond/-/commit/c3f2dddaa2b16231bc2f786fba7421f
g me to the previous
discussion on this topic, I wasn't aware of these changes until now.
I'll start including those two lines after including
lilypond-book-preamble when wanting the cropping behaviour from now on.
Best wishes!
Gilberto
ts=eps,png,pdf
Here is where I got my knowledge from:
https://gitlab.com/lilypond/lilypond/-/issues/6235
Hope this helps,
Klaus
Hello everyone,
I hope you are all well and had a great year. I noticed that since
version 2.24.x, lilypond-book-preamble has stopped automatically
cropping the output around the music grobs.
*1) *This is the behaviour of 2.22.2, which is what I expect when using
lilypond-book-preamble
:28, Jean Abou Samra
wrote:
> Le dimanche 24 septembre 2023 à 09:21 +, Ole V. Villumsen via
> bug-lilypond a écrit :
>
>> \version "2.24.2"
>>
>> \relative {
>> g'1 |
>> % The following has no effect.
>> \override Score.S
Le dimanche 24 septembre 2023 à 09:21 +, Ole V. Villumsen via bug-lilypond a
écrit :
> \version "2.24.2"
>
> \relative {
> g'1 |
> % The following has no effect.
> \override Score.SpacingSpanner.strict-grace-spacing = ##t
> \grace { a4 } g1 |
&
As a consequence we cannot change this property dynamically in the course of
the score.
Context: My score contains all of \grace, \acciaccatura, \appoggiatura,
\slashedGrace and \afterGrace. I want the first four to have the space that
Lilypond assigns to them by default. I do not want \aft
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:
\ve
Code:
\version "2.24.1"
\new ChoirStaff \relative c {
% breve rest has lines on either side, like a normal breve note, when it
shouldn't c\breve\rest
}
By Matrix :)
>> Running this code in 2.24 crashes on initializing the engraver with In
>> procedure ly:spanner-set-bound!: Wrong type argument in position 3
>> (expecting Item): ().
>
>
> Thanks for the report. I suppose you did not realize that this “Extending
> LilyPond” re
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 ly:spanner-set
able in the initialize-step of an engraver.
> Not the time to bisect when and why this happened,
It’s this:
https://gitlab.com/lilypond/lilypond/-/commit/7a09ffee2c69ab9617289afd21dae1b9198a9fee
Perfectly intentional.
Also, reading it in initialize was a bad idea in 2.22 in the first place. T
ith In
> procedure ly:spanner-set-bound!: Wrong type argument in position 3
> (expecting Item): ().
Thanks for the report. I suppose you did not realize that this “Extending
LilyPond” resource is not part of the official documentation, it’s something I
wrote up and maintain externally (unlike the o
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 ly:spanner-set-bound!: Wrong type argument in position 3
(expecting Item): ().
% Using the snippet below (from the official webpage), when I added a
measure rest at
% the beginning of Coda, an additional measure rest is printed out the
staff (close to "D.S...").
% It doesn't happen in the equivalent snippet from version 2.18.2.
\version "2.24.0"
{
\relative c'' {
c4 c
e all the breath marks now available listed,
the "old" one is not there:
https://lilypond.org/doc/v2.23/Documentation/notation/list-of-breath-marks
kind regards
Andreas
Am 12.11.2022 um 10:19 schrieb Mark Knoop:
At 10:10 on 12 Nov 2022, samarutuk via bug-lilypond wrote:
Dear all, when
At 10:10 on 12 Nov 2022, samarutuk via bug-lilypond wrote:
> Dear all, when I tried version 2.23.80 for the first time yesterday, I
> was absolutely shocked to see the new, very mundane comma as a breath
> mark when rendering. I know that other notation programs also use the
> comma
.
Kind regards
Andreas
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Hi all,
I know the topic itself is not new, and I am aware that lilypond can't
easily take advantage from multiple CPU cores as the way it "compiles"
lilypond notation into a final pdf file does not allow for it.
But there could be an exception to be used for it: Slicing a (big
t;> What is the problem you are encountering? I think that normally, it
>> should work on all 64-bit-capable Macs.
>
>
> I don't run LilyPond at the command line, but I use Frescobalidi.
>
> When I extract the files from lilypond-2.23.10-darwin-x86_64.tar.gz and
> p
I think that normally, it
should work on all 64-bit-capable Macs.
I don't run LilyPond at the command line, but I use Frescobalidi.
When I extract the files from lilypond-2.23.10-darwin-x86_64.tar.gz
and place it in my Applications folder, then point Frescobald to
lilypond in bin/ , I get t
all 64-bit-capable Macs.
I don't run LilyPond at the command line, but I use Frescobalidi.
When I extract the files from lilypond-2.23.10-darwin-x86_64.tar.gz and
place it in my Applications folder, then point Frescobald to lilypond in
bin/ , I get the following error:
Traceback (most
blem is that repeats now support
putting the
>> \alternative phrase inside of the construct since that is a
saner way of
>> doing things. But the previous way is still supported for
compatibility
>> reasons. Your input file could be interpreted eithe
Le 02/05/2022 à 08:50, Stéphane SOPPERA a écrit :
Hi,
This very basic program reproduce the issue:
#(error "test")
\relative {
c'1 |
}
With Lilypond 2.20, the compilation produces:
Processing `scheme_err.ly'
Parsing...
scheme_err.ly:1:2: error: GUILE signaled an erro
Hi,
This very basic program reproduce the issue:
#(error "test")
\relative {
c'1 |
}
With Lilypond 2.20, the compilation produces:
Processing `scheme_err.ly'
Parsing...
scheme_err.ly:1:2: error: GUILE signaled an error for the expression
beginning here
#
(error &qu
Thanks Jean for the detailed answer!
Regarding having custom versions of functions & macros that defines
functions & procedures, I would prefer avoiding doing so even though I
already do so for macros and classes to attach documentation strings
(https://github.com/soppera/lilypond
Le 01/05/2022 à 20:29, Stéphane SOPPERA a écrit :
Hi,
While trying to make sure my automatic documentation generation code
works with Lilypond 2.23.8 (and especially Guile 2.2) I noticed a bug
that may be due to how Lilypond is using Guile 2.2.
The current version of my code uses /(p
Hi,
While trying to make sure my automatic documentation generation code
works with Lilypond 2.23.8 (and especially Guile 2.2) I noticed a bug
that may be due to how Lilypond is using Guile 2.2.
The current version of my code uses /(p//rocedure-source)/
<https://github.com/soppera/lilyp
Am 12.01.2022 um 20:02 schrieb Stu McKenzie:
Environment: Microsoft Windows 10 Home, Version 10.0.19043 Build 19043.
I've installed the following versions of LilyPond, with the result
listed:
Version Result
2.20.0 does not add blank lines.
2.22.0 adds blank lines.
2.22.1 adds blank
There's been discussion about a similar issue during 2016, but this is
the first time in years that I've tried to upgrade to the latest version.
Environment: Microsoft Windows 10 Home, Version 10.0.19043 Build 19043.
I've installed the following versions of LilyPond, with th
Hello,
On 05/12/2021 21:25, K. Blum wrote:
Hello,
on Windows 10 with LilyPond 2.23.35 I noticed a problem:
lilypond-book-preamble.ly doesn't produce an auto-cropped image.
The following snippet
% -
\include "lilypond-book-pream
Le 06/12/2021 à 17:02, Johannes Feulner a écrit :
When running lilypond on LY-input broken.ly (s. below), lilypond
crashes with SIGSEGV and a temporary file named like
broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note
on/off events.
\version
Hello,
On 06/12/2021 16:02, Johannes Feulner wrote:
When running lilypond on LY-input broken.ly (s. below), lilypond
crashes with SIGSEGV and a temporary file named like
broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note
on/off events.
\version
When running lilypond on LY-input broken.ly (s. below), lilypond crashes
with SIGSEGV and a temporary file named like broken.midi.0123abcd remains.
The desired output would be a correct MIDI file without any note on/off
events.
\version "2.22.0"
\score {
\new voice {
Hello,
on Windows 10 with LilyPond 2.23.35 I noticed a problem:
lilypond-book-preamble.ly doesn't produce an auto-cropped image.
The following snippet
% -
\include "lilypond-book-preamble.ly"
{c}
% -
should
Hi Andreas,
thanks for reporting.
I added this issue as
https://gitlab.com/lilypond/lilypond/-/issues/6213
to the tracker.
A fix is in preparation.
Michael
Am 04.11.2021 um 17:21 schrieb Andreas K. H. von Rüden:
This should be included.
___
bug
Hello,
using lilypond 2.20.0 on Ubuntu 20.04, lilypond-book worked perfectly. After
Update to Ubuntu 21.10 and lilypond 2.22.1, lilypond-book crashes, when the
lytex-file contains the \input command.
Here's an MWE:
lytex-file:
---
\documentclass{scrartcl}
\begin{document}
\input{bugtest}
Jean Abou Samra writes:
> (Sorry, not replying to all was an oversight.)
>
> On 16/10/2021 17:31, Dan Eble wrote:
>> On Oct 16, 2021, at 10:58, Jonas Hahnfeld via Discussions on
>> LilyPond development wrote:
>> >
>> > in my opinion we want to
>>
(Sorry, not replying to all was an oversight.)
On 16/10/2021 17:31, Dan Eble wrote:
On Oct 16, 2021, at 10:58, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> in my opinion we want to
> send users to the mailing list by default.
I don't devote much time to
On 10/16/21, 4:55 AM, "lilypond-devel on behalf of Jean Abou Samra"
wrote:
A factor to consider is that, as far as I can read
http://lilypond.org/bug-reports.html (but I can't
remember how it worked for myself), posting to
bug-lilypond requires being su
On Oct 16, 2021, at 10:58, Jonas Hahnfeld via Discussions on LilyPond
development wrote:
>
> in my opinion we want to
> send users to the mailing list by default.
I don't devote much time to handling bugs (until I'm tagged), but the reports
that have come directly through
ile-devel.
> > > So I finally sent it to bug-guile, where nobody
> > > reacted either. I feel safer having dumped it
> > > on the Guile bug tracker (through bug-guile) because
> > > when in 2 years (let's hope...) Guile gets
> > > developers who look
en in 2 years (let's hope...) Guile gets
developers who look at bug reports, they might
notice it.
Pointing to bad experiences with other projects is not exactly a
convincing argument to me with respect to LilyPond.
I gave an example with a LilyPond user above.
Given that I have for so
und a lot in the tracker, including
> > > 10-year-old issues, and sometimes they give
> > > nice ideas. \vshape was born like that.)
> > In my opinion, this is a very weak argument: The archives of bug-
> > lilypond go back more than 20 years (first month is 2001-07). This is
&g
Le 16/10/2021 à 14:28, David Kastrup a écrit
bug-lilypond@gnu.org is not a subscribers-only list and it is expected
that responses include a Cc: to the sender.
Ah, ok. I had inferred the contrary from
http://lilypond.org/bug-reports.html
b) read up on the categories and flags we use for
ur work on bug reports, but I had the impression that
>>> most often the issue was made just from the email thread. That's
>>> also what I usually do. To be clear, I am not proposing that we
>>> change anything to the way we respond to bug reports (discussing
>>>
developers walking around
> there than let it be forgotten about. (I do
> walk around a lot in the tracker, including
> 10-year-old issues, and sometimes they give
> nice ideas. \vshape was born like that.)
In my opinion, this is a very weak argument: The archives of bug-
lilypond go ba
anything to the
way we respond to bug reports (discussing whether it's a bug,
pointing to documentation, etc.) which is handled very well as it is.
It just appears to me that the bug-lilypond mailing list is redundant
as the same tasks can be done better via the issue tracker.
I disagree. &q
y do.
>
> To be clear, I am not proposing that we change
> anything to the way we respond to bug reports
> (discussing whether it's a bug, pointing to
> documentation, etc.) which is handled very well
> as it is. It just appears to me that the bug-lilypond
> mailing lis
Hi James, Werner, all,
Le 14/10/2021 à 08:43, James a écrit :
Hello,
My own thoughts on this.
On 14/10/2021 01:31, Jean Abou Samra wrote:
Hi,
After having opened a few GitLab issues in response to
bug reports on bug-lilypond, I find James extraordinarily
patient for having done this over
er.
Regards
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> After having opened a few GitLab issues in response to bug reports
>> on bug-lilypond, I find James extraordinarily patient for having
>> done this over the years. However, I don't get the value in this
>> system compared to letting people creating issues on
Hello,
My own thoughts on this.
On 14/10/2021 01:31, Jean Abou Samra wrote:
Hi,
After having opened a few GitLab issues in response to
bug reports on bug-lilypond, I find James extraordinarily
patient for having done this over the years. However, I don't
get the value in this system com
Hi,
After having opened a few GitLab issues in response to
bug reports on bug-lilypond, I find James extraordinarily
patient for having done this over the years. However, I don't
get the value in this system compared to letting people
creating issues on GitLab directly. When we transfer an
t;>> I was under some pressure to get this working for a client, who
>>>> was unfortunately on Mac OS Catalina. I tried importing xml files
>>>> with many many different combinations of Lilypond and
>>>> Frescobaldi. The only combination I could ge
r a client, who
> > > was unfortunately on Mac OS Catalina. I tried importing xml files
> > > with many many different combinations of Lilypond and
> > > Frescobaldi. The only combination I could get to work was with
> > > Frescobaldi 3.1.2 and an "unofficia
gt;> many many different combinations of Lilypond and Frescobaldi. The
>> only combination I could get to work was with Frescobaldi 3.1.2 and
>> an "unofficial" build of Lilypond from this link
>> https://gitlab.com/marnen/lilypond-mac-builder/-
>> /releases/v2.20.0.build
Am Dienstag, dem 12.10.2021 um 16:02 -0400 schrieb Jim Weisbin:
> I was under some pressure to get this working for a client, who was
> unfortunately on Mac OS Catalina. I tried importing xml files with
> many many different combinations of Lilypond and Frescobaldi. The
> only combina
I was under some pressure to get this working for a client, who was
unfortunately on Mac OS Catalina. I tried importing xml files with many many
different combinations of Lilypond and Frescobaldi. The only combination I
could get to work was with Frescobaldi 3.1.2 and an "unofficial"
ks on these lists
> > but it might be worth pinging him directly.
> >
> > There are a number of ways - https://frescobaldi.org/links.
> >
> > Regards
> >
> > James
>
> It has been reported independently at
> https://gitlab.com/lilypond/lilypond/-
i.org/links.
Regards
James
It has been reported independently at
https://gitlab.com/lilypond/lilypond/-/issues/6189,
where Jonas diagnosed a problem in MacPorts' Python.
Best,
Jean
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lis
James
Lilypond 2.22.1 installed via Macports, works. Frescobaldi v 3.1.3 installed
via the DMG works. But fails to import MusicXML files with this error:
Starting musicxml2ly...
Python path configuration:
PYTHONHOME = '/Applications/Fresc
Dear list,
For now, lilypond-book leaves the raw LilyPond book in the XML file after
its processing. If this is the DocBook input
http://docbook.org/ns/docbook";
xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:m="
http://www.w3.org/1998/Math/MathML"; xmlns:xi
Dear lilypond team.
I recently acquired a new iMac, with Mac OS 11.5.1, and I’ve managed to migrate
most of my software and data from its predecessor. Unfortunately neither
lilypond nor Frescobaldi falls into that group.
I’ve used git to clone lilypond, but am struggling to get it compiled
Hello
On 06/02/2021 18:41, Daniel Connors wrote:
The python script lilypond-book.py can hang on Windows if the user's
Windows user_id is longer than 8 characters and the user's default Windows
temporary directory is in C:\Users\. This is because of an old,
legacy DOS filename conv
1 - 100 of 19862 matches
Mail list logo
