Re: \tempo indication not printed
Am Monday, 5. September 2011, 09:41:58 schrieb Dmytro O. Redchuk:
On Thu 01 Sep 2011, 16:06 Reinhold Kainhofer wrote:
BTW, this is a really minimal example:
\version 2.15.9
{
s1
\tempo Waldo
s1
}
Neil mentioned issue 1276. What do you think, should this one be a separate
issue?
AFAICS, it's a separate issue. 1276 wrongly aligns on the note, even if it
should align on other grobs, while this issue does not print the mark at all,
because there is no column to attach that survives.
cheers,
Reinhold
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1865 in lilypond: tempo indication can not be attached to spacers
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 1865 by brownian.box: tempo indication can not be attached to
spacers
http://code.google.com/p/lilypond/issues/detail?id=1865
Reported by Valentin Villenave,
http://lists.gnu.org/archive/html/bug-lilypond/2011-09/msg00037.html :
%8-
\version 2.15.9
{
s1
\tempo Waldo
s1
}
%8-
Reinhold commented:
%8-
The issue is that the moment after the \tempo command does not have any
grobs where the tempo could be attached to. As soon as you change the s1 to
a note or rest, or if you have clef/key/timesig change at the same moment
as the \tempo, the tempo mark can be reparented. But it seems that the
engraver misses the case that there are no other grobs at the same moment
as the \tempo change. In that case, the tempo mark should be reparented to
the barline...
%8-
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: dynamics on chords with notehead to left and right of stem arewrongly aligned
Reinhold Kainhofer wrote Monday, September 05, 2011 12:45 AM
Dynamics on chords with a notehead to the left and to the right of
the
stem align differently than when there are only noteheads to the
right.
It's even worse :( The alignment of dynamics against a chord
depends on which note appears first in the chord definition.
Well, maybe it's worse - this way one can at least choose
which note to align to. Here's the input, output attached.
\version 2.15.8
% Dynamics on chords with a note head to the left and to the right
of the
% stem align differently when the order of notes is changed
\score {
\new Staff \relative c'' { c d2\pp }
\new Staff \relative c'' { d c2\pp }
}
What should Lily do in this case? Align to the stem?
Trevor
attachment: dynamic_alignment.jpg___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets
Updates: Status: Fixed Labels: -Patch-push fixed2_15_10 Comment #14 on issue 1742 by janek.li...@gmail.com: print transposed guitar chords on piano sheets http://code.google.com/p/lilypond/issues/detail?id=1742 pushed as 7770772b6101f60b28173fd68ceb701048016b21 closed ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets
Comment #15 on issue 1742 by n.putt...@gmail.com: print transposed guitar chords on piano sheets http://code.google.com/p/lilypond/issues/detail?id=1742 Just a comment on this: I did object to the use of a shim to post-process the chord name markup, since there's now a disconnect between the chord name formatter and what actually might get set as the markup text. We don't generally use ly_lily_constant_module to generate markup unless it's actually accessing a markup command. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1775 in lilypond: LSR: add broken- and unbroken slur shaping function
Comment #20 on issue 1775 by lilyli...@googlemail.com: LSR: add broken- and unbroken slur shaping function http://code.google.com/p/lilypond/issues/detail?id=1775 Thanks for making this available. But I still find it confusing that the usage of the version for broken slurs isn't mentioned at all in the text of the snippet (but only in the source). So I suggest a different text: - If you want to adjust the shape of a slur, one way is to specify a new list of control-points. The function presented here offers a different approach by allowing you to adjust existing control-points. This is done by entering a list of offsets (in staff spaces) to the default coordinates: \shapeSlur #'(x1 y1 x2 y2 x3 y3 x4 y4) Setting a value to 0 leaves the default coordinate unchanged, so it is easy to maintain a slur's attachment-points while changing its interior. This version of the function is also able to deal with slurs that are broken. You can shape the different parts of the broken slur by entering separate lists of offsets for each part: \shapeSlur #'((x1 y1 x2 y2 x3 y3 x4 y4) (xx1 yy1 xx2 yy2 xx3 yy3 xx4 yy4) (xxx1 yyy1 xxx2 yyy2 xxx3 yyy3 xxx4 yyy4) ) If you use an empty bracket the corresponding part of the slur isn't changed at all from LilyPond's default decision. This snippet is a revised version, by David Nalesnik, of the original (snippet 639). Is this too long for a snippet? If no, could it just changed on LSR? Should the issue be reopened or just corrected? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source
Updates: Status: Fixed Comment #1 on issue 1864 by percival.music.ca: lilypond.org does not use lilypond-git for source http://code.google.com/p/lilypond/issues/detail?id=1864 I have added a symlink, and I believe it is now done. I have not yet updated the website-building scripts, but once they are fixed in the CG, I'll copypaste them into the webserver. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
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. The way the code had been written originally, I suspect that it was written with a particular use case in mind. My guess would be that the side-effects were worse than the cure, but until we get an explicit report of the purported problem, I would prefer to have the code stick with the straightforward version that corresponds with both function name as well as documentation. The use case was wanting to make sure that the TabStaff and the FretBoards both used the same tuning to avoid the possibility of an error. The current version is clearly better. No need to go back to try to implement the old use case. Actually, I don't like the entire approach all too much, so I am currently working on making a define-scheme-function thingy that can take Lilypond arguments like define-music-function but produces not a music but a Scheme expression. That would be much nicer than the current usage. IMO, the best practice would be to do a \makeStringTuning, at the top of the file, then as needed instantiate your TabStaff and FretBoards contexts with the named string tuning. Thanks, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1864 in lilypond: lilypond.org does not use lilypond-git for source
Comment #2 on issue 1864 by percival.music.ca: lilypond.org does not use lilypond-git for source http://code.google.com/p/lilypond/issues/detail?id=1864 I'll verify this myself once the updated scripts are in play. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets
Updates: Labels: -fixed2_15_10 fixed_2_15_10 Comment #16 on issue 1742 by tdaniels...@googlemail.com: print transposed guitar chords on piano sheets http://code.google.com/p/lilypond/issues/detail?id=1742 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1866 in lilypond: Uses langdefs.py to create language list for create-weblinks-itexi.py
Status: Accepted Owner: Labels: Type-Build Patch-review New issue 1866 by pkx1...@gmail.com: Uses langdefs.py to create language list for create-weblinks-itexi.py http://code.google.com/p/lilypond/issues/detail?id=1866 Patch 1 demonstrates how to import a library into a python file where the path is not already in the pathlist. It half-fixes the issue where languages are defined in many places in make website - the other needs changes to website.make, but there is a problem with that since the variable PYTHON is not guaranteed to be defined. Patch 2 should be read in conjuction with the change to the CG pushed as 022d5c7ef759c586e3ca6478cf5f1b5d56d31778. This shows how to set PYTHONPATH as part of the call to make, to allow python to find included libraries. Note the comment about the definition of the PYTHON variable. This is defined in config.make.in which is called with a normal call to make website, but not with the out-of-build-tree version documented in the CG section as above. Setting this as part of the call will be the next step. http://codereview.appspot.com/4951047/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1663 in lilypond: Images missing on web site
Comment #37 on issue 1663 by pkx1...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 graham_percival-music.ca 5 days, 14 hours ago #6 On Mon, Aug 29, 2011 at 05:24:51PM +0100, Phil Holmes wrote: OK. My claim that this is fixed is partly down to the number of copies of web-big-page.html on the system after a build. It's fixed in the wrong one, but not fixed in the right one. To get my head fully around this, I think I need to be able to run lots of full make doc sessions. I need to wait a couple of weeks for my new machine to be delivered. ok. Another option would be to sort out the locations of css/ and pictures/, and/or add some symlinks, instead of modifying the texinfo+html. http://code.google.com/p/lilypond/issues/detail?id=983 But that's also something that should wait until your new computer. :) Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1405 in lilypond: Web: website Google search-bar should allow to search the website.
Updates: Status: Accepted Labels: Patch-needs_work Comment #3 on issue 1405 by pkx1...@gmail.com: Web: website Google search-bar should allow to search the website. http://code.google.com/p/lilypond/issues/detail?id=1405 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1838 in lilypond: Make accidental styles available as context mods
Updates: Labels: -Patch-push Patch-review Comment #3 on issue 1838 by pkx1...@gmail.com: Make accidental styles available as context mods http://code.google.com/p/lilypond/issues/detail?id=1838 Not sure this should be patch-push after the comments in http://codereview.appspot.com/4819064/. Setting to review. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1193 in lilypond: [PATCH] Enhancement: internal ledger lines
Updates: Owner: n.putt...@gmail.com Comment #10 on issue 1193 by pkx1...@gmail.com: [PATCH] Enhancement: internal ledger lines http://code.google.com/p/lilypond/issues/detail?id=1193 Neil is this patch really abandoned? The rietveld is still open so we'd like to just tie up the loose ends. http://codereview.appspot.com/1855056/ James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options
Status: Accepted Owner: reinhold...@gmail.com Labels: Type-Build Patch-new New issue 1867 by pkx1...@gmail.com: Flush all ports after each file, flush stdout after displaying all options http://code.google.com/p/lilypond/issues/detail?id=1867 Flush all ports after each file, flush stdout after displaying all options So far, the output of the safe.ly regtest showed up randomly in some later regtest, because stdout was buffered when redirected to a file. This patch flushes all ports after each processed file (only relevant when multiple files are processed at once). Unfortunately, it seems stdout is not an open Scheme port when Scheme doesn't print anything to stdout. So, when displaying all options, we have to flush stdout directly after printing all options. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests.
Updates: Labels: -Patch-push Patch-review Comment #3 on issue 1833 by pkx1...@gmail.com: Deprecate \fermataMarkup for full-bar rests. http://code.google.com/p/lilypond/issues/detail?id=1833 Again not sure this is pushable from comment since - setting to Patch review Also do we need doc changes in the NR? if so we probably need a new tracker (so that we can focus on this one being for the code change push). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options
Updates: Labels: -Patch-new Patch-review Comment #2 on issue 1867 by pkx1...@gmail.com: Flush all ports after each file, flush stdout after displaying all options http://code.google.com/p/lilypond/issues/detail?id=1867 Passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
doubled accidental
I'm not top posting. If the initial key sets a note flat (b-flat minor) and I later change this note to sharp (ges to gis), in the score I get two accidentals in a row: first a natural and right to it the sharp. There is no need of the natural, it only disturbs. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions
Status: Accepted
Owner: d...@gnu.org
Labels: Type-Other Patch-needs_work
New issue 1869 by pkx1...@gmail.com: Parser.yy: rearrange to allow more
lenient use of music arguments for music functions
http://code.google.com/p/lilypond/issues/detail?id=1869
parser.yy: rearrange to allow more lenient use of music arguments for music
functions.
This change may be somewhat contentious: it removes a lot of
opportunities for syntax errors by allowing a lot of music functions
to work that did not do so previously.
For one thing, you can use a ly:music? style signature as often as you
want to in all music functions. There are some cases where it will
only be accepted in closed form, namely as a music identifier or a
music expression enclosed in { ... } or ... . Those cases are
before a post-event not belonging to the music argument, or a duration
argument.
Music functions can be used in a number of places with different
semantics, not necessarily the cleanest thing. When they are used as
post-events and have a music argument last, they will actually try
getting a post-event as that music argument. What is new (and
probably less than fabulous) that they will instead accept a closed
form music expression.
However, when such a function is used as a primary music event, its
last argument will be a regular music expression anyway. So it is not
like this argument dichotomy was really all that novel.
In a similar vein, as a chord constituent, a music function will
accept a chord constituent in the place of a prospective last music
argument.
It does not seem overly satisfactory that only the last such component
will be syntactically warped according to the surrounding. Perhaps
one should use different signatures in the first place.
Suggestions welcome.
http://codereview.appspot.com/4815052/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doubled accidental
On 9/5/2011 7:55 PM, Maxim Gawrilow wrote: I'm not top posting. If the initial key sets a note flat (b-flat minor) and I later change this note to sharp (ges to gis), in the score I get two accidentals in a row: first a natural and right to it the sharp. There is no need of the natural, it only disturbs. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond This is the default behavior of LilyPond and is, in fact, a standard practice. This is not a bug so I'm also posting to lilypond-user. You can change this. See: http://lilypond.org/doc/v2.14/Documentation/notation/writing-pitches#accidentals -David ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1868 in lilypond: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly)
Updates: Labels: -Patch-new Patch-needs_work Comment #1 on issue 1868 by pkx1...@gmail.com: Loglevels in our python scripts (lilypond-book, musicxml2ly, convert-ly) http://code.google.com/p/lilypond/issues/detail?id=1868 Patch no longer applies to current tree. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1870 in lilypond: replace DIGIT token class with UNSIGNED
Status: Started Owner: d...@gnu.org Labels: Type-Other Patch-needs_work Warning New issue 1870 by pkx1...@gmail.com: replace DIGIT token class with UNSIGNED http://code.google.com/p/lilypond/issues/detail?id=1870 replace DIGIT token class with UNSIGNED Do _not_, I repeat, do _not_ merge. This patch passes regression testing. It removes the token class DIGIT (single-digit unsigned constants) and replaces it by UNSIGNED (previously multiple-digit unsigned constants, now any unsigned constants). Every previous occurence of UNSIGNED in the grammar has been _removed_: instead every occurence of DIGIT has been _replaced_ with UNSIGNED. The result is that single-digit unsigned constants are interpreted by the grammar just like they were before. For example, xxx=-3 creates a variable containing a _fingering_ event instead of a numeric value of -3. Multiple-digit unsigned numbers, however, will be interpreted as strange as previously just single-digit constants were. So xxx=-30 also creates a variable containing a fingering event rather than a numeric constant. I consider the resulting grammar bordering on insane but have been unable to come up with a grammar without additional shift/reduce conflicts that would have resolved this particular nuisance the other way round. So this is just food for thought. http://codereview.appspot.com/4311041/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1248 in lilypond: GUB produces a random unbound open-file in regtests
Comment #5 on issue 1248 by percival.music.ca: GUB produces a random unbound open-file in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 this may be solved with issue 1867. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets
Comment #17 on issue 1742 by lemniska...@gmail.com: print transposed guitar chords on piano sheets http://code.google.com/p/lilypond/issues/detail?id=1742 Neil: Sorry! I thought that if issue has label patch-push, there is nothing more to do than push. Should i revert? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1781 in lilypond: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x
Updates: Status: Fixed Labels: fixed_2_15_9 Comment #8 on issue 1781 by percival.music.ca: Mac OS X 10.7 (Lion) cannot run LilyPond 2.14.x http://code.google.com/p/lilypond/issues/detail?id=1781 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1871 in lilypond: Several fixes for annotate-spacing
Status: Started Owner: joenee...@gmail.com Labels: Type-Enhancement Patch-new New issue 1871 by pkx1...@gmail.com: Several fixes for annotate-spacing http://code.google.com/p/lilypond/issues/detail?id=1871 Several fixes for annotate-spacing. Fixes annotate-spacing to use the new spacing names. Annotates spacing between staves as well as spacing between systems. Fixes some collisions between annotations. http://codereview.appspot.com/4724041/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1871 in lilypond: Several fixes for annotate-spacing
Comment #1 on issue 1871 by pkx1...@gmail.com: Several fixes for annotate-spacing http://code.google.com/p/lilypond/issues/detail?id=1871 Last comment by Neil: Neil Puttock 1 month, 3 weeks ago Hi Joe, Do you have a follow-up patch which defines ly:get-spacing-spec? Cheers, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1871 in lilypond: Several fixes for annotate-spacing
Updates: Labels: -Patch-new Patch-needs_work Comment #2 on issue 1871 by pkx1...@gmail.com: Several fixes for annotate-spacing http://code.google.com/p/lilypond/issues/detail?id=1871 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1869 in lilypond: Parser.yy: rearrange to allow more lenient use of music arguments for music functions
Updates: Status: Invalid Labels: -Type-Other -Patch-needs_work Comment #1 on issue 1869 by d...@gnu.org: Parser.yy: rearrange to allow more lenient use of music arguments for music functions http://code.google.com/p/lilypond/issues/detail?id=1869 This has actually already been pushed some time ago. The long-winded huff-haugh boils down to things appear less than perfect afterwards, but are upwards-compatible to before and an improvement. So short of more convincing feature requests, this should be closed. I closed the Rietveld issue: it had a comment remaining that suggested how to do a nice regtest/demo of functionality once certain syntax was available. The syntax actually _is_ now available, but I found that using it in the proposed manner is not particularly useful since it basically does not apply to much more than just ties. More useful proposals for a regtest should become separate feature requests. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1742 in lilypond: print transposed guitar chords on piano sheets
Comment #18 on issue 1742 by percival.music.ca: print transposed guitar chords on piano sheets http://code.google.com/p/lilypond/issues/detail?id=1742 Yes, please revert it. Yes, if a patch has the label patch-push, it should be pushed -- but it appears that that one fell through the cracks. Mistakes happen, no big deal. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1872 in lilypond: update the address of git-cl source files
Status: Started Owner: janek.li...@gmail.com Labels: Type-Documentation Patch-review New issue 1872 by janek.li...@gmail.com: update the address of git-cl source files http://code.google.com/p/lilypond/issues/detail?id=1872 git://neugierig.org/git-cl.git is down replacing with https://github.com/martine/git-cl in CG http://codereview.appspot.com/4967054 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1248 in lilypond: GUB produces a random unbound open-file in regtests
Comment #6 on issue 1248 by reinhold...@gmail.com: GUB produces a random unbound open-file in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 Right, I was actually trying to fix this bug when I wrote the patch mentioned in issue 1867... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1248 in lilypond: GUB produces a random unbound open-file in regtests
Comment #7 on issue 1248 by reinhold...@gmail.com: GUB produces a random unbound open-file in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 Issue 1867 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1248 in lilypond: GUB produces a random unbound open-file in regtests
Updates: Status: Started Labels: Patch-review Comment #8 on issue 1248 by reinhold...@gmail.com: GUB produces a random unbound open-file in regtests http://code.google.com/p/lilypond/issues/detail?id=1248 Patch up (originall attached to issue 1867) http://codereview.appspot.com/4956062/ ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1867 in lilypond: Flush all ports after each file, flush stdout after displaying all options
Updates: Status: Duplicate Mergedinto: 1248 Comment #4 on issue 1867 by reinhold...@gmail.com: Flush all ports after each file, flush stdout after displaying all options http://code.google.com/p/lilypond/issues/detail?id=1867 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1663 in lilypond: Images missing on web site
Comment #38 on issue 1663 by reinhold...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 IIUC, symlinks are a problem in Windows, that's why we are copying files all over the place... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1835 in lilypond: no learing manual pdf in dutch
Updates: Labels: -Patch-review Patch-push Comment #6 on issue 1835 by colinpkc...@gmail.com: no learing manual pdf in dutch http://code.google.com/p/lilypond/issues/detail?id=1835 This had a countdown to Aug 31. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1833 in lilypond: Deprecate \fermataMarkup for full-bar rests.
Comment #5 on issue 1833 by colinpkc...@gmail.com: Deprecate \fermataMarkup for full-bar rests. http://code.google.com/p/lilypond/issues/detail?id=1833 Now I'm completely confused, but it looks as though Patch Needs Work might not be appropriate, so let's let this one simmer a couple of days! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: doubled accidental
Maxim Gawrilow eldrad.ulthran at o2online.de writes:
If the initial key sets a note flat (b-flat minor) and I later change this
note
to sharp (ges to gis), in the score I get two accidentals in a row: first a
natural and right to it the sharp. There is no need of the natural, it only
disturbs.
This has been fixed for version 2.14.2
Specifically, given input
{ \key bes\minor gis' eses' es' }
LilyPond prints single sharp for the gis, but prints a natural-flat
for the es, unless you change extraNatural to #f as David indicated.
The thinking is that classical-period music often wrote the extra natural
when a single-flat followed a double-flat, presumably because it looked
strange to write a flat alone when the pitch is /raised/ relative the last
instance of that note, especially when compared to the use of relative
accidentals in baroque music.
A sharp following a flat was much less common in the classical period,
so there is no clear standard notation for that case. I believe there
are zero users who want LilyPond to automatically insert an extra natural
between ges and gis.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
