Le samedi 23 mars 2024 à 16:02 +0100, Jonas Hahnfeld via Discussions on
LilyPond development a écrit :
> Native Apple Silicon build: https://cloud.hahnjo.de/s/x9D62eASSn6Ng7D
> This is a native arm64 version for macOS 12+
Great! OOI, what machine did you use for that?
signature.asc
> While revising the documentation for proportional spacing in the NR I
> stumbled upon
>
> ```
> \override PaperColumn.used = ##t
> ```
>
> that gets mentioned without any explanation. Looking up some
> discussion in `lilypond-user` from 2006
>
>
> there is no key signature at this point, right?
This is my interpretation: the key signature is removed by break-visibility,
but the X alignment of a mark is computed before that happens.
signature.asc
Description: This is a digitally signed message part
> I was just waxing nostalgic about that fabulous Salzburg conference in 2020,
> and noted that in Jan 2025 — just under a year from now! — it will have been
> five years since we got together, talked music/notation, and raised [more
> than] a few pints together.
>
> Any chance for a repeat? :)
> It prints
>
> backtrace:
> 0: AgogicLineSpanner.Y-offset (# ly:side-position-interface::y-aligned-side (_ #:optional _)>)
> 1: AgogicLineSpanner.vertical-skylines (# ly:grob::vertical-skylines-from-element-stencils (_)>)
> 2: VerticalAxisGroup.vertical-skylines (#
> Alas, as soon as the relevant engravers are moved to another context,
> which is a common use case, I get an error:
>
> programming error: cyclic dependency: calculation-in-progress
> encountered for AgogicLineSpanner.vertical-skylines
>
> and the graphical output is wrong.
> Again, this does
Le vendredi 02 février 2024 à 20:29 +0100, Éric Würbel a écrit :
> Hi fellow listers
>
> (from a long time user and enthusiast of lilypond from the very first
> released version),
>
> The recent introduction of so called "chord grids" is a long awaited
> feature for me, amateur musician mainly
Le vendredi 26 janvier 2024 à 00:19 +0100, Jean Abou Samra a écrit :
> > Are you getting two copies of my emails?
> >
> > When I send an email to myself, I don't get the blank lines. But there is
> > also a microsoft forwarding that happens when I send an ema
> Are you getting two copies of my emails?
>
> When I send an email to myself, I don't get the blank lines. But there is
> also a microsoft forwarding that happens when I send an email to
> lilypond-devel, and that forwarded email appears to have the blank lines in
> it.
The blank lines don't
> Can someone remind me why the build system sets the C locale
> in the first place?
Answering my own question: I guess it is because we can't assume the
system has an en_US.UTF-8 locale or a C.UTF-8 locale?
Maybe we ought to set only LC_MESSAGES to C? It should prevent overriding
the system
Ah, but, wait.
$ touch àéù.txt
$ guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
$1 = #
~/tmp $ LC_ALL=C guile3.0
scheme@(guile-user)> (open-file "àéù.txt" "r")
ice-9/boot-9.scm:1685:16: In procedure raise-exception:
In procedure open-file: No such file or directory: "??.txt"
Le lundi 22 janvier 2024 à 18:00 -0700, Carl Sorensen a écrit :
> So I ran the file in this log message:
>
>
> carl@carls-mbp-2 build % out/bin/lilypond out/share/lilypond/current/ly/
> init.ly
>
> GNU LilyPond 2.25.13 (running Guile 3.0)
>
> Processing `out/share/lilypond/current/ly/init.ly'
Le mardi 23 janvier 2024 à 01:58 +0100, Jean Abou Samra a écrit :
> The latter is basically that this regtest (pdf-copy-paste.ly)
> has Japanese text, specifying the Noto Serif JP font, but since
> you apparently don't have that font installed, Fontconfig falls
> back to some
Le lundi 22 janvier 2024 à 16:38 -0700, Carl Sorensen a écrit :
> > Looks like no error:
> >
> > carl@Carls-MBP-2 lilypond % build/out/bin/lilypond
> > input/regression/pdf-copy-paste.ly
> > GNU LilyPond 2.25.13 (running Guile 3.0)
> > Processing `input/regression/pdf-copy-paste.ly'
> >
Le lundi 22 janvier 2024 à 21:10 +, Werner LEMBERG a écrit :
> > >
> OK, thanks. This means that there is apparently a macOS-specific
> problem with either Guile or LilyPond. For testing purposes I renamed
> one of my local fonts to something containing Katakana, and my
> self-compiled
> "f" = #(make-music 'AbsoluteDynamicEvent
> 'text "f"
> 'tweaks '(((DynamicLineSpanner . horizon-padding) . 0.1)))
>
> { \stemDown f'4\f f'4\p }
This isn't going to work well anyway. Try it on
{ \stemDown f'1\p\< \break f'2\f r2 }
There is only one
Hi Carl,
> I also tried using HomeBrew (since there is no port for guile3, either).
>
> brew install guile got me a guile 3.0, which I was able to symlink to my
> MacPorts tree, and when I run guile from the prompt, I get guile3.
>
> In the HomeBrew tree there is an include directory:
>
>
You can't -- scm_boolean_p is a C function, not a Guile function.
(It's sort of like trying to access a chocolate as a chocolate box.)
What you can do is to import boolean? from Guile using lily-imports.cc.
signature.asc
Description: This is a digitally signed message part
Probably related to the code and comment in lily/rhythmic-music-iterator.cc.
Looks like it was fixed?
https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7
> What is wrong? The documentation or LilyPond's behaviour?
IMHO the documentation is wrong. Everything's in the name. set-global-staff-size
sets the *global* staff size. Per-\book is not global.
signature.asc
Description: This is a digitally signed message part
> Now m̀ake' fails.
> Offending line in the doc-string is
> The input-string @var{strg} may be composed by any string of \";|.:![]{}\".
> Obviously the braces, { and }, need to be escaped.
> How to?
Like this I think:
... composed of the characters @samp{; | . : ! [ ] @{ @}}
> Ok.
> https://gitlab.com/lilypond/lilypond/-/merge_requests/2179
Oh, I see. You forgot to give it a #:category .
signature.asc
Description: This is a digitally signed message part
Is this a doc build from scratch or an incremental rebuild?
I'd suggest opening the MR anyway.
Le mercredi 15 novembre 2023 à 20:14 +0100, pubabhervegueg...@free.fr a écrit :
>
> Thanks Jean for imagemagick , no more 'convert' error.
> guile-3.0-dev was already installed, I still have guile-devel >= 2.2 missing
> error.
That's a bit strange.
It is very recent that LilyPond looks for
> I ran apt-get install guile-3.0 without improvement.
You also want guile-3.0-dev, which contains C headers and other stuff needed to
compile programs that use Guile, as opposed to merely using programs that use
Guile.
The convert tool should be provided by the imagemagick package.
HTH
Jean
FYI, this migration is now complete.
Jean
signature.asc
Description: This is a digitally signed message part
> “_” needs to be replaced with “G_”. Already in Guile 2, but Guile 3 checks for
> it more eagerly.
Fixed in LSR.
signature.asc
Description: This is a digitally signed message part
> Le 12 nov. 2023 à 19:14, Robin Bannister a écrit :
>
> If I take the code of LSR1098 [1] , without the demo part,
> Guile3 errors the input-warning call:
>
> GNU LilyPond 2.25.10 (running Guile 3.0)
> Processing `1.ly'
> Parsing...
> 1.ly:38:2: error: Guile signaled an error for the
Hi,
This mailing list is for discussing the development of LilyPond. For support
questions, please write to lilypond-user (lilypond-u...@gnu.org) instead.
Thanks,
Jean
signature.asc
Description: This is a digitally signed message part
Le lundi 06 novembre 2023 à 01:11 +0100, David Kastrup a écrit :
> I have not checked recently, but last time I looked, Guile's versioning
> system more or less worked so that the development branch (and the
> corresponding versions) was Andy Wingo's playground. It was not
> concerned with APIs
Le dimanche 05 novembre 2023 à 22:36 +0100, Jonas Hahnfeld via Discussions on
LilyPond development a écrit :
> Please let me know of your comments!
I'm very happy that you got Guile 3.0 working on Windows. Kudos for
that (and I guess we need to send big thanks to Mike Gran too).
What I don't
Le jeudi 26 octobre 2023 à 21:26 +0200, Matthias Kilian a écrit :
> https://lilypond.org/doc/v2.25/Documentation/notation/font-families
>
> still claims that LilyPond still includes URW fonts, which it doesn't
> since 2.24.
It does — otherwise, they could not be set as the default fonts.
If
I think it's a side effect of the mechanism that makes
my-indent = 5
\paper {
indent = #my-indent
}
work.
AFAIK, this is seldom used by Guile coders, though some other Scheme
communities do use this style by convention.
I wouldn't embark on rewriting lots of code/documentation for this; I don't
think the effort pays off.
Le jeudi 19 octobre 2023 à 07:00 +, Dennis Mitchell via Discussions on
LilyPond development a écrit :
> I noticed that the online documentation often uses PNG images of the engraving
> output, rather than SVG images. Now that SVG images are widely supported in
> browsers, perhaps we should
Le dimanche 15 octobre 2023 à 18:39 +, Werner LEMBERG a écrit :
> does localization of, say, `lilypond --help` work on Windows? I've
> tested LilyPond 2.25.9 within `cmd.exe` of a US version of Windows 10
> (i.e., the standard language and region setup is for the USA), and I
> can't make it
Hi,
Not sure how many remember this, but until a few years ago, there
used to be a Web interface to LilyPond lists on a site called “Nabble”,
enabling users to interact with lists without the usual mailing
list “workflow”, which is unfamiliar to many people these days.
(If you find it hard to
> Le 6 oct. 2023 à 12:34, Werner LEMBERG a écrit :
> BTW, can
> you estimate a release date of Frescobaldi that has this new feature?
Long story short, no. Generating the installers is thorny, especially because
it has appeared in private discussions with Jacques Menu that the current
Below is the copy of a discussion on the LilyPond Facebook group that I found
interesting. Just food for thought.
Anonymous Participant: No lilypondinstaller for Macos Monterrey?
Me: What is the issue exactly? As stated on https://lilypond.org/download.html,
the provided downloads support
> Le 30 sept. 2023 à 16:41, Werner LEMBERG a écrit :
>
> The 'ledger-line-thickness' paper variable is set in `paper.scm`. It
> isn't used for anything, AFAICS, and it looks like a historical
> oversight that it wasn't removed.
Yes, that's correct. It doesn't serve a purpose anymore.
>
+1 for removing these
> Le 27 sept. 2023 à 23:33, Peter X a écrit :
>
> Could you kindly guide me on the appropriate channel or procedure to
> formally suggest this feature? I understand that there might be a specific
> format or platform where such suggestions are reviewed and discussed.
Welcome. The procedure
Le samedi 23 septembre 2023 à 14:40 +, Werner LEMBERG a écrit :
> > > Is there ever a situation where `Cairo_outputter::textedit_link` is
>
> > > called? I've set a breakpoint on this function and run over all
>
> > > files in `input/regression`, but there wasn't a single hit...
>
> >
>
Le samedi 23 septembre 2023 à 14:01 +, Werner LEMBERG a écrit :
> Is there ever a situation where `Cairo_outputter::textedit_link` is
> called? I've set a breakpoint on this function and run over all files
> in `input/regression`, but there wasn't a single hit...
Point-and-click. Regtests
Le mercredi 20 septembre 2023 à 05:06 +0200, yuanyelele--- via Discussions on
LilyPond development a écrit :
> In Jianpu, different numbers of underlines are used to indicate note values,
> much like the way beams function in standard staff notation. Therefore, in the
> script, the underlines are
Hi,
Le mardi 12 septembre 2023 à 16:01 -0400, Joseph DiMarino a écrit :
> I have enjoyed Lilypond for many years. I recently got a new computer
> (MacBook Air 2020) and am trying to install Lilypond. The computer seems to
> identify the executables as being for unix. Is it possible that the
Hi,
Gérard, welcome to the list.
Le dimanche 10 septembre 2023 à 21:47 +0200, pubabhervegueg...@free.fr a écrit :
>
>
> Thank you David for your answer.
>
> git-cl is part of setup.sh I downloaded on 2023-08-17 from
> LilyDev-2-debian-vm.zip.
>
> Should I have downloaded instead Lilydev 3,
Le samedi 01 juillet 2023 à 17:01 +0200, Jean Abou Samra a écrit :
> Since yesterday, I've been receiving all posts twice, from all gnu.org mailing
> lists (lilypond-{devel,user,user-fr}). Is this only happening to me? (I did
> fiddle with my mailing list subscriber account recently
Le dimanche 03 septembre 2023 à 14:48 +0200, Jonas Hahnfeld a écrit :
> Can you please
> change it to something more like:
> "IMPORTANT: Binaries and documentation archives are NOT updated on
> lilypond.org anymore, please refer to releases on GitLab instead."
Done.
signature.asc
Description:
> For a possible timeline, we could wait for the release of LilyPond
> 2.25.8 (probably September 16/17 because I'm travelling next weekend,
> unless Jean wants to do it again)
I've recently moved to a new apartment and I doubt I will have Internet
other than through telephone network by next
Le vendredi 01 septembre 2023 à 19:56 +0200, Jonas Hahnfeld a écrit :
> Yes, could be a good idea. Looking at the directory, it seems like the
> contents of README.html are displayed below the list of directories,
> maybe we should use that? If not, we can probably come up with a custom
> solution
> Le 3 sept. 2023 à 06:10, Werner LEMBERG a écrit :
>
> Is there a standardized way to mention the default value of
> `chord-range` in the documentation string, where this default value is
> directly derived from the signature?
No.
Le vendredi 01 septembre 2023 à 16:07 +0200, Jonas Hahnfeld a écrit :
> IIRC it was alluded to when I proposed uploading only the binaries (and
> the documentation) to GitLab: the source archive is used to build for
> various distributions (Linux, Homebrew, MacPorts). They all had (and
> still
Hi,
Per the release procedure
https://lilypond.org/doc/v2.25/Documentation/contributor/release-checklist ,
GitLab releases for LilyPond contain both binaries + doc tarballs and source
tarballs generate by "make dist", while the old download site
lilypond.org/download, which used to host all of
> Le 31 août 2023 à 13:22, Dan Eble a écrit :
>
> My opinion hasn't changed since we instituted the automation. The previous
> discussion is in the archive.
I couldn't find it. Do you happen to have a link at hand?
Le lundi 21 août 2023 à 21:33 -0600, Colin Campbell a écrit :
> The countdown.py script is throwing a unicode error:
>
> PS C:\Lilypond> python countdown.py > 20230823.txt
> Traceback (mos t recent call last):
> File "C:\Lilypond\countdown.py", line 92, in
> print_state(grouped_mrs[state],
Five months later ...
Le samedi 18 mars 2023 à 23:14 +0100, Jean Abou Samra a écrit :
> Le samedi 18 mars 2023 à 16:44 -0500, Karlin High a écrit :
> > Or, maybe it would be better to have all this handled within
> > Frescobaldi instead?
> > Have Frescobaldi look up the lates
Le lundi 31 juillet 2023 à 07:53 +0200, Jonas Hahnfeld a écrit :
> Yes, it has always been there for the online pages because the big-
> pages use language content negotiation and aren't valid file names. You
> can see this by either running an old version through build-doc.sh or
> by looking at
Le lundi 31 juillet 2023 à 22:52 +0200, Jonas Hahnfeld a écrit :
> Right, it also comes up with "brew bundle cleanup"... Did you manually
> install it for your environment during the weekend?
Yes.
> I'm relatively sure I didn't, it may have come in as a dependency in the past
> (even though
>
Le lundi 31 juillet 2023 à 22:29 +0200, Hans Åberg a écrit :
> Apple has patched their version of Flex so that the generated .cc file must be
> used with their header FlexLexer.h.
I don't think this is the problem. Before I installed Flex from Homebrew, the
only Flex installation was the system
> Yes, but flex has always been there as a dependency of some other
> package I think, only not added in your environment variables. We can
> explicitly add it to the Brewfile if you think that's better, but it
> shouldn't change the set of already installed packages.
Hm, I just SSHed into the
We are happy to announce the release of LilyPond 2.25.7. This is termed
a development release, but these are usually reliable for testing new features
and recent bug fixes. However, if you require stability, we recommend using
version 2.24.1, the current stable release.
Downloads are available
Hi,
As a follow-up to the release: on macOS I encountered a quirk which is that the
compiler spit out build errors on the Flex-generated lexer out/lexer.cc. (Now I
find myself stupid for not saving the error messages somewhere.)
I noticed that the macOS-provided flex version (on the MacStadium
Le dimanche 30 juillet 2023 à 19:00 +0200, David Kastrup a écrit :
> It looks to me like the "not accessible" file names are without any file
> extension. That would make it unlikely that their size can be
> determined. Something appears rotten.
I looked into the generated archives, and
Trying to do the release, I got these messages during "./build-doc.sh":
fix-docsize.sh: ../changes-big-page not accessible from
Le vendredi 28 juillet 2023 à 09:42 -0400, Kieren MacMillan a écrit :
> Anyone else have thoughts?
You should read the recent
thread https://lists.gnu.org/archive/html/lilypond-devel/2023-07/msg00028.html .
The desire is pretty similar.
(I don't have more time to spend on this, sorry.)
Le jeudi 27 juillet 2023 à 07:25 -0700, Jason Yip a écrit :
>
> These flags are mostly for a better debugging experience and
> strengthened security. A lot of them are copied from
> https://wiki.gentoo.org/wiki/GCC_optimization
> and some of the configure options added compilation flags that I
>
Le mercredi 26 juillet 2023 à 16:04 -0700, Jason Yip a écrit :
> Carl told me that Lilypond is still trying to maintain capability with
> C++11.
This isn't up-to-date information; as Dan said, we're on C++17 now (and I think
the experiment has lasted long enough without Guile quirks that
> Yes, I deleted the build directory before redoing autogen.sh, redid `mkdir
> build && cd build` in between autogen.sh and configure
Then you failure is pretty strange.
Can you show the output of "build/out/bin/lilypond -V" please? Verbose mode
should give some information about load paths.
I'm not sure we understand "clean build" in the same way. I get that you rerun
autogen and configure, but are you starting from a completely empty build
directory?
signature.asc
Description: This is a digitally signed message part
I also got the compilation error, but after adding , my locally built
LilyPond works fine. Is this from a clean build?
signature.asc
Description: This is a digitally signed message part
Le dimanche 23 juillet 2023 à 23:23 +0200, Valentin Petzel a écrit :
> But I feel that this is a bigger issue. Generally the issue here is that
> systems-per-page only cares about systems of music and not about anything
> else
> that may be placed on the page, as one can see here:
>
> \paper
Le dimanche 23 juillet 2023 à 14:36 -0400, Kieren MacMillan a écrit :
> While we‘re talking about this… :) How difficult would it be to separate
> titling from systems in the spacing engine? I would love it — and I know
> others would, too! — if Lily could easily/automagically put [e.g.] score
Le dimanche 23 juillet 2023 à 16:55 +0200, Valentin Petzel a écrit :
> Hello Pondmates,
>
> I’ve just stumbled upon a music SE question regarding the formatting of page
> numbers. Currectly we do not have any hooks to change formatting of such
> things, rather the general approach to this is
Hi Jason,
Sorry that I haven't been able to follow your project as closely as I wanted
to. Your progress sounds great!
> Does anyone know how the process of parsing tuplet fractions goes? At
> what location in the codebase does the original tuplet numerator and
> denominator become a Moment?
Le samedi 08 juillet 2023 à 15:29 +0200, Jonas Hahnfeld via Discussions on
LilyPond development a écrit :
> Unfortunately, this won't happen: My fiber is cut and I don't have
> (fixed) internet and while I could work around this by using my
> phone and / or driving to work (that's what I did
Le mercredi 12 juillet 2023 à 17:44 -0700, Saul Tobin a écrit :
> A custom grob MarkAlignSpanner, created by Mark_align_engraver. This is
> based very closely on DynamicLineSpanner and the example engraver here:
>
Le dimanche 09 juillet 2023 à 12:57 +0200, David Kastrup a écrit :
> Ugh. Looks like our test pipeline setup would warrant including testing
> about this, then.
IIRC, when "make bytecode" and "make install-bytecode" were introduced, we still
considered them a bit experimental and didn't want to
Le dimanche 09 juillet 2023 à 12:39 +0200, David Kastrup a écrit :
> The build isn't broken unless you use bytecode compilation. Do we do
> this in general?
Depends on who is "we". I for one always build with bytecode because LilyPond is
quite slow without it, especially the startup.
> Do we
For the record, there is now a patch
at https://gitlab.com/lilypond/lilypond/-/merge_requests/2057
It LGTM. What do you think of fast-tracking it, to unbreak the build for
everyone?
signature.asc
Description: This is a digitally signed message part
> Le 8 juil. 2023 à 12:21, Werner LEMBERG a écrit :
>
> ...display-lily-tests.ly:252:8: fatal error:
> Guile signaled an error for the expression beginning here
> \test #
> #[ \key e \minor #]
> ```
That sounds like the same problem as
Le vendredi 07 juillet 2023 à 14:43 +0200, Jean Abou Samra a écrit :
> Le vendredi 07 juillet 2023 à 14:15 +0200, David Kastrup a écrit :
> > Yikes. Looks like the bytecode compiler/optimizer/whatever converts (- ) or
> > something like it into (- 0 )
> Indeed.
https://d
Le vendredi 07 juillet 2023 à 14:15 +0200, David Kastrup a écrit :
> Yikes. Looks like the bytecode compiler/optimizer/whatever converts
> (- ) or something like it into (- 0 )
Indeed.
```
$ cat minus.scm
(use-modules (oop goops))
(define-class ()
(bar #:init-keyword #:bar))
Le samedi 01 juillet 2023 à 15:02 +0200, Jonas Hahnfeld via Discussions on
LilyPond development a écrit :
> Hi all,
>
> after the unstable release 2.25.6 is out and the included update of
> bdwgc seems to resolve the rare crashes on Windows (not backported
> yet), I would like to go ahead with
Hi,
Since yesterday, I've been receiving all posts twice, from all gnu.org mailing
lists (lilypond-{devel,user,user-fr}). Is this only happening to me? (I did
fiddle with my mailing list subscriber account recently in order to investigate
a problem someone else had, but at least not the
Le jeudi 22 juin 2023 à 20:29 +0200, Jonas Hahnfeld a écrit :
> On Thu, 2023-06-22 at 14:32 +0200, Jean Abou Samra wrote:
>
> > Recently, GitLab gained a "bulk edit" button in the MR view.
>
> This button has "always" been there ...
Ok, not sure h
Le jeudi 22 juin 2023 à 14:32 +0200, Jean Abou Samra a écrit :
> So far, I think different people have different habits on when to set MR
> milestones — some do it just after merging, some don't, I do it when I
> remember to, and the MRs without milestone get their
> milestone on the
So far, I think different people have different habits on when to set MR
milestones — some do it just after merging, some don't, I do it when I remember
to, and the MRs without milestone get their
milestone on the release day.
Recently, GitLab gained a "bulk edit" button in the MR view. That
Le lundi 19 juin 2023 à 10:06 +, Werner LEMBERG a écrit :
> Folks,
>
>
> I've attached my current version of the LilyPond Visual Index that now
> covers all grobs. The source code for these two pages is more than
> 52kByte...
>
> My original idea was to make the Visual Index part of the NR
Le vendredi 16 juin 2023 à 16:13 -0700, Jason Yip a écrit :
> My implementation is available in a private fork, I'm not sure how I
> should share it if any other developers want to examine it (manual
> invite to each one who wants it?) It's a bit messy at the moment and
> definitely needs more
Le vendredi 16 juin 2023 à 18:11 +0200, Jonas Hahnfeld a écrit :
> On Fri, 2023-06-16 at 10:37 +0200, Jean Abou Samra wrote:
> > I know that 2.25.6 was planned for this weekend. Unfortunately, due to
> > https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not
&g
I know that 2.25.6 was planned for this weekend. Unfortunately, due to
https://gitlab.com/lilypond/lilypond/-/issues/6620 , current master is not
going to work on Kubuntu and possibly other distros.
I will try to find time this evening to experiment with the alternative
approaches proposed on
Le dimanche 04 juin 2023 à 12:27 -0700, Flaming Hakama by Elaine a écrit :
> I guess I am kind of confused at the default behavior, why does lilypond
> not reprint a clef when you specify \clef ?
>
> Are people putting \clef commands in their code where they don't want a
> clef to appear?
>
Le mercredi 31 mai 2023 à 16:09 +0200, Han-Wen Nienhuys a écrit :
> On Wed, May 31, 2023 at 3:56 PM David Kastrup
> <[d...@gnu.org](mailto:d...@gnu.org)> wrote:
>
> >
> > I think I disagree in this particular context because the commitment
> > from GSOC is a temporary one, and a fork is not a
Le mardi 23 mai 2023 à 20:13 +, Werner LEMBERG a écrit :
> So yes, please open an issue.
https://gitlab.com/lilypond/lilypond/-/issues/6613
signature.asc
Description: This is a digitally signed message part
On master, compiling the code
```
\version "2.25.6"
\paper {
property-defaults.fonts.serif = "Noto Serif"
}
\markup \bold "abc"
```
I get
```
warning: font index 393216 too large for font
`/usr/share/fonts/google-noto-vf/NotoSerif[wght].ttf', using index 0
warning: font index
Le lundi 22 mai 2023 à 20:00 +0200, Jean Abou Samra a écrit :
> Ok, if that was all Chinese to you,
It was pointed out to me that this sounded strange; it was a false cognate,
sorry. The equivalent of the idiomatic expression “c'est du chinois” in French
is “that's all Greek to me” in Engl
Le lundi 22 mai 2023 à 20:00 +0200, Jean Abou Samra a écrit :
> Hi,
> As I was annoyed by the code needed to automatically download LilyPond in the
> “extending-lilypond” guide, I created a “lilypond” project on PyPI...
> https://pypi.org/project/lilypond
> ... and uploaded whe
Hi,
As I was annoyed by the code needed to automatically download LilyPond in the
“extending-lilypond” guide, I created a “lilypond” project on PyPI...
[https://pypi.org/project/lilypond](https://pypi.org/project/lilypond)
... and uploaded wheels to it using a tiny script which lives at ...
1 - 100 of 1156 matches
Mail list logo
