Re: git-cl upload issues

Am 12.12.2013 11:48, schrieb David Kastrup: Urs Liska lilyli...@googlemail.com writes: Hi, trying to upload a patch through git-cl I encounter two issues (one merely being a documentation issue): - I'm asked about my Google mail address and password. No. You are asked about your Google

Re: Spacing/collision behaviour of NullVoice

Am 17.12.2013 11:16, schrieb Trevor Daniels: Urs Liska wrote Tuesday, December 17, 2013 9:01 AM However I noticed a behaviour I wouldn't have expected: Try out the following snippet: soprano = \relative c' { c e g c } verse = \lyricmode { This is my song } \score { \new Staff

Re: Spacing/collision behaviour of NullVoice

Am 17.12.2013 12:09, schrieb Trevor Daniels: Urs, you wrote Tuesday, December 17, 2013 10:50 AM What about changing that to For example, arbitrary notes in the NullVoice may arbitrarily move rests or cause accidentals to appear (or disappear) on the staff. ? I see David's already had some

\parenthesize collision with dots

If I parentesize a dotted note with { \parenthesize f'2. } the right paren collides with the dot. Urs attachment: document.png___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: \parenthesize collision with dots

Am 18.12.2013 07:15, schrieb Mike Solomon: On Dec 18, 2013, at 1:00 AM, Urs Liska lilyli...@googlemail.com wrote: If I parentesize a dotted note with { \parenthesize f'2. } the right paren collides with the dot. Urs Do you want the dot to shift to avoid the collision or the parenthesis

Re: \parenthesize collision with dots

Am 20.12.2013 21:25, schrieb James: On 18/12/13 06:18, Urs Liska wrote: Am 18.12.2013 07:15, schrieb Mike Solomon: On Dec 18, 2013, at 1:00 AM, Urs Liska lilyli...@googlemail.com wrote: If I parentesize a dotted note with { \parenthesize f'2. } the right paren collides with the dot. Urs

Re: Double transpose when in tags within music function

Am 09.01.2014 12:55, schrieb Ole V. Villumsen: Expected behaviour of the example below: engrave a d (transpose the c to d). Actual behaviour: engraved an f. Seems to have done both of the transpositions described in the two different tags in the music function (transposed c to d, then to f, or

Define custom/new \accidentalStyles (dodecaphonic minus repeated notes)

Hi, searching the docs and the lilypond-user archive I couldn't find any relevant information. I am looking for a custom \accidentalStyle. Actually I think this is quite commonly used, so it would also seem like a useful addition to LilyPond proper. a) Every note gets an explicit

Default padding of portato dashes

Hi, I'm so often adjusting the padding of portato dashes (increasing the padding) that I'd like to ask if we should change the built-in default values for that. Opinions? Urs ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Slur padding on dotted notes

Am 12.02.2014 12:48, schrieb James: On 12/02/14 00:06, Jay Anderson wrote: \score { \new Staff \relative c''' { %non-dotted \time 4/4 g4( f) g( a) | g4~ g a~ a | %dotted \time 12/8 g4.( f) g( a) | %Slurs pushed further away than necessary. g4.~ g a~ a

Re: Support german notation

Thomas Scharkowski t.scharkow...@t-online.de schrieb: Sorry, his and hisis do work, as opposed to heses, which does not. There is no hes :-) Yeah, _if_ one would consider this a bug then it would be in the German naming conventions outside of LilyPond :-) Original-Nachricht

Re: treble clef looks horrible in sizes smaller than 20

Am 24.02.2014 22:36, schrieb Karol Majewski: \version 2.19.2 #(set-global-staff-size 18) \clef treble For the sake of reference: The source of the problem seems to have been identified: http://lists.gnu.org/archive/html/lilypond-devel/2014-02/msg00238.html

Re: dodecaphonic-first accidental style

Am 25.03.2014 11:59, schrieb James: On 24/03/14 14:45, Rutger Hofman wrote: On 03/24/2014 01:50 PM, Gilberto Agostinho wrote: Gilberto Agostinho wrote The correct syntax is with the s [...] I meant without without the s, as in repeat and NOT repeats Rutger Hofman-2 wrote [...] As a fix,

Re: dodecaphonic-first accidental style

Am 25.03.2014 11:59, schrieb James: On 24/03/14 14:45, Rutger Hofman wrote: On 03/24/2014 01:50 PM, Gilberto Agostinho wrote: Gilberto Agostinho wrote The correct syntax is with the s [...] I meant without without the s, as in repeat and NOT repeats Rutger Hofman-2 wrote [...] As a fix,

Re: dodecaphonic-first accidental style

Am 26.03.2014 11:16, schrieb Phil Holmes: What is the correct way to deal with this? 3889 should be closed, marked as duplicate or merged in 3890. I'd like to learn how to do that and do it myself rather than simply asking someone to do it. Urs Change the status to duplicate. There will

\voiceOne rest positioning

Hi, I've just updated an example on the German Wikipedia http://de.wikipedia.org/wiki/Notensatzprogramm#Text and noticed that the position of the initial \voiceOne rest is suboptimal. Compare LilyPond's output with that of Score and Amadeus which are both better. I have no clue about the Score

Re: \voiceOne rest positioning

Am 08.04.2014 11:13, schrieb Phil Holmes: Urs Liska lilyli...@googlemail.com wrote in message news:5343080e.4060...@googlemail.com... Hi, I've just updated an example on the German Wikipedia http://de.wikipedia.org/wiki/Notensatzprogramm#Text and noticed that the position of the initial

Re: \voiceOne rest positioning

Am 08.04.2014 13:15, schrieb Phil Holmes: Urs Liska lilyli...@googlemail.com wrote in message news:5343d37c.4070...@googlemail.com... Am 08.04.2014 11:13, schrieb Phil Holmes: Urs Liska lilyli...@googlemail.com wrote in message news:5343080e.4060...@googlemail.com... Hi, I've just updated

Re: add lilypondblog.org to contact page?

Am 22.04.2014 18:48, schrieb Federico Bruni: In this page: http://lilypond.org/contact.html we currently have a link to news.lilynet.net, which have been down for months. I've already opened an issue about lilynet.net links: http://code.google.com/p/lilypond/issues/detail?id=3903 This is to

Re: lilypond-book on Windows needs LaTeX?

Am 21.05.2014 13:44, schrieb Federico Bruni: I'm trying to verify issue 3874. I'm not a Windows user but I have the chance to use a Windows machine at work. When I try to compile the musicological example in Usage, I get a warning about pdflatex being a command not detected. I guess that LaTeX

Website language selection

Hi, I'm not sure if that has been discussed before (I think it has), but I'm quite annoyed with the automatic language selection on lilypond.org. I don't know how this function is realized, but I would strongly prefer if clicking on a link would always open a page in the same language. As it

Re: Website language selection

Am 30.05.2014 10:38, schrieb Phil Holmes: Urs Liska lilyli...@googlemail.com wrote in message news:53883f91.6000...@googlemail.com... Hi, I'm not sure if that has been discussed before (I think it has), but I'm quite annoyed with the automatic language selection on lilypond.org. I don't know

Re: Possible bug with \oneVoice involving rests

Am 02.06.2014 09:33, schrieb Brian Eve: { \clef bass \compressFullBarRests \override Rest #'staff-position = #0 R1*6 { \voiceOneg4. f e4 } \new Voice { \voiceTwo e4. d d4 } \oneVoice a1 R1*6 { \voiceOneb8 } \new Voice { \voiceTwo e8 } r8 r4 r2 R1*6

Re: Possible bug with \oneVoice involving rests

Am 02.06.2014 09:51, schrieb Brian Eve: \version 2.18.2-1 { \clef bass \compressFullBarRests \override Rest #'staff-position = #0 R1*6 g4. e f d e4 d a1 R1*6 b8 e8 r8 r4 r2 R1*6 R1 r R } No, that's very wrong code. With these you are actually

Re: typo in LM 2.18/2.19 (Contributor's guide)

Am 22.06.2014 12:51, schrieb Federico Bruni: Thanks Pierre There's already a patch: https://codereview.appspot.com/109140043/ And it's already pushed to staging :-) Il 22/giu/2014 00:13 Pierre Perol-Schneider pierre.schneider.pa...@gmail.com ha scritto: I'm not top posting. Hi Squad,

Re: accidentalStyle dodecaphonic-no-repeat

Am 05.07.2014 15:50, schrieb Jean-Charles Malahieude: Hi all, On my way in updating translations, I notice that this style seems to not do what it claims. Look at the two successive examples in NR-1.1.3 Automatic accidentals, both styles dodecaphonic and dodecaphonic-no-repeat: there is no

Re: accidentalStyle dodecaphonic-no-repeat

Am 05.07.2014 16:49, schrieb Urs Liska: Am 05.07.2014 15:50, schrieb Jean-Charles Malahieude: Hi all, On my way in updating translations, I notice that this style seems to not do what it claims. Look at the two successive examples in NR-1.1.3 Automatic accidentals, both styles dodecaphonic

Re: unclear topic

Am 07.07.2014 23:23, schrieb Federico Bruni: 2014-07-07 21:40 GMT+02:00 Michael Gabor i...@elala.de: Dear Lilypond-Team, In LM 2.18.2 german version under 2.7.3 Generalbaß at the end of the page is an example on \bassFigureExtendersOn and -Off (as shown in the attached PNG). However, the

Problematic example in LM (was: Re: Multiple voices tie across barline into single voice?)

Am 14.09.2014 17:34, schrieb Mark Stephen Mrotek: Joey, Tying notes across voices located at http://www.lilypond.org/doc/v2.18/Documentation/learning/other-uses-for-tweaks would be a good place to start. Oh, looking at this I find the example is actually _wrong_. The second image shows

Fwd: Isolated durations and \pageBreak

Original-Nachricht Betreff:Isolated durations and \pageBreak Datum: Wed, 24 Sep 2014 19:50:33 +0200 Von:Davide Liessi davide.lie...@gmail.com An: lilypond-u...@gnu.org lilypond-u...@gnu.org Hi all. Isolated durations don't behave well with \pageBreak. The

Re: Fwd: Isolated durations and \pageBreak

Am 24.09.2014 22:11, schrieb David Kastrup: Urs Liska lilyli...@googlemail.com writes: Original-Nachricht Betreff:Isolated durations and \pageBreak Datum: Wed, 24 Sep 2014 19:50:33 +0200 Von:Davide Liessi davide.lie...@gmail.com An: lilypond-u...@gnu.org

Ugly collision between dynamics and crossStaff stem

Hi bug-squad, attached you'll find source and image of an ugly collision between dynamics and a cross-staff stem. The image is from current master but the issue is the same with 2.18.2. Thanks for adding an issue report. Urs \version 2.19.14 \layout { \context { \PianoStaff

Re: Incorrect example in Vocal Music documentation

I think it's the other way round. This syntax changed between 2.16 an 2.18. So I assume he is usong 2.16 and reading 2.18 or 2.19. HTH Urs Am 24. Oktober 2014 14:27:45 MESZ, schrieb pkx166h pkx1...@gmail.com: On 24/10/14 13:10, Greg Swinford wrote: There is an error in the example given on the

Re: Segfault from unusual time signatures

Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version 2.19.0 \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1 } } Compiled without problem on a build from current master (Debian Linux) Urs

Re: Segfault from unusual time signatures

Am 26.10.2014 21:39, schrieb David Kastrup: Urs Liska lilyli...@googlemail.com writes: Am 26.10.2014 21:19, schrieb Dan Eble: % This input caused a segfault on OS X Yosemite with Lilypond 2.19.15. \version 2.19.0 \new Staff { \relative d' { \time 8/1024 d128 | \time 9/1 d1

\partcombine, trill spanner and acciaccatura

Hi all, I'm experiencing an issue with \partcombine. Consider the attached snippet and image. When there is an acciaccatura in one of the voices the trill spanner doesn't stop in the \partcombine-d voice. It doesn't matter in which voice the acciaccatura is. \appoggiatura has the same

Re: \partcombine, trill spanner and acciaccatura

Am 28.10.2014 04:33, schrieb Dan Eble: Urs Liska ul at openlilylib.org writes: Hi all, I'm experiencing an issue with \partcombine. Consider the attached snippet and image. When there is an acciaccatura in one of the voices the trill spanner doesn't stop in the \partcombine-d voice

Re: Pitched rest bug [was: A pause in 3/4 measure]

Am 1. November 2014 21:55:01 MEZ, schrieb Trevor Daniels t.dani...@treda.co.uk: Thomas Morley wrote Saturday, November 01, 2014 12:05 PM Using d1*3/4\rest has a draw-back: The rest will change it's position, if \transpose is used. Copying to bug list. This seems like a bug to me. Do

Time signature position broken

With a build from current master (151120c3240601fd29bbb20a315decbde681fcdb) compiling \version 2.19.16 { c'1 } results in the attached output. This is not related to the concrete example but a general issue: The time signature is printed completely at the left edge of the staff. I suspect

Re: Issue 4205: Improve part combiner's rest analysis (issue 174610043 by nine.fierce.ball...@gmail.com)

I don't know how to properly review this, but I checked against a current score I'm working on, and I see it removes one of the most annoying issues I had so far. Consider this snippet: \version 2.19.16 one = \relative c'' { c2 c \voiceOne r8 c b a g f e d c1 } two = \relative c' {

Re: Issue 4205: Improve part combiner's rest analysis (issue 174610043 by nine.fierce.ball...@gmail.com)

Am 25.11.2014 02:45, schrieb Dan Eble: On Nov 24, 2014, at 04:11 , Urs Liska u...@openlilylib.org wrote: I don't know how to properly review this, but I checked against a current score I'm working on, and I see it removes one of the most annoying issues I had so far. I’m glad to hear

partcombiner should not set solo when a rest is printed in the other voice

Hi all, consider the following \partcombine situation: - voices are merged to a given point - then voices start with different rests, followed by notes in one voice \version 2.19.16 one = \relative c'' { c2 c \voiceOne % this doesn't affect the solo section at all r8 %\voiceOne %

Re: Issue 4205: Improve part combiner's rest analysis (issue 174610043 by nine.fierce.ball...@gmail.com)

Am 25.11.2014 14:50, schrieb Dan Eble: On Nov 25, 2014, at 04:21 , Urs Liska u...@openlilylib.org wrote: Is the following assumption correct? At the beginning of m.2 the partcombiner treats the crotchet and the full measure rests as two voices. Yes. The part combiner directs those rests

Fwd: 3 new lilypond issues

forwarding ... Ursprüngliche Nachricht Von: Jan Hakenberg jan.hakenb...@gmail.com Gesendet: 6. Dezember 2014 07:35:15 MEZ An: James pkx1...@gmail.com CC: Urs Liska u...@openlilylib.org Betreff: 3 new lilypond issues Hi, I briefly searched the open issues, but did not find

Glyph fallback (Fwd: Re: Alternative fonts glyph support)

Dear bug squad, I second Davide's suggestion to add below point 2. as a feature request. Urs Weitergeleitete Nachricht Betreff:Re: Alternative fonts glyph support Datum: Sat, 03 Jan 2015 11:19:32 +0100 Von:Davide Liessi davide.lie...@gmail.com An: tisimst

Re: Retrieving information about breaks

is handle mid-measure breaks, but I know where I can look that up ;-) So this isn't a feature request anymore ... Best Urs Am 23.01.2015 um 17:42 schrieb David Nalesnik: Hi Urs, On Fri, Jan 23, 2015 at 9:33 AM, Urs Liska u...@openlilylib.org mailto:u...@openlilylib.org wrote: Picking up

Re: How to pack notes very tightly?

-shortest-duration to adjust horizontal spacing ( http://www.lilypond.org/doc/v2.16/Documentation/notation/changing-horizontal-spacing), but in fact, it seems as though common-shortest-duration is the variable that really needs to be tweaked. Steve On Mon, Jan 19, 2015 at 11:07 PM, Urs Liska u

Re: How to pack notes very tightly?

Am 20. Januar 2015 13:25:25 MEZ, schrieb James p...@gnu.org: On 20/01/15 07:29, Urs Liska wrote: Forwarding to bug-lilypond. Could someone please verify this Verify what precisely? If what the NR states is wrong. Or if it needs enhancement by the other property. James and create

wish: ly:cheapest-breaking (or whatever name)

Hi list, following up on a thread that I started some time ago (http://lists.gnu.org/archive/html/lilypond-devel/2014-11/msg00139.html) I'd like to draw the conclusions from that and ask for an additional breaking algorithm. It would be nice to have a compilation mode that doesn't care

Problem with enharmonic tie in partcombine (can let LilyPond crash)

Hi, I encountered a strange crash that is related to enharmonic ties. I'm using an engraver that is passed a grob. One particular snippet of input code lets now crash LilyPond. I can't easily produce a compiling (i.e. crashing) example because it's quite intertwined with project specific

Output break positions (question or feature request)

Hi, as asked on the -user list I am looking for a way to collect the positions of all breaks in a LilyPond score. http://lists.gnu.org/archive/html/lilypond-user/2015-01/msg00185.html suggests that at the time engravers are doing their work the line and page breaking hasn't been performed so

Re: Typo in NR example (vocal music)

Am 09.01.2015 um 16:00 schrieb Ralph Palmer: On Wed, Jan 7, 2015 at 4:50 AM, Urs Liska u...@openlilylib.org mailto:u...@openlilylib.org wrote: Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music.html there's a typo in the example

Typo in NR example (vocal music)

Hi all, on http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-vocal-music.html there's a typo in the example about special characters (with the text Schad' um das schöne grüne Band). The sixth note should read es' instead of e'. I'd fix that myself but I have problems

Re: cadence font and lilypond-book

Am 17.03.2015 um 11:20 schrieb Marc Hohl: Am 17.03.2015 um 10:57 schrieb Urs Liska: Am 17.03.2015 um 10:53 schrieb Marc Hohl: Am 17.03.2015 um 10:27 schrieb Urs Liska: [...] does not help here, lilypond-book has ceased to work, obviously. I checked the contents of lilypond-book

Re: cadence font and lilypond-book

Am 17.03.2015 um 09:57 schrieb Marc Hohl: Am 17.03.2015 um 09:36 schrieb Urs Liska: Am 17.03.2015 um 09:32 schrieb Marc Hohl: Hi list, hi Abraham, I asked about this subject before, but now I think I did everything right, but still ... I use the self-compiled lilypond and install

Re: cadence font and lilypond-book

Am 17.03.2015 um 10:53 schrieb Marc Hohl: Am 17.03.2015 um 10:27 schrieb Urs Liska: [...] does not help here, lilypond-book has ceased to work, obviously. I checked the contents of lilypond-book in a number of installations and have the impression there's a quite serious bug (if I'm

Re: cadence font and lilypond-book

Am 17.03.2015 um 10:27 schrieb Urs Liska: I can't test it because I don't have any .lytex files available, but obviously there should be some point in the build/installation process that determines the correct paths relative to the installation directory. Oops, no. Of course the include

Re: website: new screenshots for Denemo and Frescobaldi?

Am 14.03.2015 um 13:21 schrieb Federico Bruni: Hi all What about adding new screenshots for Denemo and Frescobaldi? Good idea. They are on top of the easier editing page and the images are very out-of-date. I've uploaded some here: http://sixbarsjail.it/tmp/lily/ I did not put too much

Retrieving information about breaks (was: Partial compilation (again))

break points of a given LilyPond run. If that's not currently accessible I'd like to add that as a feature request. Urs Am 21.11.2014 um 14:44 schrieb Urs Liska: Am 21.11.2014 13:33, schrieb David Kastrup: Urs Liska u...@openlilylib.org writes: Am 21. November 2014 12:36:59 MEZ, schrieb

Re: wish: ly:cheapest-breaking (or whatever name)

Am 23.01.2015 um 13:35 schrieb Ralph Palmer: On Mon, Jan 19, 2015 at 9:33 AM, Urs Liska u...@openlilylib.org mailto:u...@openlilylib.org wrote: Hi list, following up on a thread that I started some time ago (http://lists.gnu.org/archive/html/lilypond-devel/2014-11/msg00139.html

Issue with symbol-list? and ly:parser-include-string

As this thread suggested https://lists.gnu.org/archive/html/lilypond-devel/2015-03/msg00193.html there is an issue with the parser when a symbol-list? predicate is used as a function argument and ly:parser-include-string in that function. As it turned out the problem is reproducible with very

Re: compile failure - parsed object should be dead in 2.19.20

releases. It is related to calling a system vs. a packaged Ghostscript. At least it doesn't seem to be an issue with my personal configuration ... Urs -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https

Re: my favorite bug :-)

Am 01.05.2015 um 13:53 schrieb Masamichi HOSODA: The bug would be fixed if lilypond would make ghostscript use a complete path to the intermediate lines.ps file for the ps to pdf conversion. Does anyone know how to convert from any path (relative and absolute path) to absolute path in scheme

Re: Ghostscript problem in 2.19.18

Am 14.04.2015 um 16:22 schrieb Masamichi HOSODA: OK. Compiling a file with lilypond-2.19.18-1.linux-x86.sh ends with Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./document.pdf

Ghostscript problem in 2.19.18

Hi, just trying out the binary releases again, and I notice that with 2.19.18 all documents fail with the following message: Layout output to `document.ps'... Converting to `./document.pdf'... warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 16:04 schrieb Masamichi HOSODA: I have just installed lilypond-2.19.18-1.linux-x86.sh on another machine running Debian 7 stable with latest updates. And the error is identical. Maybe (this is a big maybe) I'll have a chance to test it on another (different) 32bit Linux

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 14:19 schrieb Masamichi HOSODA: This is on Debian with the linux-386 binary and applies to _any_ file, even { c } . Compiling with the 2.19.17 binary works. Compiling with the 2.19.18 binary fails. Compiling with a custom build from current master works. As there are no

Re: Ghostscript problem in 2.19.18

Am 13.04.2015 um 16:47 schrieb Masamichi HOSODA: gs: Interpreter revision (905) does not match gs_init.ps revision (915). lilypond-2.19.18-1.linux-x86.sh includes gs-9.15. However, lilypond seems to be invoking the external gs-9.05 instead of included gs-9.15. My ubuntu 64 bit environment

Re: musicxml2ly doesn't handle nested tuplets

Am 5. Juni 2015 13:55:04 MESZ, schrieb Ralph Palmer ralphbugl...@gmail.com: On Tue, Jun 2, 2015 at 10:54 AM, Urs Liska u...@openlilylib.org wrote: When dealing with export of nested tuplets to MusicXML ( https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can

\tempo collision with cross staff beam

Hi bug squad, I ran into a collision bug. With a cross-staff beam present \tempo doesn't take any objects above the staff into account. If you comment out the beam in the following example the \tempo is correctly shifted upwards to accomodate the dynamic. Result is identical with 2.18.2 and

musicxml2ly doesn't handle nested tuplets

When dealing with export of nested tuplets to MusicXML (https://github.com/wbsoft/python-ly/issues/25) I realized that the exported MusicXML can be properly read by Finale but not be reimported through musicxml2ly. https://github.com/wbsoft/python-ly/issues/25#issuecomment-107363569 shows how

Re: Accidentals tied over a system break

Am 8. Oktober 2015 19:59:57 MESZ, schrieb Sven : >Sorry, I didn't know this is a known issue. > >And thanks for correcting me on how to actually remove the second >sharp, >Urs: \once \omit Accidental get's rid of the bugger, while \once \hide >Accidental makes it

Remove old News entry from home page

Hi, I've just stumbled over it again: The first thing you see on lilypond.org after the latest release informations is the news item about the Fried edition prize. I really think this should be either removed or pushed downward by new news. Isn't there anything worthwile that can be added here?

Re: PDF Links in Windows

Am 05.10.2015 um 11:18 schrieb Federico Bruni: > Il giorno lun 5 ott 2015 alle 10:57, Federico Bruni > <f...@inventati.org> ha scritto: >> Il giorno lun 5 ott 2015 alle 9:54, Urs Liska <u...@openlilylib.org> ha >> scritto: >>> I think what he wants is the f

Re: PDF Links in Windows

Am 05.10.2015 um 15:04 schrieb Henning Hraban Ramm: > On OSX, my old Acrobat Pro 9 as well as Adobe Reader 11 try to open > LilyPond’s "textedit://" links with LilyPad, after asking if they may or > should block such attempts. So the "security reasons" seem to apply only on > Windows (I don’t

Re: Another beam subdivision issue

e it a try. Of course ready-made solutions are OK too, but I'd be willing to learn ... Best Urs Am 25.11.2015 um 16:34 schrieb Urs Liska: > After completing my patch for #4664 I tested beam subdivision with > another example and was unpleasantly surprised that the other example > prod

Re: Fontmap entry for Fontmap.local ends prematurely!

Am 07.12.2015 um 00:24 schrieb Karl Berry: > We have no plans for any more 2.18.x releases, so ca you confirm if you > still get the same problem when using the lastest development (2.19.x) > available download? > > The old version is working ok for my (minimal) purposes for the

Command line option to have barcheck failures cause errors instead of warnings

Hi, there was the request for a way to have barcheck failures cause errors instead of warnings: http://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00074.html I think this is a valid use case as very often you don't actually want to have the compiled score when it contains barcheck

Re: Noteheads slightly too large

Am 12.12.2015 um 00:02 schrieb Simon Albrecht: > Thanks for the report. > This *may* be intended, which should be checked - if someone recalls any discussion. At least I recall speaking someone from a major publishing house about how they

Re: Noteheads slightly too large

Am 12.12.2015 um 11:11 schrieb Simon Albrecht: > On 12.12.2015 00:43, Urs Liska wrote: >> >> Am 12.12.2015 um 00:02 schrieb Simon Albrecht: >>> Thanks for the report. >>> <https://sourceforge.net/p/testlilyissues/issues/4693/> >> This *may* be intended,

Another beam subdivision issue

After completing my patch for #4664 I tested beam subdivision with another example and was unpleasantly surprised that the other example produced a wrong result. This example should render the subdivisions with a regular alternation of two and one beams. Instead all beam subdivisions show two

Ugly collision when acciaccatura is followed by downward stem

I encountered a rather ugly rendering of an acciaccatura. As you can see in the first attachment the slurs is colliding pretty hard with the beam. In addition, it seems that an acciaccatura's slur always crosses the stem of the following note if that happens to be downwards, see the second

Re: Ugly collision when acciaccatura is followed by downward stem

Am 26.11.2015 um 12:16 schrieb lilyp...@maltemeyn.de: > Am 2015-11-26 10:33, schrieb Urs Liska: >> PS: A non-bug question: I tweaked that slur using \shape, but could >> someone give me a hint as to use other properties to override, so the >> slur doesn't cross the

Re: slurs with more than 2 control points

list archive at Nabble.com. > _______ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond > -- Urs Liska www.openlilylib.org ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

SubdivideBeam gives undesired result when beaming over more than a quarter note

Since the fix for #4355, respectively commits 8fa2d858 and 0382ed88, it is not possible anymore to subdivide beams that are longer than a quarter note. \version "2.19.32" { \set subdivideBeams = ##t % This is correctly subdivided \set baseMoment = #(ly:make-moment 1 8) \repeat unfold 16

Re: Problem understanding subdivided beam

e -> no beam. I've written a feature request/bug report to bug-lilypond. Urs > > Cheers, > Jan-Peter > > Am 19.11.2015 um 09:42 schrieb Urs Liska: >> Hi, >> >> I have a problem getting a beam subdivision right, and I can't seem to >> find a solutio

dynamics-barline collision

Hi list, I am somewhat surprised that dynamics can still collide with barlines as shown in the attached image. I thought this kind of issue had been quite long overcome. The \pp is defined in a Dynamics context, and of course I can work around the collision by overriding self-alignment-X. But is

Irregularity in horizontal spacing

Hi, one more question. I am right now experiencing an irregularity in the horizontal spacing that is very small but still pretty annoying. In the attached image you can see how the quavers are spaced out irregularly. It is most obvious in the melody staff but you can also see it in the piano

Re: Irregularity in horizontal spacing

regularly. And in effect inacceptably. As I have to get that score ready ASAP I can't wait for a proper fix (if it should be considered a bug) but need a workaround that works better than having to space the notes in all measures manually. Urs > - Abraham > > On Friday, November 20, 2015, Urs L

Re: Irregularity in horizontal spacing

Weitergeleitete Nachricht Betreff: Re: Irregularity in horizontal spacing Datum: Fri, 20 Nov 2015 23:04:42 +0100 Von: Urs Liska <u...@openlilylib.org> An: bug-lilypond@gnu.org Am 20.11.2015 um 17:09 schrieb tisimst: > Are you referring to the final 16ths in each of t

Re: Irregularity in horizontal spacing

(space) #{ \extraSpace #(car space) #(cdr space) #}) spaces)) which now allows me to write \extraSpaces #'((3 . 3) (3 . 6)) etc. Best Urs Am 21.11.2015 um 01:06 schrieb Urs Liska: > > Am 21.11.2015 um 00:01 schrieb Simon Albrecht: >> On 20.11.2015 23:19, Urs

Re: Irregularity in horizontal spacing

Am 23.11.2015 um 09:57 schrieb Simon Albrecht: > On 23.11.2015 09:49, Urs Liska wrote: >> Just to finish this thread up (apart from the opened issue) I'll report >> how I finally dealt with the issue in my score. >> >> It turns out that >> \override Spacin

Re: SubdivideBeam gives undesired result when beaming over more than a quarter note

d server (host[:port]) [codereview.appspot.com]: Allura server []: You must provide the address of the Allura tracker server: ``` What should I do now? Urs Am 19.11.2015 um 10:43 schrieb Urs Liska: > Since the fix for #4355, respectively commits 8fa2d858 and 0382ed88, it > is not possible

Re: Can't download Lilypond(!)

Am 04.06.2016 um 15:33 schrieb Mike: > Hi there, I'm using the link offered on your webpage > http://download.linuxaudio.org/lilypond/binaries/linux-64/lilypond-2.18.2-1.linux-64.sh > but it's not working, is the server down? I've been trying since this > morning... > > Unable to connect >

Re: Wrongly combined note heads

Am 23.06.2016 um 09:19 schrieb Andrew Bernard: > Fixing lilypond would presumably > mean adopting one particular style that may not be what everybody wants. or rather: setting *a default* that not everybody wants. But having to override the default because it's not your preferred way is clearly

ly:one-line-breaking doesn't properly handle indent value/side margins

Hi, while testing the new #ly:one-line-auto-height-breaking I noticed some issues with the already available #ly:one-line-breaking. It seems the left and right margins are not properly handled in that mode: The right margin is way too large to my eyes, which you can see when setting

Re: ly:one-line-breaking doesn't properly handle indent value/side margins

Am 18.01.2016 um 17:04 schrieb Urs Liska: > Hi, > > while testing the new #ly:one-line-auto-height-breaking I noticed some > issues with the already available #ly:one-line-breaking. > > It seems the left and right margins are not properly handled in that mode: > > The

git-cl traceback (timeout?)

When uploading a patch git-cl failed with the transcript below: I'm not sure if that's caused by git cl (I had just pulled the newest version) or if it's a simple time-out on my side, but: a) If it's a git-cl issue it should be fixed b) If it's a time-out such an error should be handled by

Re: git-cl traceback (timeout?)

Am 19.01.2016 um 12:29 schrieb Trevor Daniels: > Hi Urs > > What did you enter in response to the query? I pressed ENTER (to create a new issue item) Urs > > Trevor > > - Original Message - > From: "Urs Liska" <u...@openlilylib.org> > T

Re: Fwd: lilypond-book/pdflatex: LaTeX Error: Environment lilypond undefined.

I *think* it's wrong usage, but I didn't have the time to inspect too closely. The error message about the undefined \lilypond environment indicates that LaTeX tries to compile the original file and not the one processed by lilypond-book. The OP should check the *actual* result of the

<    1   2   3   4   >