Re: Why doesn't the build fail for anybody else, including the bots?

> Our dependencies are nothing short of annoying. If one can only > reliably build after make *-clean there is no point in using Make. +1 In case it is too complicated to get complete dependencies (I think this was the argument then when it was simplified by Han-Wen) maybe we can get a new tar

Re: Proposing commit access for Lukas-Fabian Moser

> As for the question of commit access, for me it's a trade-off > between my fear of accidentally breaking something and my wish not > to burden others too often with eventual rebasing/merging chores the > way Jean generously did for me a couple of times. Don't worry about breaking something! I

usage example for pure-unpure container sought

I've found some minor documentation and formatting issues in NR section 5.5.6, "Unpure-pure containers", which I'm going to fix. In general, however, there is a serious problem with the example in this subsubsection, as documented in issue #3512: https://gitlab.com/lilypond/lilypond/-/issues/

Re: usage example for pure-unpure container sought

>> I've found some minor documentation and formatting issues in NR >> section 5.5.6, "Unpure-pure containers", which I'm going to fix. In >> general, however, there is a serious problem with the example in this >> subsubsection, as documented in issue #3512: >> >>https://gitlab.com/lilypond/li

Re: usage example for pure-unpure container sought

>> Looking at the current output of regtest `unpure-pure-container.ly` >> I have the feeling that the description text doesn't fit the code >> at all: It always talks about the second note of each group, while >> the code modifies the first note. > > To answer the second part of your question: th

Re: usage example for pure-unpure container sought

>> Thanks. It's not clear to me what I should do now. Shall the >> whole subsubsection simply be removed? Shall a warning be added >> that this section is under construction? > > Let's leave it as-is for now as it reflects the current state, even > though the example is moot. I'll revamp the

Re: What is the point of 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 GitLab >> directly. When we transfe

Re: SMuFL Name mapping update, 13 October: Accordionist input needed

> Just got the next batch of glyphs in: > https://wolfgangsta.github.io/emmentaler-bravura/. That completes > the mapping of Feta to SMuFL (bar the still-contentious mappings). Exellent, thanks a lot! Regarding "Ped" vs. "Ped.": What exactly do you mean with the sentence I wonder if there's

Re: SMuFL Name mapping update, 13 October: Accordionist input needed

>> Regarding "Ped" vs. "Ped.": What exactly do you mean with the >> sentence I wonder if there's any way to map a SMuFL base name to a >> sequence of Emmentaler glyphs. > > Emmentaler has a "Ped" glyph and a "." glyph, but no "Ped." glyph. > > SMuFL has a "." glyph and a "Ped." glyph; "Ped" is

strange bbox of 'flat' glyph

Does anybody know why the top and the bottom of the bounding box of the 'Flat' glyph, contrary to 'Sharp' and 'Natural', don't coincide (more or less) with the extrema of the glyph's outline? A small overshoot outside of the box make sense (although Feta doesn't handle this consistently), but the

Re: strange bbox of 'flat' glyph

>> Does anybody know why the top and the bottom of the bounding box of >> the 'Flat' glyph, contrary to 'Sharp' and 'Natural', don't coincide >> (more or less) with the extrema of the glyph's outline? A small > > I can't remember any reason. :-) The question is whether we should fix this. Gi

Re: TimeSignature with note in denominator

> For my first official patch as a Lily-dev, I’m proposing to make the > result of an official > #'style in TimeSignature. It would be nice to see some real-world examples in printed scores. Do you have links for that? Werner

Re: TimeSignature with note in denominator

>> How far do you intend to push this style? Are you going to be >> content with a single denominator or allow stuff like >> >>2 12+2+3 >>- + - for- >>q q. 8 > > Optimally, yes. But right now I’m trying to get a few singles in > before swingin

Re: TimeSignature with note in denominator

>> BTW, Gould gives the following example in her book (also noting >> that it would be better to use 15/16 together with a '2+3 sempre' >> remark instead). >> >> 3 >>-- >>8 ~ 8. >> >> (the tilde denotes a tie). > > This reminds me of the \rhythm markup function that David K. onc

bbox of accidentals

Folks, please have a look at MR 1007 https://gitlab.com/lilypond/lilypond/-/merge_requests/1007 I would like to hear your opinions. Werner

Re: ANN: Pygments support for LilyPond

> So the next step now would be adding syntax highlighting to the > documentation. I've managed a prototype for HTML fairly easily, and > Info doesn't know about colors, so that's easy. Good. I'm all for colours :-) > What about PDF, however? Texinfo itself doesn't seem to have > commands fo

towards a 'normal' Emmentaler font

While playing around with accidentals, I compared Bravura's glyph metrics with the ones from Emmentaler. In short: Bravura looks like a 'normal' font, while Emmentaler is non-standard. With 'normal' I mean that if you mix Bravura glyphs with other text, they behave as expected, that is, the curr

Re: ANN: Pygments support for LilyPond

>> However, it would be necessary to define a special version of the >> `@verbatim` environment (similar to LaTeX's `minted` environment) >> that recognizes color changes. This is certainly doable and >> probably not too difficult, but I currently have other things to >> do. Maybe it's best to

Re: ANN: Pygments support for LilyPond

>> `@example` is a verbatim environment, too. Ah, I was misled. Indeed, macros are expanded within `@example`, which is good, since it simplifies colour support – you only have to convince 'pygments' to insert proper `@setcolor` commands before and after the coloured tokens. > As far as I under

Re: ANN: Pygments support for LilyPond

>> Thanks. Please apply the attached patch to `texinfo.tex` to make >> `@setcolor` work in `@example` environments; it is necessary to >> temporarily make a space character behave normally. > > Thanks a lot! I'll test it as soon as possible. Note that the actual command to be used by 'pygments

Re: ANN: Pygments support for LilyPond

>> Thanks. Please apply the attached patch to `texinfo.tex` to make >> `@setcolor` work in `@example` environments; it is necessary to >> temporarily make a space character behave normally. >> >> If my solution is sufficient I will submit it to texinfo upstream. > > It looks like the patch works

Re: ANN: Pygments support for LilyPond

>> It works with my small tests, so please send an example that fails. > > This doesn't print any color, with or without your patch: [...] Interesting, for me it works, see attached file. > $ xetex --version > XeTeX 3.14159265-2.6-0.92 (TeX Live 2020/Debian) I use XeTeX 3.141592653-2.6

Re: towards a 'normal' Emmentaler font

>> (2) The same as (1), but make LilyPond undo the font changes >> internally, that is, it horizontally translates a glyph's >> outline back to the position specified by the Lisp tables (if >> the glyph is in the tables). This ensures both consistency and >> backwards compatibili

Re: towards a 'normal' Emmentaler font

> While playing around with accidentals, I compared Bravura's glyph > metrics with the ones from Emmentaler. In short: Bravura looks like > a 'normal' font, while Emmentaler is non-standard. Meanwhile I came to the conclusion that this doesn't matter because... > With 'normal' I mean that if yo

Re: towards a 'normal' Emmentaler font

>> I think (2) might be the route to go. Comments? > > semi-related: what about the Y dimension (depth?). For accidentals, > the glyph is centered on the center of the notehead, but for > integrating with text, it should typically be centered on 0.5ex ? Something like this, yes. I will soon s

Re: ANN: Pygments support for LilyPond

>>> This doesn't print any color, with or without your patch: [...] >> Interesting, for me it works, see attached file. D'oh, yesterday I used the wrong incantation, sorry. I can reproduce the problem; attached is a new patch that also takes care of xetex. Werner ==

Re: [RFC] Moving to Guile 2.2 and away from GUB

> What do you think? +1 Werner

\tweak Score.MetronomeMark.X-offset

If I want to offset a `\tempo` mark horizontally, only \override Score.MetronomeMark.X-offset = #3 \tempo ... works. Writing \tweak MetronomeMark.X-offset #3 \tempo ... has no effect. I now wonder whether it would be possible to extend the `\tweak` command to accept also the context:

Re: \tweak Score.MetronomeMark.X-offset

>> If I want to offset a `\tempo` mark horizontally, only >> >>\override Score.MetronomeMark.X-offset = #3 >> \tempo ... >> >> works. Writing >> >>\tweak MetronomeMark.X-offset #3 \tempo ... >> has no effect. > > For reference, this is > https://gitlab.com/lilypond/lilypond/-/issue

Re: spacing/breaking with header considered separate from music

> The page breaker is the single one area I've always been afraid of > looking at :-)  It's all C++, the algorithms are not entirely > trivial, and it is very performance-sensitive. What about slurs? This is really black art IMHO :-) Werner

Re: ANN: Pygments support for LilyPond

> According to Gavin, Texinfo has no way to print text monospace text > in bold. Here's the thing: The CM family doesn't contain a font for monospace bold. Since `texinfo.tex` essentially only uses this font family, there is no support for it. > [...] Doing > > \input{texinfo} > > @tex > \tex

Re: ANN: Pygments support for LilyPond

>> Here's the thing: The CM family doesn't contain a font for >> monospace bold. Since `texinfo.tex` essentially only uses this >> font family, there is no support for it. > > Ah! OK, of course. Given your help offer below, I suppose you have > another font in mind. What would that be? Alas,

pygments support in PDFs with LM fonts

ntains the new macro stuff and some tests; I've also appended the resulting PDF. As can be seen, the LM fonts are a *light* version of CM typewriter. This is not ideal IMHO, but... Werner % lm-ot1.tex % % Written 2021 by Werner Lemberg . % % This is an input file for the `fontinst` p

Re: pygments support in PDFs with LM fonts

> * Files `lm-ot1.tex` and `lm-ot1-map.tex`. They should be executed as > follows > > export TEXINPUTS="/fonts/afm/public/lm;" > tex lm-ot1.tex > tex lm-ot1-maps.tex I forgot to mention that you need the 'fontinst' TeXLive package for that. Werner

Re: pygments support in PDFs with LM fonts

> Stupid question: how do I find the path to TeXLive in the build > system? All TeXLive binaries are expected to be in PATH. Why do you need the path? > Also, can we rely on TeX being installed via TeXLive? (This is a > genuine question.) TeXLive itself is a multi-gigabyte but modular monster

Re: pygments support in PDFs with LM fonts

>>> Stupid question: how do I find the path to TeXLive in the build >>> system? >> >> All TeXLive binaries are expected to be in PATH. Why do you need >> the path? > > Sorry, I meant the part of TEXINPUTS in your previous > email. Ah, ok. I think a good solution is to let `kpsewhich` directly

Persian accidentals (koron and sori)

In case there are experts on Persian music notation: please have a look here https://gitlab.com/lilypond/lilypond/-/merge_requests/1047 and comment on the design. Werner

Iranian classical music support

Dear LilyPond community, based on Kees van den Doel's `persian.ly`, I've submitted a Merge Request to integrate support for Iranian classical music into LilyPond. https://gitlab.com/lilypond/lilypond/-/merge_requests/1060 Please comment (and ideally, revise)! You have to sign in to comment

Learning Manual vs. Notation Reference

I wonder whether the information in the Learning Manuaol should be a subset of the Notation Reference. For example, the `AccidentalPlacement` grob is only documented in the former but missing in the latter. IMHO, this should be fixed. What do you think? I volunteer for taking care of that.

balloonText and DoublePercentEngraver

Please have a look at the following example. ``` \new Score \with { \consists "Balloon_engraver" } \new Staff { \repeat "percent" 2 { e'4 e' e' e' | \balloonGrobText #'PercentRepeat #'(0 . 1) \markup "Repeat" } \repeat "percent" 2 { e'2 e' | e' e' | \balloonGrobText #'Dou

Re: balloonText and DoublePercentEngraver

>> \new Score \with { >>   \consists "Balloon_engraver" >> } > > Ah, sorry, I forgot one: > > \new Score \with { >   \consists Balloon_engraver > } Thanks. I normally use extra `"` to mark stuff that is not a keyword. It seems I should revisit that practice... Werner

Re: balloonText and DoublePercentEngraver

Hello Lukas and Jean, thanks a lot for your help. > It seems that the correct time offset for the DoublePercentRepeat is > at the beginning of the _second_ of the two bars. Undocumented... While adding a balloon is probably exotic, being able to modify other properties of a `DoublePercentRepe

Re: balloonText and DoublePercentEngraver

>> ``` >> \once\override DoublePercentRepeat.slope = #.3 >> \repeat percent 2 { e'2 e' e' e' } >> ``` >> >> Would it be possible to make `\repeat` accept such overrides, >> passing them down to the various repeat grobs? > > ``` > { > \override DoublePercentRepeat.slope = #.3 > \repeat perce

Re: balloonText and DoublePercentEngraver

>> Thanks. I normally use extra `"` to mark stuff that is not a >> keyword. It seems I should revisit that practice... > > If we get syntax highlighting in the docs, that might be relevant. > Quoted strings are just strings, but unquoted names can be > recognized as builtins. Good point. > (

Joram Berger's 'Visual LilyPond Index' revisited

The last few days I played around to update and extend Joram's excellent 'Visual LilyPond Index' so that it covers the current development version. I've submitted an intermediate stage as a Pull Request that displays almost all grobs from the `Score`, `Staff`, `Voice`, `ChordNames`, `FiguredBass

CodaMark and friends not included in skyline

I noticed that the following grobs are not part of the skyline. Actually, I would expect that they are part of it... BarNumber CodaMark MetronomeMark RehearsalMark SectionLabel Interestingly, `SegnoMark` and `JumpScript` are both part of the skyline. The same is true for `CenteredBar

Re: CodaMark and friends not included in skyline

>> I noticed that the following grobs are not part of the skyline. >> Actually, I would expect that they are part of it... >> >>BarNumber >>CodaMark >>MetronomeMark >>RehearsalMark >>SectionLabel >> >> Interestingly, `SegnoMark` and `JumpScript` are both part of the >> skyline.

Re: CodaMark and friends not included in skyline

> Here's a second version with this fix and small improvements. Excellent, thanks! Your working speed is really amazing :-) Werner

Re: "Meisters" in the Contributor's guide

> There is this section in the Contributor's guide: > > http://lilypond.org/doc/v2.23/Documentation/contributor/meisters > > It lists four roles with decision power in the project. This dates > back to older times where the team was quite different. These days, > I don't think we have any form

Re: balloonText and DoublePercentEngraver

>>> Well, it's not very logical, but not entirely illogical either. >>> [...] >> >> I agree, but having a hint in the NR would be helpful. > > Feel free to add it. Will do soon. >>> This might eventually be a good solution. For example, the only >>> way I found to adjust the width of a double

Re: balloonText and DoublePercentEngraver

> One last thing: an aid to understanding is to view these horizontal > skylines. You can show them using > > #(ly:set-option 'debug-skylines) > \layout { > \context { > \Score > \override PaperColumn.stencil > = #ly:separation-item::print > \override NonMusicalPaperColumn.st

Re: balloonText and DoublePercentEngraver

> Horizontal spacing is computed with a system that tries to achieve > the best possible layout [...] A very good explanation, thanks. > Hope that helps to understand and document! Well, right now you are plowing the NR so I think it's best if you do that. Otherwise I can work on it after you

Re: Doc: is a tag not an environment

> While translating I saw that the tag recognized by > lilypond-book is called environment (as \lilypond{} in LaTeX). > Wouldn't it be more correct to call it tag? > > Here's the part of the Usage manual where HTML is discussed: > https://gitlab.com/lilypond/lilypond/-/blob/master/Documentation

Re: Using/requiring Cairo

> The first step would likely just involve moving to Cairo data > structures while keeping most of the current code except where the > code would duplicate Cairo API calls in a reasonably straightforward > way. Sounds very sensible. Looking around for other PDF generation libraries, we don't hav

Re: Using/requiring Cairo

>> "taking care of PostScript" is not related to converting LilyPond's >> graphics internals to Cairo since LilyPond's graphics internals are >> not written in PostScript. > > Ok, forget it then, you are not listening. [...] Why such a hostile tone, Karl? There is no reason for this. I have t

pdfsizeopt can now handle lilypond PDFs

Folks, the author of pdfsizeopt https://github.com/pts/pdfsizeopt has recently applied some bug fixes to make it work with lilypond documentation files (cf. https://github.com/pts/pdfsizeopt/issues/11). Using trueroad's approach (i.e., using `extractpdfmark'), `lilypond-notation.pdf' genera

OpenType info tools

Folks, the following two tools should help any user identify scripts and features of OpenType fonts. `fontdrop' is a nice browser tool which analyzes a font on your harddisk without uploading it to a place in the internet. It needs a recent browser that supports OpenType CSS features. [I haven

Re: OpenType info tools

> FontDrop is really handy! I can see myself using it all the time. > Although it seems to support many of the most likely used features, > it doesn't show them all. Note that you should be only interested in *typographic* features, not the features mandatory for complex script support. If you a

Re: [gs-devel] Ghostscript/GhostPDL 9.22 Release Candidate 1

>>> LilyPond has option `--bigpdfs` for unifying duplicate fonts in >>> this method. >> >> And your point is what ? That's not what the pdfwrite device is >> intended for, and we don't claim you can use it to do that. >> >> As I said, if you think its that useful, then you can add the >> switch bac

Re: Ghostscript/GhostPDL 9.22 Release Candidate 1

> In general, however, my experience of working with large documents > is that the content should be maintained in the layout application > native format until the last moment. Broadly speaking this is > similar to keeping bitmap data in something like TIFF and only > converting to JPEG at the la

Re: Ghostscript/GhostPDL 9.22 Release Candidate 1

>>There are already libraries that can read PDFs into a data structure >>and then write a new PDF [...] > > Indeed, and if I was going to do this I would use MuPDF. [...] Thanks for your suggestions. However, these are long-time solutions, which need capable persons for an implementation (and I

Re: Ghostscript/GhostPDL 9.22 Release Candidate 1

> I'm surprised you find it necessary to have different fonts for > different point sizes though. For full scores, this is *extremely* important. Today, music publishers no longer typeset pocket scores (approx. in A5 format) separately in most cases, mainly to save money. Instead, they simply s

Re: NR: Update Clef styles Appendix (issue 324420043 by pkx1...@gmail.com)

> https://cloud.woelkli.com/s/dBGXat0NEGVoy5C This link doesn't work (`Invalid PDF structure'). Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Use -b together with -dgs-never-embed-fonts (issue 325630043 by knup...@gmail.com)

> Somehow, concisely say "get-rid-of-anything-extra" versus > "keep-everything-that-comes?" > > --min-fonts and --max-fonts > --compress-fonts and --expand-fonts I would rather prefer --compress-fonts and --no-compress-fonts. This is easier to remember (and rather common in GNU packages). > --

Re: Use -b together with -dgs-never-embed-fonts (issue 325630043 by knup...@gmail.com)

> lilypond --help gives the following output: [...] > -O, --pspdfopt=KEY set ps/pdf optimization to KEY > (default: size) > KEY is either 'size', 'TeX' or > 'TeX-GS' LGTM, thanks! BTW, is there any chance to reduce the width of the he

Re: regtests for previous stables failing

>>> In that case, I can only think of our Makefiles not being >>> compatible with current make (there are also problems with current >>> g++ but you should not even have gotten as far had you encountered >>> those). > > Obviously David was right about the make-version. Do we need to fix > somethi

Re: regtests for previous stables failing

>> But I get >> /home/hermann/lilypond-git/lily/pango-font.cc: In member function >> 'Stencil Pango_font::pango_item_string_stencil(const PangoGlyphItem*) >> const': >> /home/hermann/lilypond-git/lily/pango-font.cc:166:55: error: >> 'FT_Get_X11_Font_Format' was not declared in this scope >>bool

Re: Developing for Turkish Folk Music Accidental glyphs

> Have a nice day. There are various styles of flat and sharp we use > for Turkish folk music. I send the font I used in the Finale > program as an email attachment. They need to be designed as a font > for the introduction to the system and the mold file should be > prepared. I can prepare th

Re: Developing for Turkish Folk Music Accidental glyphs

> As far as I can, I got the code numbers of the signs to be used. Thanks. Note that the mapping of b² → U+0077 is invalid (as are all other mappings). Reason is that Unicode character U+0077 is `LATIN SMALL LETTER W' and nothing else. Whoever built the font, she or he incorrectly assigned

Re: Issue 5272: Add \depart (issue 337520043 by nine.fierce.ball...@gmail.com)

>> If we want to capture semantics properly, I believe we need to >> recognize that there are three different kinds of marks: >> >> 1) "jump-from" marks (D.S. al ..., D.C. al ..., To Coda) >> 2) "jump-to" marks (Segno, beginning of piece, coda) >> 3) "stop playing" marks (Fine, end of piece) [...]

1/8 and 1/16 feta flags too wide?

While checking Malte's feta flag patches I've just seen that the 1/8 and 1/16 up-flags (i.e., glyphs `flags.u3' and `flags.u4') have a width approx. 10% larger than other `flags.uX' glyphs – this is also reflected in the lilypond metrics embedded in the fonts. Note that the two larger widths are

Re: 1/8 and 1/16 feta flags too wide?

>> While checking Malte's feta flag patches I've just seen that the >> 1/8 and 1/16 up-flags (i.e., glyphs `flags.u3' and `flags.u4') have >> a width approx. 10% larger than other `flags.uX' glyphs – this is >> also reflected in the lilypond metrics embedded in the fonts. Note >> that the two larg

Re: 1/8 and 1/16 feta flags too wide?

> I've now remove the extra stemthickness# / 2 from the 8th and 16th > flags and run a regtest. > > There were no effects to be seen at all. Thanks! > But for the sake of consistency and homogeneity, we (i.e. Malte) > should remove these two relics now we have issue #5277. Yes, this is a good o

Re: 1/8 and 1/16 feta flags too wide?

> I've now set up a little comparison test (see attachment). [...] Great! While the effect is subtle, it can sum up significantly for longer pieces. > After all, I agree to go for unified widths because there is no > reason at all why tails of quavers/semiquavers should be treated > differentl

speed of fontconfig

I've just read the following on the fontconfig mailing list. > [... replacing] 2.12.6 [... with] 2.12.93 indeed provides ~100x > improvement and builds the cache on my system in 600ms. This was a report of using fontconfig on Windows, IIRC. So my question: Does the Windows tarball of lilypond c

Re: speed of fontconfig

>>> [... replacing] 2.12.6 [... with] 2.12.93 indeed provides ~100x >>> improvement and builds the cache on my system in 600ms. >> >> This was a report of using fontconfig on Windows, IIRC. So my >> question: Does the Windows tarball of lilypond contain a recent >> fontconfig version? > > Accord

Re: speed of fontconfig

>> For LilyPond 2.21, we should upgrade fontconfig, in my humble >> opinion. But, for LilyPond 2.20, I'm wondering whether we should >> upgrade or not. >> >> If I understand correctly, the new fontconfig has significant >> changes. > > I created https://sourceforge.net/p/testlilyissues/issues/52

Re: Build error. MergeFonts: Can't find font: feta11.pfb

> Invoking "t1asm parmesan-noteheads14.pt1 parmesan-noteheads14.pfb"... > mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find > another way to convert parmesan-noteheads14.pt1 to > parmesan-noteheads14.pfb > […] > > t1utils (including t1asm) are installed in the correct version

Re: Skylines and certain grob properties (rotation, extra-offset)

>> What do you think about making skylines consider the grob >> properties rotation and extra-offset? >> >> (1) keep everything as it is >> (2) skylines should reflect both grob rotation and grob extra-offset >> (3) skylines should reflect grob rotation only >> (4) skylines should reflect grob extr

Re: Release schedule for 2.20

> On my GUB build machine (4 core hyperthreaded i7, 8 Gigs, SSD) an > incremental build (i.e. with a stable version of GUB with the > toolset all up to date) takes around one to one and a half hours. > If GUB needs updating, it can, as you say, take over 6 hours even on > that machine. The upload

Re: Release schedule for 2.20

>> What about setting up GUB (with LilyPond) on >> https://hydra.nixos.org/? Other GNU projects like Emacs are also >> hosted there for daily builds, so it should be easy to get lilypond >> registered there... >> >> https://nixos.org/hydra/ > > Are you going to do it? Basically, I'm intereste

Re: Rational

> The ultimate in self-assertion is to disagree with those that agree > with you. Hans, such remarks aren't helpful. You sound like you are lecturing. Maybe this is not your intention and you have serious questions – if this is so, please be more careful in formulation. Werner _

Re: Now this is a nightmare...

> We probably need some ly_is_integer instead that also checks for > scm_exact_p or so? Guile-2.0 has scm_is_exact_integer but Guile-1 > apparently not. What about emulating `scm_is_exact_integer', either in Scheme or in C++? This should make transition to Guile-2 simple. Werner ___

Re: Now this is a nightmare...

>> What about emulating `scm_is_exact_integer', either in Scheme or in >> C++? This should make transition to Guile-2 simple. > > You mean, complex. Hmm. I was thinking along the gnulib mechanism which provides drop-ins for many system functions. > Get it wrong, and our private version is ge

Re: C++ standards

> What C++ standard should we be able to ask for? I think that at the > current point of time, C++11 should be reasonably fine for the > asking. Yes. > Would we need some autoconf tests? Probably yes. > Should we provide some --std=c++11 option or similar at least to > gcc? This is handled

Re: C++ standards

>>> Should we provide some --std=c++11 option or similar at least to >>> gcc? >> >> This is handled by autoconf, isn't it? > > Don't see anything in its documentation regarding that. My bad. It's rather the AX_CXX_COMPILE_STDCXX macro from the `autoconf-archive' repository. Werner _

Re: C++ standards

>> My bad. It's rather the AX_CXX_COMPILE_STDCXX macro from the >> `autoconf-archive' repository. > > So one needs to copy that macro from there to configure.ac or how > does this work? Normally, programs that use autoconf have an `m4' directory that contains all M4 files with macros used in `co

Re: Issue 5368: Reduce allocations in Grob dimension caching (issue 359770043 by nine.fierce.ball...@gmail.com)

> It took long time to get C++11 right, so it is best to avoid older > compilers I think. I disagree. The proper way is to test various C++11 features to check whether a compiler really supports this standard. The macro AX_CXX_COMPILE_STDCXX does such checks, BTW. Werner ___

Re: Issue 5368: Reduce allocations in Grob dimension caching (issue 359770043 by nine.fierce.ball...@gmail.com)

>> I disagree. The proper way is to test various C++11 features to >> check whether a compiler really supports this standard. The macro >> AX_CXX_COMPILE_STDCXX does such checks, BTW. > > Full C++11 support was first in GCC 4.8.1, see: > https://gcc.gnu.org/projects/cxx-status.html The prom

Re: GUB

From: David Kastrup Subject: Re: GUB Date: Tue, 10 Jul 2018 09:30:04 +0200 > Carl Sorensen writes: > >> In May, when we were discussing the limitations of 32 bit MinGW, I >> asked Jan for an estimate of how much work it would be to add a 64-bt >> MinGW to GUB. >> >> His answer was that GUB is a

Re: GUB

>> guix pack --target=i686-w64-mingw32 guile > > But we'd not longer have regular Windows installers, right? I guess this is correct. Isn't it possible to make the Windows installer simply use the created tarball? [I have no idea how the Windows installer works.] Werner _

Re: Limiting the number of accepted contexts

> I am considering allowing context definitions to express that no > more than one of a certain child is accepted. This is the currently > implicitly the case for Score as a child of Global. > > I thought a syntax something like this would work: > > \accepts “Zinnia” % any number of Zinn

Re: GUB

>>> I found a possibility that the wrong PDF is output >>> if the build directory is not clean. > > I've created the patch. > https://sourceforge.net/p/testlilyissues/issues/5380/ > https://codereview.appspot.com/355750043 Thanks a lot! Werner

status of linuxaudio.org

Folks, downloading 2.19.82 from lilypond.org works just fine. However, the last mirrored tarball on linuxaudio.org is 2.19.80. What's the current state of mirroring? Is it still active? Werner ___ lilypond-devel mailing list lilypond-devel@g

Re: Turkish makam using regular.ly

> Sorry, I forgot to attach an screenshot of some of the future > Emmentaler tiny-arrow accidentals. Very nice! > It's not the final design state, there's still some tweaking needed. Indeed. I suggest that the tips of the arrows don't cross the staff lines. Werner _

compilation with clang

[git 964722f8046cbc77633fb8efbc4696677a579311] Folks, for better support of lilypond on MacOS I think it would be a good idea to be able to compile lilypond with clang. Trying so with clang-6.0 as provided by my openSuSE GNU/Linux box quickly aborts as follows (clang-6.0 on my MacOS Lion box

Re: compilation with clang

>> Looking around in the internet it seems that this is a real >> problem, violating the C++11 standard, cf. >> >> >> https://stackoverflow.com/questions/33872039/invalid-explicitly-specified-argument-in-clang-but-successful-compilation-in-gcc >> >> Unfortunately, I'm completely stuck with a fix

Re: compilation with clang

>> Are you *sure* that lilypond's code conforms to C++11? > > I had read the standard on this after the first report. It was > pretty clear I thought. We had a discussion then. I think that > Mojca reported it then, maybe you can look this up. Found it, together with your MWE. Note that the

Re: compilation with clang

>>> Could you extract a MWE so that I can create a question on >>> stackexchange? >> >> What would that be good for? > > The idea is that other people can have a look at it, too. And answers are trickling in; see thread starting with http://lists.llvm.org/pipermail/cfe-users/2018-November/0

Re: compilation with clang

What would that be good for? >>> >>> The idea is that other people can have a look at it, too. >> >> And answers are trickling in; see thread starting with >> >> http://lists.llvm.org/pipermail/cfe-users/2018-November/001417.html > > That's not exactly what I call "Stackexchange" though.

<    2   3   4   5   6   7   8   9   10   11   >