ince this was an intentional change, it's not a bug, so bug-lilypond is
not the best place to discuss it. Either lilypond-user or lilypond-devel
would be a better place.
Sincerely,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Sat, Jul 2, 2022 at 10:23 AM Jean Abou Samra wrote:
> Le 02/07/2022 à 18:14, Carl Sorensen a écrit :
>
> > I can't currently run 2.23.10 on my Mac, so I can't try it,
>
>
> What is the problem you are encountering? I think that normally, it
> should work on all 64-bit
ely if bug-lilypond is replace
with direct submission to GitLab issues.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 9/30/21, 10:32 AM, "Peter Toye" wrote:
Oddly, Frescobaldi doesn't recognise \magnifyMusiceither wher I've put it
or within the brackets.
You haven't matched the required structure for the file. Our parser is
flexible to allow different kinds of music functions, so sometimes the
On 5/18/21, 2:11 PM, "Jean Abou Samra" wrote:
It is worth noting that the \volta command added by Dan Eble in the 2.23
development series does exactly the job requested here, if I understood
correctly.
Perfect!
Tha
or (albeit
with warnings).
I'd be in favor of Aaron's snippet being added to the Docs.
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
From: Marnen Laibow-Koser
Date: Thursday, April 22, 2021 at 1:26 PM
To: Carl Sorensen
Cc: Bart Kummel , David Kastrup , Karlin High
, Kenneth Wolcott ,
"bug-lilypond@gnu.org"
Subject: Re: 64 bit MacOS version + Apple Silicon version
[..]
Do you have any suggestions about how I c
From: Marnen Laibow-Koser
Date: Thursday, April 22, 2021 at 12:59 PM
To: Carl Sorensen
Cc: Bart Kummel , David Kastrup , Karlin High
, Kenneth Wolcott ,
"bug-lilypond@gnu.org"
Subject: Re: 64 bit MacOS version + Apple Silicon version
On Thu, Apr 22, 2021 at 2:54 PM Car
From: Marnen Laibow-Koser
Date: Thursday, April 22, 2021 at 12:48 PM
To: Bart Kummel
Cc: Karlin High , Carl Sorensen ,
Kenneth Wolcott , David Kastrup ,
"bug-lilypond@gnu.org"
Subject: Re: 64 bit MacOS version + Apple Silicon version
On Thu, Apr 22, 2021 at 2:24 PM Bart Kummel
dy else?
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
uld use would be "when there is no layout block".
Fortunately, Jonas figured out the error very quickly and has already posted a
patch for review.
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
I would be surprised if Frescobaldi or
Emacs had anything to do with the issue, because both just call the lilypond
executable. But I think it's good to understand your use case completely.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
h
This is a known issue that was resolved back in 2016. It has to do with some
font configurations.
See here for more info:
http://lilypond.1069038.n5.nabble.com/Problem-with-Fonts-too-big-td196510.html
HTH,
Carl
___
bug-lilypond mailing list
bug
://github.com/alif-type/libertinus
You may wish to investigate thin font with ongoing development.
Carl
On 6/28/20, 6:09 AM, "Andrew Bernard" wrote:
Thanks Aaron. I didn't give an MWE as it was a preliminary probe to
see if this is a known issue.
Here's the code in question:
#(de
rs to be dead and takes me to a 404 - Page Not Found
> landing page at gnu.org.
>
> Cheers,
>
> Dave
The current link is here:
https://www.gnu.org/software/guile/docs/docs-1.8/guile-ref/Simple-Data-Types.html#Simple-Data-Types
Carl
_
per output in graphical mode (I think).
Carl
From: Antonio Ortega Brook
Date: Thursday, May 21, 2020 at 9:18 PM
To: Carl Sorensen
Cc: "bug-lilypond@gnu.org" , Valentin Villenave
, Valentin Villenave
Subject: Re: Keys won't display as text in saxophone diagram
This would be the desire
What is the desired output?
Carl
From: Antonio Ortega Brook
Date: Thursday, May 21, 2020 at 7:13 PM
To: Carl Sorensen
Cc: "bug-lilypond@gnu.org" , Valentin Villenave
, Valentin Villenave
Subject: Re: Keys won't display as text in saxophone diagram
Oh, don't worry, I've alre
procedure is necessary because I don't think we've ever had a version
without this typo.
HTH,
Carl
On 5/20/20, 5:42 PM, "Antonio Ortega Brook"
wrote:
Hello everyone. First of all I think maybe I misunderstood the instructions
for bug reporting and I've opened an issue in G
dered part of the score system?
CDS-> The fret diagrams are markups attached to chords in the staff, so they
are part of the staff. If you had used a FretBoards context as well as a
ChordNames context, you would have found the bar numbers above the fret
diagrams.
HTH,
Carl
I am using a brain-dea
the start of lines and when the chord changes." would be more consistent
with our policy, although listing the context name is suspect. How would you
feel about that sentence?
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> don't (but would like to) know the answer.
>> Also - should it be "Contributors' Guide". Presumably you have more
>> than one contributor.
> It is also called User Guide rather than Users
> Guide. It's a guide for
> the user, res
From: Peter Toye
Reply-To: Peter Toye
Date: Tuesday, November 26, 2019 at 11:43 AM
To: Carl Sorensen , "bug-lilypond@gnu.org"
Subject: Re: Midi block gives errors with bar number checks
Carl,
I've just found the MIDI "beat clock" - 24 per crotchet. Still no bar numbers
On 11/26/19, 9:24 AM, "Peter Toye" wrote:
The following MWE gives bar number check errors. If you comment out the
midi block they go away. Bizarre, but a definite bug IMHO.
I don't think it's a bug at all. Midi files require ascending bar numbers,
IIUC. You can't have two measure #2
On 6/14/19, 9:35 AM, "Florian" wrote:
Hi again,
Carl Sorensen-3 wrote
> I believe that this is less a bug in musicxml2ly and more a limitation of
> musicxm2ly. MusicXML and Lilypond have fundamentally different concepts
> of the
the converter has done its job.
I'm certainly not opposing raising an issue for this, but fixing it would be
very low priority for me.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
either.
I think this discussion belongs on the -user list, not the bug list, as we're
now talking about aesthetics, so I've copied it over there.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
t we would replace the defaults.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
sd and see if
that eliminates the spurious stem direction commands.
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 1/14/19, 9:32 PM, "Carl Sorensen" wrote:
On 1/14/19, 11:11 AM, "samaru...@aim.com" wrote:
PS Windows+Mac: StemUp/Downs appear everywhere after the import, this
was not the case with older LilyPond versions, e.g. 2.19.31, which
east point you in this promising direction.
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 11/28/18, 2:50 AM, "David Kastrup" wrote:
Arcus Impetus writes:
> %The measure following a cadenza
> %does not properly automatically
> %place accidentals. Lilypond seems to consider
> %the meaning of the accidentals in the cadenza
> %to carry forward to the
the pdf to get
to a minimal Frescobaldi run that doesn't do much but generate the pdf?
This sounds like a truly bizarre bug.
Carl
On 11/12/18, 4:46 PM, "Andrew Bernard" wrote:
Hi k\Kevin and All,
It ranks as one of the most bizarre bugs I have ever seen (a
ave a link to some good, robust Bezier intersection finding
algorithms if you are interested.
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 6/5/18, 2:45 AM, "Thomas Morley" wrote:
2018-06-05 4:14 GMT+02:00 Carl Sorensen :
>
>
> On 6/4/18, 6:13 PM, "Thomas Morley" wrote:
>
>
> That said, in our git we have a 'guile-v2-work'-branch, but it's not
>
up to date.
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
\override Slur.height-limit = #10
a'( ges'') a'( gis'') % Collision with both accidentals.
\override Stem.direction = #UP
a'( ges'') a'( gis'') % Collision with flat only.
}
This is not a bug, but just a hard slur to engrave, so the default values of
the deta
On 4/23/18, 1:30 PM, "Torsten Hämmerle" <torsten.haemme...@web.de> wrote:
But why \once?
If generally all cancellations collide, you may well use a general
\override.
Because all cancellations don't collide; only the cancellations of flats
had a fair share of "this could not possibly break compilation"
>kind of changes breaking compilation.
>
>Also any possibility for contention is worth a review. This here seems
>solid enough to me.
I agree with David.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
d probably go ahead and add a command
\aikenThinHeads (rather than \aikenHeadsThin -- all of the others end
with Heads) and \aikenThinHeadsMinor.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 6/12/17 4:06 AM, "Federico Bruni" <f...@inventati.org> wrote:
>
>
>Il giorno sab 10 giu 2017 alle 2:54, Carl Sorensen <c_soren...@byu.edu>
>ha scritto:
>> On 6/8/17 10:26 AM, "Federico Bruni" <f...@inventati.org> wrote:
>>
>&g
taff height (pt) staff height (mm) use
>feta11 11.22 3.9 pocket scores
>feta13 12.60 4.4
>[...]
>"""
>
>Should "font name" be replaced with "glyph name"?
Not in my opinion. The font is feta11 (the font family is feta). The
staff hei
2
(ly:grob-set-property! grob 'positions (cons position position
#})
Thanks,
Carl
On 19/12/2016 00:43:52, Thomas Morley <thomasmorle...@gmail.com> wrote:
Hi Carl,
2016-12-18 8:26 GMT+01:00 Carl Williams :
> One more little adjustment, for anyone who will benefit f
hickness))) 2)
)
)
)
(ly:grob-set-property! grob 'positions (cons position position))
)
)
#})
On 18/12/2016 18:08:34, Carl Williams <carl.j.willia...@gmail.com> wrote:
To anyone who's interested,
I've tidied up the workaround for this. It now takes two inputs; s
r8 g\4 c,4 e2
a1
g8\4 c, e a c,[ c] a'8 a
}
}
%%
Cheers,
Carl
On 16/12/2016 22:09:09, Carl Williams <carl.j.willia...@gmail.com> wrote:
Thanks Harm,
That's just what I was after.
I'm keen to learn more about how beam positions and stems are calculated
be in.
Thanks for adding the feature request too.
Cheers,
Carl
On 16/12/2016 12:39:08, Thomas Morley <thomasmorle...@gmail.com> wrote:
Hi Carl,
2016-12-14 8:14 GMT+01:00 Carl Williams :
> Hi Everyone,
>
> First time using a mailing list.
> I've raked through the documentation pages all t
dle of the staff
\override TabVoice.Rest.Y-offset = #0
%hide voiceTwo stems
\override TabVoice.Stem.transparent = ##t
\mynotes
}
>>
here's how it comes out now:
On 14/12/2016 20:14:57, Carl Williams <carl.j.willia...@gmail.com> wrote:
Hi Everyone,
First time using
t the deal is with pictures.
Eventually I want to look at half length stems for minim and quarter length for
semibreve, but one thing at a time.
Thanks,
Carl
http://purl.org/dc/elements/1.1/;
xmlns:cc="http://creativecommons.org/ns#;
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#
>I agree with you, I wonder this annoying issue did not pop up more
>frequently in the list.
I suspect it's because few (or perhaps no) developers are using Windows 10.
That makes it very hard to troubleshoot.
Thanks,
Carl
___
bug-lilypond maili
ion failure
Because few of the developers work in Windows, it will be difficult for
them to debug this problem. So anything you can do to narrow it down will
increase the likelihood that the problem will be solved.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
s it didn't yet meet LilyPond coding standards).
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
atchy-testing scripts working, so this
manual procedure is no longer needed, or is at least simplified.
I've found the Patchy scripts at github as shown in the CG. Are changes
made by sending a pull request to Graham? Or do we have push permission
on the Patchy repo?
Thanks,
Carl
__
\break
\rondoPiSU
}
\new Staff = SU {
\clef bass
s2*4 |
}
>>
}
Thus, I would make sure the issue title includes "cross-staff unbeamed
tuplets".
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
olumn.
Hazarding a guess that the dynamic text is bound to the note column, and
thus the hairpin moves out of the columns into the inter-column space.
And if the dynamic text overflows the column, the hairpin is shortened.
When the text is omitted, the hairpin can only move to the
program? If nothing else, others
>who encounter it will be able to search for it.
I agree. We need a bug posted.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
ent settings for overdone_heads and the noteheads
in green are available on the tracker issue:
https://sourceforge.net/p/testlilyissues/issues/4693/
<https://sourceforge.net/p/testlilyissues/issues/4693/>
Thanks,
Carl
--
View this message in context:
http://lilypond.1069038.n5.n
*
staff_line_thickness. It seems to avoid the overlap problem, but still
appears to be full width.
If this is acceptable, I will prepare a patch.
Thanks,
Carl
<http://lilypond.1069038.n5.nabble.com/file/n187152/noteheads.png>
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Not
trating that you can add breaks in a
music expression that contains only breaks and spacing information, as
long as that expression is in parallel with the music.
I use this feature often in my scores; I create a spacing variable and
actually add it in a parallel context in a
in the lilypond distribution, it
would be much easier to just have the file as it should be, with all of
the wrong items eliminated and the right items included.
Could you please prepare a copy of the file in that format?
Thanks,
Carl
___
bug-lilypond mailing
(the attached
file may be ignored...). You find the information here:
http://www.lilypond.org/doc/v2.19/Documentation/contributor/commits-and-pa
tches
I will be happy to submit a patch, so Oliver and Julia do not have to, if
they would rather not.
Please let me know.
Thanks,
Carl
shouldn't be read. It should only be referenced. And I
think we should make that clear whenever we talk about it.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
on the user list. See
http://lists.gnu.org/archive/html/lilypond-user/2015-03/msg00365.html
and surrounding emails.
A new issue, number 4355, has been created for this bug.
http://code.google.com/p/lilypond/issues/detail?id=4355
Thanks,
Carl
___
bug
as far as I know) is a scale-degree chord namer. This would
be a reasonable feature request. I'll copy to bug-lilypond so the bug
squad can do their magic.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
There has been a difference of opinion on why the default B7 guitar chord
shape should be. I'm making a poll to determine what the users would
prefer.
Would you like the first chord in the attachment (barred on fret 2) or the
second chord (open chord in first position)?
Thanks,
Carl
part
combined for the purpose of being able to attach lyrics, but if
someone might test it to see how it works in other situations?
Carl P.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
/Documentation/contributor/debugging-website-and-docs-locally
Carl Peterson
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On Mon, Dec 9, 2013 at 1:05 PM, David Kastrup d...@gnu.org wrote:
James pkx1...@gmail.com writes:
Hello,
On 09/12/13 14:03, Carl Peterson wrote:
When trying to work the Documentation/lilypond-texi2html.init file, I
have
observed that changing this file does not trigger
On 11/26/13 8:37 PM, Keith OHara k-ohara5...@oco.net wrote:
Philippe Ploquin philippeploquin at neuf.fr writes:
The accidental called eksik bakiye is missing in lilypond.
Can anyone give a link to a reference image showing this accidental in
use?
exactly what is supposed to do: print a sixteenth note
that takes up the duration of 7 sixteenth notes, followed by a sixteenth
note that takes up the duration of 5 sixteenth notes for a total of 12/16
or 6/8, thus filling the bar.
What do you believe it should do?
Thanks,
Carl
FWIW the macports version runs on my machine. I'll use that for now-- i can
live with command-line compiling.
Be nice to get the GUI-based lilypond.app running, tho.
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/crash-report-for-OSX-tp151959p152320.html
Sent from
More info. Ran gdb and at the point I tried to typeset file, got:;
2013-10-13 20:59:34.580 LilyPond[86224:a0f] *** NSTimer ignoring exception
'type 'exceptions.OSError': [Errno 4] Interrupted system call' that raised
during firing of timer with target 0x4956d0 and selector 'timerCallback:'
SOrry for the delay - I didn't get the direct email you sent. Anyway,
I was using the initial sample file that Lilypond generates at first run.
I've tried Lilypond versions 16,15 and 14, with same failure. There's
something fundamentally wrong with the Lilypond compiled OSX version.
--
Hi -- OSX 10.6.8, iMac core Duo Intel
LilyPond compiled binary off the main site, 2.16.2.
All the previous versions I tried (back thru 2.14) were from the repository
at lilypond.org as well.
More tests: I invoked the executable
`Lilypond/Contents/Resources/bin/lilypond` directly from the command
For christsake lose that idiotic Top post filter will you?
Latest stable LilyPond, trying to compile the example file.
OSX 10.6.8 on iMac IntelCore2Duo.
Here's the crashlog.
Process: lilypond [448]
Path:/Applications/Music
Tools/LilyPond.app/Contents/Resources/bin/lilypond
(texlive-lang-cyrillic or texlive-texmf-fonts)
I was able to use apt-get to install the texlive-lang-cyrillic to complete
the build prep and execute the make command.
The issue is that this should theoretically already be installed if needed.
Thanks,
Carl Peterson
On Sat, Jul 20, 2013 at 6:34 PM, Thomas Morley thomasmorle...@gmail.comwrote:
Though, it's a known one issue:
http://code.google.com/p/lilypond/issues/detail?id=2538
Cheers,
Harm
Thanks. I searched for it, but I guess I didn't search well enough :-)
Cheers,
Carl
the
process.
I have offered to shepherd his patch, but have been busy with family
emergencies. I should get to it tomorrow.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
the output
file from cppcheck, as long as the file is not too long.
At any rate, I'd like to see the output file.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
/Documentation/contributor/commits-and-patches
#uploading-a-patch-for-review
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
}
%}
\unset tupletSpannerDuration
}
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
updated.
When the translation is updated, the snippet should also be fixed, I think.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
(with David K's new syntax, where we can have duration
elements)
\set subdivideBeams = #'( 8 16 )
I'll put this in the hopper and think about it.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug
2228 restores the previous behavior, with the
option to use strict beat beaming by setting a context property.
Hopefully this will be part of 2.15.27. If you can build your own source,
it's available now from Rietveld.
Thanks,
Carl
___
bug-lilypond
will be exactly the same. In fact,
I'll go ahead and demonstrate it.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
be under user control.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
On 1/15/12 6:04 PM, Carl Sorensen c_soren...@byu.edu wrote:
On 1/15/12 3:06 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
2012/1/15 Martin Straeten martin.strae...@gmail.com:
I'm not top posting.
in 6/8 an 3/4 measure the beamlet of the last/first semiwaver
points to the dotted quaver
a misuse of lilypond, and there is no *right* beaming.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
'{
\time 6/8
c16 d e f8. c8. d16 e f
\time 3/4
c16 d e f8. c8. d16 e f
}}
This has been added as issue 2228:
http://code.google.com/p/lilypond/issues/detail?id=2228
A patch is up for review:
http://codereview.appspot.com/5545067
Thanks,
Carl
On 1/16/12 3:41 PM, Janek Warchoł janek.lilyp...@gmail.com wrote:
Carl,
Thanks for your research.
I agree that there must be tied notes if one wants this melody to be
in 3/4 meter.
However, i'm not sure about 6/8. My pure reasoning is that a
measure in 6/8 meter divides like this:
4. + 4.
8+8
invalid. Martin, if you'd like to make an argument
that I was wrong in doing so, I'm willing to listen. It would be best if
you can show some well-engraved music that shows the beaming you were
after.
Thanks,
Carl
___
bug-lilypond mailing list
bug
,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
= #LEFT
\mark markb'4 g'8 b' g' b' g' b' \break
}
}
\new Lyrics \lyricsto theme \lyricmode { \repeat unfold 21 A}
}
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman
of first 64th points to the left instead of beeing connected to the
beams
of the 2nd and 3rd 64th.
This is issue 2113, and has been fixed in 2.15.24.
Thanks for the report.
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org
linux).
I wish I had better news for you than this. We are short on developers
for OSX.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
, happens before the first music in the TabStaff).
HTH,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
problem, and a new potential regression test.
When I've fixed the new problem, the regtests will show that 11 is *still*
fixed.
So a new issue should be added for this bug.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https
This should become a new issue, type Documentation.
Thanks,
Carl
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
., patches whose only verification is verify that
the patch was applied.
Those that can be verified through changed documentation or fixed regtests
could easily keep going as they have historically.
Thanks,
Carl
--
Phil Holmes
Bug Squad
of rather high quality and coverage (including
the entire Lilypond code base).
Let me take the time (much belated) to thank you for that set of
convert-ly rules. I disagree that they are of rather high quality and
coverage; I believe they are of extremely high quality and coverage.
Thanks,
Carl
-note-names.scm, with a language
unicode added.
Another concern about having unicode as the default language -- when I
opened the file in my default editor (TextEdit), none of the unicode
characters appeared. Readability was definitely not higher in this case.
Thanks,
Carl
missacc) (number? number? pair? boolean?) #{
\once \override Glissando #'bound-details #'left #'padding =
#$padleft
\once \override Glissando #'bound-details #'right #'padding =
#$padright
I believe you now use just $padright instead of #$padright
HTH,
Carl
1 - 100 of 295 matches
Mail list logo
