Re: New breathing mark

On Sat, Nov 12, 2022 at 10:00 AM wrote: From: samarutuk > To: bug-lilypond > Cc: > Bcc: > Date: Sat, 12 Nov 2022 10:10:35 +0100 > Subject: Breath mark style in LilyPond 2.23.80 > Dear all, > when I tried version 2.23.80 for the first time yesterday, I was > absolutely shocked to see the new,

Re: LilyPond on macOS (was: \repeat unfold has problems inside \repeat volta)

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

Re: What is the point of bug-lilypond?

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 subscribed to the

Re: A suggestion for Dynamic staves

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

Re: Changing volta number text

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! Thanks, Carl

Re: Changing volta number text

On 5/18/21, 1:46 PM, "lilypond-user on behalf of Kieren MacMillan" wrote: Hi Ralph, > I have to admit, after learning from you that the documentation is accurate, and spending some time examining the various examples in the documentation, I think I could achieve what I want.

Re: 64 bit MacOS version + Apple Silicon version

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

Re: 64 bit MacOS version + Apple Silicon version

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

Re: 64 bit MacOS version + Apple Silicon version

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

Re: 64 bit MacOS version + Apple Silicon version

On 4/22/21, 9:49 AM, "Bart Kummel" wrote: I think you should re-consider this comment: "The other option is ditching LilyPad and doing a Darwin-only version of LilyPond, assuming that we can do this with suitably free components.", by David Kastrup. I don't think many people

Re: Lilypond 2.23.0 crashes on layout

On 2/17/21, 12:21 PM, "Arusekk" wrote: > This statement seems a little bit strange to me. I didn't think we had a > lilypond editing app on Linux -- only on Windows and MacOS. How are you > using lilypond when it is "not told to lay out"? Are you using > Frescobaldi? Are

Re: Lilypond 2.23.0 crashes on layout

On 2/16/21, 4:00 PM, "Arusekk" wrote: On my box lilypond crashes every single time I command it to produce PDFs (never does if not told to lay out), so I think I can provide much help, maybe core files, or recorded execution from GDB (never tried to do it before, though).

Re: wrong text font

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

Re: Fonts on Arch Linux

I checked on Wikipedia. The Libertine website has been archived in the Wayback Machine. You can also get a forked continuation of the now non-developed Linux Libertine fonts as Libertinus, which has Serif, Sans, and Mono variants. https://www.tug.org/TUGboat/tb37-1/tb115hosny.pdf

Re: Dead link in documentation

On 6/5/20, 12:43 AM, "Dave Atkinson" wrote: > Dear Lilypond Devs, > > I'm reading Lilypond - Extending, and trying to learn a bit of Scheme to > achieve my aims. At the bottom of the page > > https://lilypond.org/doc/v2.19/Documentation/extending/scheme-simple-data-types > > there is the

Re: Keys won't display as text in saxophone diagram

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

Re: Keys won't display as text in saxophone diagram

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

Re: Keys won't display as text in saxophone diagram

Valentin, Thanks for the quick fix. I was trying to fix it, but I'm not as fast as you. If you attach the proper copy of scm/display-woodwind-diagrams.scm to an email, I can give Antonio instructions about how to get the file into the proper place on his MacOS. The instructions: Browse

Re: Bar number with chord name

On 4/19/20, 9:07 AM, "Aidan O Connor" wrote: Hi, Thanks for that info. The workaround makes sense. But the behavior seems a little inconsistent. If the cord names are removed the bar numbers appear above the staff, but below the fret diagram. Is the fret diagram not considered part of the

Re: Possible documentation error in 2.7.2

On 2/29/20, 1:46 AM, "Ben Eichler" wrote: HI there, I read at "2.7.2 Displaying Chords" in the docs: "*Chord names can be displayed only at the start of lines and when the chord changes.*" This is a little bit misleading. By default, each chord in the content is

Re: Documentation suggestions.

On 12/30/19, 11:58 AM, "Peter Toye" wrote: Monday, December 30, 2019, 6:39:39 PM, David Kastrup wrote: > Peter Toye writes: >> As an occasional and fairly new Lilypond user I've found that the >> documentation is occasionally obscure or misleading. I've made a few

Re: Midi block gives errors with bar number checks

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

Re: Midi block gives errors with bar number checks

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

Re: [musicxml2ly] handling empty staffs

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

Re: [musicxml2ly] handling empty staffs

On 6/10/19, 12:00 PM, "Florian" wrote: Hi Aaron, Aaron Hill wrote > Seems to be a case of the first context not being alive by the time the > other notes come along. If you manually added some spacer rests of > suitable length to the upper Staff... >

Re: modern-straight and flat- flags too thick and too spaced apart

On 2/17/19, 7:52 PM, "edes" wrote: el 2019-02-17 a las 21:41 Thomas Morley escribió: > I'm currently working on it. Thank you! > Though, there is a design-decision we need to do. Indeed... In general terms, I stand by my original

Re: modern-straight and flat- flags too thick and too spaced apart

On 2/16/19, 7:22 PM, "edes" wrote: Hello, list. Some time ago I reported a bug with modern-straight and flat flags, and it was accepted as issue 5412: https://sourceforge.net/p/testlilyissues/issues/5412/ I only have a very basic knowledge of lilypond,

Re: Windows: XML import problems due to strange blanks in LilyPond 2.19.82 (Win)

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 I still use on my Windows system because of the errors listed above (I know that

Re: Windows: XML import problems due to strange blanks in LilyPond 2.19.82 (Win)

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

Re: Windows: XML import problems due to strange blanks in LilyPond 2.19.82 (Win)

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 I still use on my Windows system because of the errors listed above (I know that would

Re: Notes in the measure following a cadenza do not automatically get accidentals if they had accidentals in the cadenza

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

Re: Disappearing dynamics

Have you tried changing the lilypond call in Frescobaldi to a gdb lilypond call, so that you can pause the execution of lilypond and give Frescobaldi time to do whatever it might do -- and then continue lilypond from the debugger? Have you tried changing the Frescobaldi options for displaying

Re: no solution found for Bezier intersection

On 7/2/18, 6:32 AM, "David Kastrup" wrote: I'll take a thorough look at this code. Looks like it could benefit from a more graphic approach to intersections than converting everything into zero-based polynomials and then doing root finding. I probably have a link to

Re: lilypond not working when compiled against guile-2.2

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 >

Re: lilypond not working when compiled against guile-2.2

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... @David I think about updating this branch, it would be far easier to point interested people to this branch. Needed would be a

Re: Slur collision detection and resolution works for sharp symbol but fails for flat symbol

On 5/27/18, 9:52 AM, "Aaron Hill" wrote: On 2018-05-27 06:29, Jürgen Reuter wrote: > Looks like slur collision detection and resolution (the slur is moved > upwards) works fine for sharp accidentals, but is ignored for flat > accidentals. Slur

Re: Key cancellation, position bug

On 4/23/18, 1:30 PM, "Torsten Hämmerle" 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 collide. Carl

Re: DOC: Correcting spelling of Harmonia Sacra in NR 1.1.4 Shape note heads

On 9/30/17 4:46 PM, "David Kastrup" wrote: >Karlin High writes: > >> This is a nitpick. The places in the documentation that reference the >> "Harmonia Sacra" songbook by Joseph Funk have the spelling Harmonica >> Sacra. Harmonia does not have a "c" here. A

Re: Better discoverability for thin-variant Aiken heads: add to snippets, docs, or features?

On 9/8/17 12:47 PM, "lilypond-devel on behalf of Karlin High" wrote: > >a snippet for the LSR, >a reference in the documentation, perhaps under NR 1.1.4 Shape note heads, >adding a feature to LilyPond, the command

Re: NR 4.2.2, table column should be called "glyph name"?

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

Re: NR 4.2.2, table column should be called "glyph name"?

On 6/8/17 10:26 AM, "Federico Bruni" wrote: >http://lilypond.org/doc/v2.19/Documentation/notation/setting-the-staff-siz >e.html > >""" >Automatic font weight at different sizes > >The Emmentaler font provides the set of Feta musical glyphs in eight >different sizes; each one

Re: Font cache issues on Windows 10

On 11/7/16 2:56 AM, "Sirius Barras" wrote: >Ciao Andrew, you wrote: > > >> Where are we at with the font caching issue on Windows 10? There does >>not >> appear to be much discussion on the bug list presently, >> > >I agree with you, I wonder this annoying issue did not

Re: Manual page breaking causing assertion failure

On 7/21/16 11:41 AM, "Chris Yate" wrote: >Hey Abraham / BugsList people, > >I'm guessing nobody had a chance to look at this problem. I'm experiencing >it again, and it's really slowing me down. > >Is there anything else I can do to help debug / isolate the issue? It's

Re: tuplets and accidentals collision

On 7/6/16 5:07 AM, "Gilberto Agostinho" wrote: > >Is this a known bug? The only similar bug I found in the tracker is this >one here , but it >seems to be a bit different than what I am reporting here. >

Re: patch labels in CG manual

James, On 5/20/16 10:15 AM, "James" wrote: > > >One thing to realise and I think people have forgotten is that the >Patchy-testing scripts (rather than Patchy-merge scripts) no longer work >as they were written to scrape the old Google tracker and don't work >with Allura. > >So

Re: PianoStaff vertical spacing messed up by tuplet

On 5/10/16 3:09 PM, "Rutger Hofman" wrote: >Hello bug list, > >I think I encountered a bug that is triggered under very specific >circumstances. The lilypond program is included below. It sets the same >line two times twice. The first time is OK. The second time, after the

Re: \omit dynamic occupies space

On 4/27/16 7:09 AM, "Graham King" wrote: >meanwhile, Harm has kindly shown me a work-round. It is in the first >two bars of this example, which also serves to illustrate the partial >effect of \omit. I haven't looked at the code, but it appears to me that without

Re: fondu fails on newer OS X versions

On 4/3/16 4:15 PM, "Andrew Bernard" wrote: >Hi Thomas et al., > > >While I was helping Mats look into this I noticed the same point. The >defect means you can¹t even use a basic system font like Times in a font >name override in markup on the Mac. Can you use LaTeX

Re: Noteheads slightly too large

Paul Morris wrote >> On Feb 14, 2016, at 10:11 AM, David Kastrup > dak@ > wrote: >> >> Your image only shows notes between staff lines. However, a reduction >> in notehead size will mainly make notes _on_ staff lines look too small >> and/or unsymmetric so the image is not really useful for

Re: Noteheads slightly too large

The feta font files specify the notehead height to be exactly staff_space + staff_line_thickness. I am assuming that in the conversion from ps to type1 font with hinting, the notehead gets just a bit larger. I have rebuilt the feta font with a notehead height of staff_space + 0.8 *

Re: Review of chapter 4 of NR (spacing.itely)

Very nice work, Federico. On 12/18/15 10:57 AM, "Federico Bruni" wrote: > >b) 4.3.1 Line breaking >"Note that manually forced line breaks have to be added in parallel >with the music:" >What means "in parallel" here? The example following this sentence does >not show

Re: Aw: Re: Several notation errors in bagpipe.ly

-- Messaggio inoltrato -- Da: Oliver Briede o.bri...@web.de Oggetto: Aw: Re: Several notation errors in bagpipe.ly Data: Sun, 7 Jun 2015 10:20:31 +0200 A: Federico Bruni f...@inventati.org Cc: Julia Meihöfer j.meihoe...@googlemail.com Hello Federico, we attached the

Re: Aw: Re: Several notation errors in bagpipe.ly

On 6/7/15 9:45 AM, Federico Bruni f...@inventati.org wrote: Thanks Oliver The correct email address is bug-lilypond@gnu.org The normal procedure is that the Bug Squad will open a new issue in the tracker if the errors are confirmed. I cannot comment on the changes proposed, sine I don't know

Re: manuals page [WAS Re: teaching a university module on engraving with lilypond]

On 4/27/15 10:47 AM, Federico Bruni fedel...@gmail.com wrote: 2015-04-27 17:25 GMT+02:00 Kevin Barry barr...@gmail.com: - I'd rather use a conversational approach instead of unordered lists: Please be aware that LilyPond is a text-based(link) music engraver and read the FAQ(link) before You

Re: Subdivided beams

On 4/23/15 10:49 AM, Trevor Daniels t.dani...@treda.co.uk wrote: Urs Liska wrote Thursday, April 23, 2015 5:06 PM From the description it seems that LilyPond doesn't do that and can't easily be talked into doing it, so this seems an embarrassing bug. This was recently discussed on the

Re: Roman Numeral placement

On 4/21/15 10:34 AM, SonusProj . sonusproject...@gmail.com wrote: I want to add below the chord, treble clef, the associated Roman numeral description of each chord. I.E. on the C Major I would have I, the Dm7 would have ii7 with the 7 in superscript, the Em7 would have iii7 with the 7 in

What should be the default B7 chord?

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

Re: turkish accidental eksik bakiye missing in emmentaler font

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?

Re: [Lilypond] Incorrectly print notes with length 16*7 and 16*5

On 10/28/13 7:15 AM, Jimmie Felidae evolution.ji...@gmail.com wrote: I'm not top posting. Tested on Lilypond 2.17.29 and latest release of 2.16. Example 1: % Wrong output in bar 1 \version 2.14.0 \relative c { \key d \major \time 6/8 g16*7 fis16*5 | d2. | } I believe this does

Re: Cppcheck reports patch for 2546

On May 20, 2012, at 1:16 PM, Graham Percival gra...@percival-music.ca wrote: On Sat, May 19, 2012 at 08:30:50AM +0200, Julien Nabet wrote: Since I don't have a Google account to sign in to http://codereview.appspot.com/, I attached the patch for 2546. Don't hesitate to tell me if it's ok or

Re: Cppcheck reports

On 5/18/12 1:42 PM, Marek Klein ma...@gregoriana.sk wrote: Hello 2012/5/17 Julien Nabet serval2...@yahoo.fr I'm not top posting. Hello, I just git clone Lilypond project and launched cppcheck (git updated today). I thought it could interest you, here are some examples :

Re: Cppcheck reports

Thanks for the file, Julien. I have split the warnings into various issues. See issues 2545, 2546, and 2548 through 2554 on the issue tracker. http://code.google.com/p/lilypond/issues/detail?id=2545colspec=ID%20Type%2 0Status%20Stars%20Owner%20Patch%20Needs%20Summary

Re: tupletSpannerDuration and percent repeat conflict

On 3/26/12 12:49 PM, Lenore Horner lenorehor...@sbcglobal.net wrote: I'm not top posting. \version 2.14.2 \paper{ ragged-right=##t } \relative c'' { \set tupletSpannerDuration = #(ly:make-moment 1 4) \times 2/3 { \repeat percent 2 {g8 f g f g f g f g

Re: NR 1.2.4 - Not working snippet

On 3/14/12 5:19 PM, Thomas Morley thomasmorle...@googlemail.com wrote: Hi, due to the changes in 3/4-time snippet lily-baa9b310-1.ly in NR 1.2.4 doesn't work any more (and the description above is wrong) At least in the german translation. This is correct. The german translation has not been

Re: complex-beam

On 2/26/12 2:10 AM, David Bobroff bobr...@centrum.is wrote: I'm looking for a way to achieve this beaming pattern: http://notendur.centrum.is/~bobroff/lily/complex-beam.png Can LilyPond do this? I suspect I'll have to use a combination of subdivideBeams and

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

On 1/19/12 6:07 AM, Martin Straeten martin.strae...@gmail.com wrote: Your idea regarding a no beamlet sticking out property seems to be a practicable solution; the workaround described in the issue is fine for the simple example, but is quite inconvenient in real life. The current patch on issue

Re: Issue 2228 in lilypond: Some users prefer to minimize partial beams rather than beam by the beat

On 1/19/12 10:05 AM, Graham Percival gra...@percival-music.ca wrote: On Thu, Jan 19, 2012 at 03:55:26PM +, lilyp...@googlecode.com wrote: New patch set after: scripts/auxiliar/makeslr.py git add Documentation/snippets/new/strict-beat-beaming.ly git commit

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

On 1/17/12 3:33 AM, Martin Straeten martin.strae...@gmail.com wrote: here two examples: BWV 544: http://216.129.110.22/files/imglnks/usimg/4/4a/IMSLP01329-BWV0544.pdf old Edition of Bach Gesellschaft This example shows examples of beaming the 3/8 unit it both two and three. In measures 3-6,

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

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

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

On 1/15/12 2:50 PM, Martin Straeten martin.strae...@gmail.com wrote: I'm not top posting. in 6/8 an 3/4 measure the beamlet of the last/first semiwaver points to the dotted quaver. semiquavers should be beamed together like in 2.14.2 %-sample-- \version 2.15.24 \score { \relative c'{

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

On 1/15/12 2:50 PM, Martin Straeten martin.strae...@gmail.com wrote: I'm not top posting. in 6/8 an 3/4 measure the beamlet of the last/first semiwaver points to the dotted quaver. semiquavers should be beamed together like in 2.14.2 %-sample-- \version 2.15.24 \score { \relative c'{

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

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.

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

After a thorough review of the literature, I'm pretty satisfied that the beaming in 2.14 was wrong. The beaming in 2.15.24 is correct. If the 2.14 beaming is desired, a workaround is shown on lilypond issue 2228: http://code.google.com/p/lilypond/issues/detail?id=2228 I've marked that issue

Re: wrong beamlet direction in 6/8 and 3/4 measure for dotted quaver and semiquavers

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. semiquavers should be beamed together I may be wrong, but i

Re: Chord names collide with notes (vertical space missing on second line staff)

On 1/10/12 10:03 AM, Jean-Alexis Montignies ja...@montignies.info wrote: % no problem without mark alignment to the left or lyrics % third staff line is to show that there's no problem after second line \score { \new ChordNames = chords \chordmode { \repeat unfold 6 {g1 c:m } }

RE: error: auto beaming in tuplets after dotted semiquaver

From: Martin Straeten [martin.strae...@gmail.com] Sent: Friday, December 30, 2011 12:47 PM To: bug-lilypond@gnu.org Subject: error: auto beaming in tuplets after dotted semiquaver I'm not top posting. Autobeaming dotted semiquaver with 64th in tuplet is incorrect for 2.15.23. Beams of

Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond

On 12/30/11 6:49 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #18 on issue 1781 by dzhan...@gmail.com: Mac OS X 10.7 (Lion) cannot run LilyPond http://code.google.com/p/lilypond/issues/detail?id=1781 When will lilypond work on Lion? (Mac OS X 10.7+) I would love to use

Re: Bug with (banjo) tablature rendering (workaround possible)

On 12/29/11 11:42 AM, Dirk De Wachter que...@belgacom.net wrote: I'm not top posting. The script should explain it all. It is written for the latest stable lilypond. This another manifestation of issue 34. This can be avoided by using \with when defining the TabStaff: context TabStaff \with {

Re: Beam subdivision bug in 2.15.22

On 12/16/11 12:12 PM, Xavier Scheuer x.sche...@gmail.com wrote: On 16 December 2011 19:48, Thomas Scharkowski t.scharkow...@t-online.de wrote: \times 2/3 { b16 b b } b8 b4 b b 2.15.22 produces a (wrong) beam subdivison. 2.14.2 output is correct. See attachments. Result is fine with 2.15.20.

Re: Issue 2059 in lilypond: Bar numbering of alternatives

On 12/6/11 3:26 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #14 on issue 2059 by x.sche...@gmail.com: Bar numbering of alternatives http://code.google.com/p/lilypond/issues/detail?id=2059 The use of this \set Score.alternativeNumberingStyle = #'number or \set

Re: Issue 1356 in lilypond: LilyPond-style comments embedded inaScheme expression can't include special characters

On 11/29/11 7:28 AM, Phil Holmes m...@philholmes.net wrote: Graham Percival gra...@percival-music.ca wrote in message news:2029015547.GA2763@chikara... On Mon, Nov 28, 2011 at 06:05:35PM -0700, Colin Campbell wrote: On 11-11-28 11:39 AM, Phil Holmes wrote: This presumes that the Bug

Re: New read/eval Scheme syntax inconsistent in handling existing code

On 11/21/11 1:35 PM, David Kastrup d...@gnu.org wrote: I don't throw out functionality as a rule. ly:export was an exception to that rule because its presence was fundamentally incompatible with maintaining predictable timing for #. But I backed up this step with a set of convert-ly rules of

Re: Using Unicode symbols for accidentals

On 11/12/11 6:29 AM, Hans Aberg haber...@telia.com wrote: On 11 Nov 2011, at 23:04, Pavel Roskin wrote: It's not exactly a bug, more like a feature request :) I have noticed that convert-ly removes the \encoding and converts everything to UTF-8. I hacked together some code,

Re: Problem with music function in 2.15.18

On 11/12/11 2:17 PM, Nick Payne nick.pa...@internode.on.net wrote: There's a music function I use in virtually every guitar score I've done with Lilypond, to move glissandi that I use to indicate that a finger should be kept on a string when moving frets. I just downloaded and installed 2.15.18

Re: Using Unicode symbols for accidentals

On 11/11/11 4:49 PM, Pavel Roskin pro...@gnu.org wrote: On Fri, 11 Nov 2011 23:21:42 +0100 (CET) Werner LEMBERG w...@gnu.org wrote: f♯ is shorter and more readable than fsharp, let alone fis. In Germany and Austria, f♯ is *never* used. Only fis and nothing else. I'm sure the signs

Re: MIDI dynamics doesn't apply to multi-voice measures

On 10/29/11 8:09 AM, Pavel Roskin pro...@gnu.org wrote: Quoting Keith OHara k-ohara5...@oco.net: Pavel Roskin proski at gnu.org writes: I'm trying to change relative loudness on the melody and the accompaniment, by it turn out the MIDI dynamics doesn't apply to the measures that have

Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context.

On 9/4/11 9:04 AM, David Kastrup d...@gnu.org wrote: lilyp...@googlecode.com writes: Comment #3 on issue 1859 by reinhold...@gmail.com: let \contextStringTunings affect only current context. http://code.google.com/p/lilypond/issues/detail?id=1859 Good, so this bug seems really fixed.

FW: Custom Tuning creating space beneath the first system

Peter, I've forwarded this to bug-lilypond, because it is a bug. \contextStringTuning sets a context property for the FretBoards context. This creates a FretBoards context if one doesn't exist. I'll investigate possible fixes. In the meantime, since you're not using FretBoards in this layout,

Re: Issue 1663 in lilypond: Images missing on web site

On 7/30/11 3:07 AM, Phil Holmes m...@philholmes.net wrote: Colin Campbell c...@shaw.ca wrote in message news:4e334502.6070...@shaw.ca... Will this mean that we won't have to use the separate scripts/auxiliar/cg-section.sh SECTION as in CG 5.6, Phil? Colin Almost certainly not.

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

On 7/24/11 2:19 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #25 on issue 1752 by percival.music.ca: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 The critical regression thing was a complete brain fart from me and

Re: Issue 1752 in lilypond: redesigning G clef in our Feta font

On 7/24/11 5:43 PM, lilyp...@googlecode.com lilyp...@googlecode.com wrote: Comment #26 on issue 1752 by lemniska...@gmail.com: redesigning G clef in our Feta font http://code.google.com/p/lilypond/issues/detail?id=1752 In order to address the difference of opinion, we have two

Re: Issue 1733 in lilypond: \displayLilyMusic ignores \tweak

On 7/24/11 4:12 AM, -Eluze elu...@gmail.com wrote: If I run the command above with 2.15.5, I get the output at the bottom. I'm not convinced that's correct. Unbound variable: t \tweak #'transparent ##unspecified c e an old question: should it be ##t or just #t? a small example

Re: 2.14.2

On 7/14/11 6:23 AM, Urs Liska lilyli...@googlemail.com wrote: Hi guys, as you may have noticed I gained some activity again lately. Glad to have you back! I think I have to apologize that I faded out of my Bug Squad duty silently half a year ago. Apology accepted. This as a general

Re: how to change gap between beams?

On 7/13/11 6:48 AM, Janek Warchoł lemniskata.bernoull...@gmail.com wrote: 2011/7/13 m...@apollinemike.com m...@apollinemike.com On Jul 13, 2011, at 1:48 PM, Janek Warchoł wrote: Is it possible to change gap between beams (i.e. the distance between the lines) painlessly? \override Beam

Re: Diatonic Instruments (Mountain Dulcimer)

On 7/8/11 1:51 AM, Janek Warchoł lemniskata.bernoull...@gmail.com wrote: Hi Blake, unfortunately the only thing we can do now is to add this to our issue tracker. Dear Bugsquad, should this be added as a comment to http://code.google.com/p/lilypond/issues/detail?id=703 or as a new issue?

Re: Backporting for 2.14.2

=On 6/28/11 12:30 PM, Federico Bruni fedel...@gmail.com wrote: Il giorno lun, 27/06/2011 alle 13.13 -0600, Carl Sorensen ha scritto: I'm trying to get ready for release 2.14.2. In general, I'd like bugfixes from 2.15.x to show up in 2.14.2. Carl, when v2.14.2 will be released? (more

FW: how to create baroque ornaments

-- Forwarded Message From: Giso Grimm gg3...@vegri.net Date: Mon, 27 Jun 2011 13:23:54 -0600 To: lilypond-u...@gnu.org Conversation: how to create baroque ornaments Subject: how to create baroque ornaments How can I create ornaments like those in the attached example? I tried \markup with

Re: Bugs in Debian

On 6/7/11 5:42 AM, Carlo Stemberger carlo.stember...@gmail.com wrote: The Debian Bug Tracking System contains some bug reports concerning LilyPond, with short examples. http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=lilypond;dist=unstable Could you verify them and in case add them to

Re: Attachments on the tracker

On 5/29/11 4:29 AM, Phil Holmes m...@philholmes.net wrote: Phil Holmes m...@philholmes.net wrote in message news:irt6lm$brs$1...@dough.gmane.org... We're now using 33.4 MB (66% of total attachment quota) on the bug tracker for attachments. At some point we will (I assume) need to prune

Re: Cross-staff beaming

On 5/29/11 5:42 AM, Hilary Snaden h...@newearth.demon.co.uk wrote: Phil Holmes wrote: Hilary Snaden h...@newearth.demon.co.uk wrote in message news:4de210b3.80...@newearth.demon.co.uk... Manual beamings of cross-staff note groups are mangled, but inconsistently. The beaming in this extract

  1   2   3   >