Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Comment #13 on issue 1349 by pnorcks: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 Ian, check out my dev/patrick branch and see if any files from scm/ still fail to compile. I haven't tested this in a while, so something may have broken again... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1682 in lilypond: Website version links need updating
Comment #7 on issue 1682 by colinpkc...@gmail.com: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 Reported by Frederico: on the docs download page, the link labelled 2.12 redirects to 2.14 instead. I've found that manuals.itexi refers properly to http://lilypond.org/doc/v2.12/Documentation/ but gets redirected when I c/p into a browser. I believe the fix is in lilypond.org.htaccess where both 2.12 and 2.13 appear as hard-wired values, and I'll send the resulting patch directly to Graham. I'm conscious that I may be floundering, but a sacrifice of dignity may well lead to an increase of knowledge, so wotthehell, archie. BTW: the other inconsistency was the old lilypond.org/web address. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1704 in lilypond: Website: old version of website still active
Updates: Status: Duplicate Mergedinto: 1272 Comment #1 on issue 1704 by percival.music.ca: Website: old version of website still active http://code.google.com/p/lilypond/issues/detail?id=1704 (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 1272 in lilypond: remove old /web/
Comment #1 on issue 1272 by percival.music.ca: remove old /web/ http://code.google.com/p/lilypond/issues/detail?id=1272 Issue 1704 has been merged into this issue. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1704 in lilypond: Website: old version of website still active
Status: Accepted Owner: Labels: Type-Build New issue 1704 by colinpkc...@gmail.com: Website: old version of website still active http://code.google.com/p/lilypond/issues/detail?id=1704 As reported by -Eluze, the URL lilypond.org/web leads to the old version of the website, unmaintained in over a year. A redirect is needed to point to the current one. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Updates: Cc: percival.music.ca Comment #12 on issue 1349 by ianhuli...@gmail.com: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 What I'm doing in T1686 is adding support for a -d compile-scheme option, which will get lily.scm to byte-compile all the files which are currently loaded in the init-scheme-files list. We need to do it this way so we can have all the Scheme definitions available which are defined in the C++ initialization code etc. I can't see a way of picking up a build system variable like SCM_ARE_DEPENDENCIES at run-time. However we do it, it looks like the ordering of this list needs sorting. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue, Jun 21, 2011 at 12:52:01PM +0300, Dmytro O. Redchuk wrote:
> In such cases I add
> \header { tagline = "" }
> to a source file and then:
>
> lilypond --png test.ly
> convert test.png -trim test-trim.png
Excellent!
Could you write a short shell script to do this? i.e. using
lilypond -e ...
to remove the tagline (maybe that's already in LSR),
and then call convert automatically? I'd really like to add this
to the CG so that we have a simple way to generate images.
(at least on non-windows machines)
This would allow us to standardize on 1-page pngs (automatically
trimmed) and multi-page pdfs, and avoid -dpreview entirely.
Cheers,
- Graham
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Comment #11 on issue 1349 by percival.music.ca: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 would it be possible to just change the order of files in the makefile? Or maybe have a SCM_ARE_DEPENDENCIES= variable (which are compiled before attempting the other scm files), or something? I'm not certain that including markups in lily-library.scm simply to work around a build system issue is a good solution. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals
Comment #6 on issue 1701 by k-ohara5...@oco.net: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 I believe the [wikipedia] source quoted in that message is wrong. Well, that is too strong a statement. It says that "some composers put a natural" in front of ges following gis. Probably some composers do, but I have never seen it. Has anyone seen the extra natural without a preceding double-accidental consistently that it might have been standard? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1349 in lilypond: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used.
Updates: Cc: jan.nieuwenhuizen Comment #10 on issue 1349 by ianhuli...@gmail.com: Guile 2.0 compat: Scheme macros must be defined/autocompiled before they are used. http://code.google.com/p/lilypond/issues/detail?id=1349 I've started work on Issue 1686 to allow us to compile our scm/*.scm files to scm/out/*.go and have come across another "feature". It looks like we have .scm files in the list loaded by lily.scm that have dependencies on other .scm files earlier in the list (e.g. markup.scm defining markup?). I think we need to do some janitor work so that definitions used like this are defined in lily-library.scm (which is the first file loaded in the list). Cheers, Ian ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals
Comment #5 on issue 1701 by k-ohara5...@oco.net: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 I believe the source quoted in that message is wrong. Look at the next message in the thread. All cited quotes of typeset music, plus what I found in my own search, cancel double-flats before a single-flat, but not a sharp going to a flat. All cited references to books on typesetting indicate double-flat to flat is canceled but are silent regarding a sharped note followed by a flattened note of the same name. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals
Comment #4 on issue 1701 by x.sche...@gmail.com: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 When coming from g flat to g sharp, there should still be a natural before the sharp according to this message, isn't it? http://lists.gnu.org/archive/html/lilypond-user/2011-06/msg00251.html ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals
Comment #2 on issue 1701 by k-ohara5...@oco.net: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 Output after the patch is below. The regression tests show only the desired changes. One can test this without recompiling, by changing two lines in music-functions.scm as indicated above. Attachments: after.png 4.9 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1640 in lilypond: Consecutive glissandos not typeset
Updates: Status: Verified Comment #3 on issue 1640 by philehol...@googlemail.com: Consecutive glissandos not typeset http://code.google.com/p/lilypond/issues/detail?id=1640 (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 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed
Comment #4 on issue 1639 by philehol...@googlemail.com: Glissando between chords at end of measure prevents break and is sometimes not printed http://code.google.com/p/lilypond/issues/detail?id=1639 Current version produces two lines. Image attached is smaller version of original bug report. Attachments: glissando-break-line.png 5.6 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1630 in lilypond: Completion heads engraver produces duplicate ties
Updates: Status: Verified Comment #19 on issue 1630 by philehol...@googlemail.com: Completion heads engraver produces duplicate ties http://code.google.com/p/lilypond/issues/detail?id=1630 (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 1043 in lilypond: Cross-staff beams confuse skyline calculations
Updates: Status: Verified Comment #14 on issue 1043 by philehol...@googlemail.com: Cross-staff beams confuse skyline calculations http://code.google.com/p/lilypond/issues/detail?id=1043 (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 1639 in lilypond: Glissando between chords at end of measure prevents break and is sometimes not printed
Updates: Status: Verified Comment #5 on issue 1639 by philehol...@googlemail.com: Glissando between chords at end of measure prevents break and is sometimes not printed http://code.google.com/p/lilypond/issues/detail?id=1639 (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 1618 in lilypond: unpredictable placement of rests
Updates: Status: Verified Comment #8 on issue 1618 by philehol...@googlemail.com: unpredictable placement of rests http://code.google.com/p/lilypond/issues/detail?id=1618 (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 1617 in lilypond: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all
Updates: Status: Verified Comment #2 on issue 1617 by philehol...@googlemail.com: chordGlissando is a hack that should be replaced with a Glissando property such as 'connect-all http://code.google.com/p/lilypond/issues/detail?id=1617 (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 1547 in lilypond: Too many colliding rests
Updates: Status: Verified Comment #6 on issue 1547 by philehol...@googlemail.com: Too many colliding rests http://code.google.com/p/lilypond/issues/detail?id=1547 (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 1614 in lilypond: DynamicTextSpanner documentation is wrong
Updates: Status: Verified Comment #5 on issue 1614 by philehol...@googlemail.com: DynamicTextSpanner documentation is wrong http://code.google.com/p/lilypond/issues/detail?id=1614 Fixed in development docs, but not in 2.14: http://lilypond.org/doc/v2.14/Documentation/snippets/expressive-marks#changing-text-and-spanner-styles-for-text-dynamics ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1502 in lilypond: Document information in PDF headers requires escapes for accented characters
Updates: Summary: Document information in PDF headers requires escapes for accented characters Comment #7 on issue 1502 by philehol...@googlemail.com: Document information in PDF headers requires escapes for accented characters http://code.google.com/p/lilypond/issues/detail?id=1502 If I run this in Windows, I get Non Lo Far Pi Johann Baptist Strau And the errors below. How should this fix work? (lilypond-windows.exe:5596): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Bold.otf continuing, cross fingers (lilypond-windows.exe:5596): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() programming error: Glyph has no name, but font supports glyph naming. Skipping glyph U+, file C:/Program Files (x86)/LilyPondV2.15.2/usr/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf continuing, cross fingers Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `1502.ps'... warning: Conversion of string `Johann Baptist Strauß' to UTF-16be failed: Partial character sequence at end of input warning: Conversion of string `Non Lo Farò Più' to UTF-16be failed: Invalid byte sequence in conversion input warning: Conversion of string `Johann Baptist Strauß' to UTF-16be failed: Partial character sequence at end of input Converting to `./1502.pdf'... `(gs -q -dNOSAFER -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite -sOutputFile=./1502.pdf -c.setpdfwrite -f1502.ps)' failed (1) error: failed files: "D:\\Music\\LilyPondDev\\BugSquad\\1502.ly" ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: bug report on 2.15.2 Mac OS X Intel version
On 21 June 2011 11:25, Henk Verhaar wrote:
> So what I did is, I copied an existing .ly file in the Finder and renamed it
> to its intended new name, ran the syntax updater, updated some fluff (some
> %obsolete marks introduced by the syntax updater), renamed the variables
> (name, composer, arranger, etc., cut out the previous music definition in the
> default \part {} (I use a \part {} construct standard), introduced a
> \transpose {} construct in my \score {} block, and entered the new music. Ran
> the 'Run' command a number of times until the part was ready and then printed
> it (I still have the finalized PDF file...), then closed Lilypond. When
> reopening the .ly file, the old content (albeit with the syntax updater fluff
> in there) was still there, and no sign of my edits. I may have done something
> wrong myself - I didn't document any of this, since this is my normal MO, but
> as said, it didn't quite result in what I expected...
Using LilyPond 2.15.2 on Mac OS X 10.6.7, its convert-ly may be broken (tried
from Terminal): I do not get any output, nor does any changes take place when
using the -e option. I tried on a file where only the version number should be
changed.
As for the GUI, it typesets the last saved version. So if one is making changes
and not saving those, the typeset will be of the last saved version. When
quitting, though, it asks if one wants to save the changes.
Hans
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 682 in lilypond: annotate-spacing should produce horizontal info as well
Comment #3 on issue 682 by percival.music.ca: annotate-spacing should produce horizontal info as well http://code.google.com/p/lilypond/issues/detail?id=682 Neil, are you still working on this annotate-spacing? (given the changes in spacing, I'm not certain it's still a valid request) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 687 in lilypond: Enhancement: inequal MIDI quantization of equal durations (swing, rubato)
Updates: Status: Accepted Comment #28 on issue 687 by percival.music.ca: Enhancement: inequal MIDI quantization of equal durations (swing, rubato) http://code.google.com/p/lilypond/issues/detail?id=687 I do not believe that there is any current development on this. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 11:15 lilyp...@googlecode.com wrote:
>
> Comment #9 on issue 163 by brownian.box: huge (ugly) slur (both
> phrasing and normal)
> http://code.google.com/p/lilypond/issues/detail?id=163
I have removed this comment (see the next one, comment #10);
sorry for the noise.
> Another real-life example (by David Kastrup,
> http://lists.gnu.org/archive/html/bug-lilypond/2011-06/msg00325.html)
> :
>
> <<
> \chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
> d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
> c1 f c f c f2 d:m a1:7 d:m
> a:7 d:m c f a:7 d:m a:7 d:m }
[...]
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Comment #10 on issue 163 by brownian.box: huge (ugly) slur (both phrasing
and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Another example (reported by David Kastrup,
http://lists.gnu.org/archive/html/bug-lilypond/2011-06/msg00325.html) -- I
have simpified it to this code:
\version "2.15.2"
{
\time4/4 \key d\minor
\relative c' {
\slurUp
e1( f \break g a)
}
}
\paper {
indent = 0
line-width = 3\cm
system-count = 2
}
This case, I guess, is related to issue 379 (reported here as a case
showing somewhat ugly slur).
Attachments:
test.png 1.7 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 10:33 David Kastrup wrote:
>
> Here is another real-life example (I have not been able to boil this
> down to something smaller, like by omitting the chords or trying to
> capture just the bars before and after the break). In this case it
> would appear the insane slur slope after the line break comes from
> trying to avoid the key signature.
I have cut this example as much as could
and added as comment #10.
Thank you.
This case is a variant of issue 379;
however I've added it to "ugly slurs" collection, too.
> <<
> \chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
> d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
> c1 f c f c f2 d:m a1:7 d:m
> a:7 d:m c f a:7 d:m a:7 d:m }
> \new Staff {
>\time4/4 \key d\minor
>\relative c' <<
> { a'2( bes a bes
>a2 g f e)
>f( g a bes
>a g f4 e d2)
>e1( f g a) g( f e f)
>e( f g a~ a~ a~ a~ a~)
> } \\
> {
>d,1~( d~ d~ d) d~( d~ d~ d)
>c~( c~ c~ c) c~( c2 d~ d cis d1)
>cis( d e f) e( d cis d)
> } >>
>}
> >>
>
> Here is the result: uh, no it isn't. What is the preferred method for
> generating a two-system preview? -dpreview just makes the first system.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1508 in lilypond: Key signature wrong with cued music
Updates: Status: Fixed Labels: -Patch-review fixed_2_15_3 Comment #4 on issue 1508 by reinhold...@gmail.com: Key signature wrong with cued music http://code.google.com/p/lilypond/issues/detail?id=1508 Pushed as 9617b03907f82f3f5d530319f6d6ae6fe5d61e97 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Comment #9 on issue 163 by brownian.box: huge (ugly) slur (both phrasing
and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Another real-life example (by David Kastrup,
http://lists.gnu.org/archive/html/bug-lilypond/2011-06/msg00325.html) :
<<
\chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
c1 f c f c f2 d:m a1:7 d:m
a:7 d:m c f a:7 d:m a:7 d:m }
\new Staff {
\time4/4 \key d\minor
\relative c' <<
{ a'2( bes a bes
a2 g f e)
f( g a bes
a g f4 e d2)
e1( f g a) g( f e f)
e( f g a~ a~ a~ a~ a~)
} \\
{
d,1~( d~ d~ d) d~( d~ d~ d)
c~( c~ c~ c) c~( c2 d~ d cis d1)
cis( d e f) e( d cis d)
} >>
}
This case may be related to issue 379.
Attachments:
test.png 11.3 KB
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
FW: bug report on 2.15.2 Mac OS X Intel version
From: Henk Verhaar [hjmverh...@googlemail.com] on behalf of Henk Verhaar [h...@stichtsend.xs4all.nl] Sent: 21 June 2011 11:51 To: James Lowe Subject: Re: bug report on 2.15.2 Mac OS X Intel version > Can I just confirm that you were using the built in editor that comes with > the mac version (as opposed to your own editor and the cli)? > As I said, it MAY have been operator error, but given my background, I didn't think this likely. I will retry with 2.15.2, just to make sure I can, or cannot, reproduce this behaviour. === ><(º> === | Dr. Henk J.M. Verhaar | e-mail: h...@stichtsend.xs4all.nl | | Ecotoxicoloog en vliegbinder | tel:035 656 2128 | | Bonte Kraailaan 22| mobiel: 06 38 279016 | | NL-1343 AJ Almere | web:www.xs4all.nl/~flyrod | === <º)>< === ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: bug report on 2.15.2 Mac OS X Intel version
Henk
From: Henk Verhaar [hjmverh...@googlemail.com] on behalf of Henk Verhaar
[h...@stichtsend.xs4all.nl]
Sent: 21 June 2011 11:25
To: James Lowe
Subject: Re: bug report on 2.15.2 Mac OS X Intel version
Yeah, done that - in fact it appears that the file was saved with the correct
name, and the correct modification time, but without retaining any of the
changes (I used a previous .ly file to adapt - this is what I normally do when
creating .ly files, so that I do not have to manually enter a number of
standard 'entries'. I could alternatively use a template, but in that case I'd
have to update the template explicitly for each Lilypond update, or change in
my preferred standard approach; in this way, I always have my most recent
adaptations in my 'running' template...).
So what I did is, I copied an existing .ly file in the Finder and renamed it to
its intended new name, ran the syntax updater, updated some fluff (some
%obsolete marks introduced by the syntax updater), renamed the variables (name,
composer, arranger, etc., cut out the previous music definition in the default
\part {} (I use a \part {} construct standard), introduced a \transpose {}
construct in my \score {} block, and entered the new music. Ran the 'Run'
command a number of times until the part was ready and then printed it (I still
have the finalized PDF file...), then closed Lilypond. When reopening the .ly
file, the old content (albeit with the syntax updater fluff in there) was still
there, and no sign of my edits. I may have done something wrong myself - I
didn't document any of this, since this is my normal MO, but as said, it didn't
quite result in what I expected...
On 21 jun 2011, at 12:13, James Lowe wrote:
> Henk,
>
>
> From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
> [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Henk
> Verhaar [h...@stichtsend.xs4all.nl]
> Sent: 21 June 2011 10:40
> To: bug-lilypond@gnu.org
> Subject: bug report on 2.15.2 Mac OS X Intel version
>
> Not a notation bug, but an I/O issue (possibly).
> This morning I installed 2.15.2 and successfully created a
> horn part for an adaptation of Fanfare for the Common Man
> (I was given F horn parts and needed them in
> E-flat, so I used the auto-transpose feature of Lilypond to
> create an Eb part. All worked fine, and I must
> have saved the source file a number of times during this
> process, since I know I created intermediate PDFs
> to check progress, and I have a PDF of the final score page
> that I will use. However, It appears that
> Lilypond has somehow removed my source file, or hid it,
> or saved it somewhere else, since I can no longer
> find the correct source file.
>
> I'll be reverting to 2.14 in the meantime...
>
> Cheers
>
> Henk
>
> --
>
> MacOSX has a basic search feature built into the finder, if you simply click
> on a folder or the HD to open a window in the finder there are some search
> filters in the left hand window 'SEARCH FOR'... Today, Yesterday, Past week.
>
> Can you use one of these to see if it has saved it in another place?
>
> I've been using 2.15.2 on MacosX and not had any problems like this.
>
> James
---
Don't forget to cc the list so others can see (and help hopefully).
I've just done a simple test of copying/saving as an old file I did in 2.13 and
making some trivial edits (delete some \header and \paper) etc and then keep
compiling (edit, cmd-s, cmd-r, edit, cmd-s, cmd-r etc) I didn't lose the file.
So unless you can give me something that you might think is key then I'm, not
sure what else to do to test to help troubleshoot.
:/
Can I just confirm that you were using the built in editor that comes with the
mac version (as opposed to your own editor and the cli)?
James
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
FW: bug report on 2.15.2 Mac OS X Intel version
From: Henk Verhaar [hjmverh...@googlemail.com] on behalf of Henk Verhaar
[h...@stichtsend.xs4all.nl]
Sent: 21 June 2011 11:25
To: James Lowe
Subject: Re: bug report on 2.15.2 Mac OS X Intel version
Yeah, done that - in fact it appears that the file was saved with the correct
name, and the correct modification time, but without retaining any of the
changes (I used a previous .ly file to adapt - this is what I normally do when
creating .ly files, so that I do not have to manually enter a number of
standard 'entries'. I could alternatively use a template, but in that case I'd
have to update the template explicitly for each Lilypond update, or change in
my preferred standard approach; in this way, I always have my most recent
adaptations in my 'running' template...).
So what I did is, I copied an existing .ly file in the Finder and renamed it to
its intended new name, ran the syntax updater, updated some fluff (some
%obsolete marks introduced by the syntax updater), renamed the variables (name,
composer, arranger, etc., cut out the previous music definition in the default
\part {} (I use a \part {} construct standard), introduced a \transpose {}
construct in my \score {} block, and entered the new music. Ran the 'Run'
command a number of times until the part was ready and then printed it (I still
have the finalized PDF file...), then closed Lilypond. When reopening the .ly
file, the old content (albeit with the syntax updater fluff in there) was still
there, and no sign of my edits. I may have done something wrong myself - I
didn't document any of this, since this is my normal MO, but as said, it didn't
quite result in what I expected...
On 21 jun 2011, at 12:13, James Lowe wrote:
> Henk,
>
>
> From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
> [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Henk
> Verhaar [h...@stichtsend.xs4all.nl]
> Sent: 21 June 2011 10:40
> To: bug-lilypond@gnu.org
> Subject: bug report on 2.15.2 Mac OS X Intel version
>
> Not a notation bug, but an I/O issue (possibly).
> This morning I installed 2.15.2 and successfully created a
> horn part for an adaptation of Fanfare for the Common Man
> (I was given F horn parts and needed them in
> E-flat, so I used the auto-transpose feature of Lilypond to
> create an Eb part. All worked fine, and I must
> have saved the source file a number of times during this
> process, since I know I created intermediate PDFs
> to check progress, and I have a PDF of the final score page
> that I will use. However, It appears that
> Lilypond has somehow removed my source file, or hid it,
> or saved it somewhere else, since I can no longer
> find the correct source file.
>
> I'll be reverting to 2.14 in the meantime...
>
> Cheers
>
> Henk
>
> --
>
> MacOSX has a basic search feature built into the finder, if you simply click
> on a folder or the HD to open a window in the finder there are some search
> filters in the left hand window 'SEARCH FOR'... Today, Yesterday, Past week.
>
> Can you use one of these to see if it has saved it in another place?
>
> I've been using 2.15.2 on MacosX and not had any problems like this.
>
> James
=== ><(º> ===
| Dr. Henk J.M. Verhaar | e-mail: h...@stichtsend.xs4all.nl |
| Ecotoxicoloog en vliegbinder | tel:035 656 2128 |
| Bonte Kraailaan 22| mobiel: 06 38 279016 |
| NL-1343 AJ Almere | web:www.xs4all.nl/~flyrod |
=== <º)>< ===
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
RE: bug report on 2.15.2 Mac OS X Intel version
Henk, From: bug-lilypond-bounces+james.lowe=datacore@gnu.org [bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Henk Verhaar [h...@stichtsend.xs4all.nl] Sent: 21 June 2011 10:40 To: bug-lilypond@gnu.org Subject: bug report on 2.15.2 Mac OS X Intel version Not a notation bug, but an I/O issue (possibly). This morning I installed 2.15.2 and successfully created a horn part for an adaptation of Fanfare for the Common Man (I was given F horn parts and needed them in E-flat, so I used the auto-transpose feature of Lilypond to create an Eb part. All worked fine, and I must have saved the source file a number of times during this process, since I know I created intermediate PDFs to check progress, and I have a PDF of the final score page that I will use. However, It appears that Lilypond has somehow removed my source file, or hid it, or saved it somewhere else, since I can no longer find the correct source file. I'll be reverting to 2.14 in the meantime... Cheers Henk -- MacOSX has a basic search feature built into the finder, if you simply click on a folder or the HD to open a window in the finder there are some search filters in the left hand window 'SEARCH FOR'... Today, Yesterday, Past week. Can you use one of these to see if it has saved it in another place? I've been using 2.15.2 on MacosX and not had any problems like this. James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals
Comment #1 on issue 1701 by x.sche...@gmail.com: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 Could we see the result after applying your PATCH? Are we sure this "trivial" PATCH won't make bad side effects? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
bug report on 2.15.2 Mac OS X Intel version
Not a notation bug, but an I/O issue (possibly). This morning I installed 2.15.2 and successfully created a horn part for an adaptation of Fanfare for the Common Man (I was given F horn parts and needed them in E-flat, so I used the auto-transpose feature of Lilypond to create an Eb part. All worked fine, and I must have saved the source file a number of times during this process, since I know I created intermediate PDFs to check progress, and I have a PDF of the final score page that I will use. However, It appears that Lilypond has somehow removed my source file, or hid it, or saved it somewhere else, since I can no longer find the correct source file. I'll be reverting to 2.14 in the meantime... Cheers Henk ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1200 in lilypond: GUB does something with fontforge all the time
Updates: Status: Verified Comment #6 on issue 1200 by percival.music.ca: GUB does something with fontforge all the time http://code.google.com/p/lilypond/issues/detail?id=1200 (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 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue 21 Jun 2011, 11:10 David Kastrup wrote:
> Graham Percival writes:
>
> > On Tue, Jun 21, 2011 at 10:33:31AM +0200, David Kastrup wrote:
> >>
> >> Here is the result: uh, no it isn't. What is the preferred method for
> >> generating a two-system preview?
> >
> > Using a full --png, unfortunately:
> > http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker
> > But that's not something that you need to do; the bug squad should
> > take care of this step.
>
> I've been told in private communication to use Windows Paint. That's
> not a useful option for me and takes some time (one could similarly do
> this in the Gimp if one likes interactive workflows). What I did in the
> end was
>
> pngtopnm kelbl.png |pnmcut -bottom -40|pnmcrop |pnmtopng >kelbl2.png
>
> (first cutting off the foot line, then cropping down), resulting in
Wow.
In such cases I add
\header { tagline = "" }
to a source file and then:
lilypond --png test.ly
convert test.png -trim test-trim.png
It is ok to me usually.
--
Dmytro O. Redchuk
Bug Squad
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1200 in lilypond: GUB does something with fontforge all the time
Updates: Status: Fixed Comment #5 on issue 1200 by percival.music.ca: GUB does something with fontforge all the time http://code.google.com/p/lilypond/issues/detail?id=1200 resolved in the fontforge bump to the 20110222 tarball. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1050 in lilypond: website translations should use gettext
Updates: Status: Accepted Comment #4 on issue 1050 by percival.music.ca: website translations should use gettext http://code.google.com/p/lilypond/issues/detail?id=1050 (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 1015 in lilypond: doc line width
Updates: Status: Accepted Owner: --- Comment #11 on issue 1015 by percival.music.ca: doc line width http://code.google.com/p/lilypond/issues/detail?id=1015 (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 1333 in lilypond: Enhancement: beamed acciaccaturas should be printed with a slash
Updates: Status: Accepted Comment #6 on issue 1333 by percival.music.ca: Enhancement: beamed acciaccaturas should be printed with a slash http://code.google.com/p/lilypond/issues/detail?id=1333 (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 1287 in lilypond: Notation 2.9 Ancient notation does not follow doc policy
Updates: Status: Accepted Comment #5 on issue 1287 by percival.music.ca: Notation 2.9 Ancient notation does not follow doc policy http://code.google.com/p/lilypond/issues/detail?id=1287 I don't think that James is actively working on this. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1508 in lilypond: Key signature wrong with cued music
Updates: Labels: Patch-review Comment #3 on issue 1508 by percival.music.ca: Key signature wrong with cued music http://code.google.com/p/lilypond/issues/detail?id=1508 (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 1669 in lilypond: Empty contexts sometimes take up too much space
Updates: Status: Accepted Comment #7 on issue 1669 by percival.music.ca: Empty contexts sometimes take up too much space http://code.google.com/p/lilypond/issues/detail?id=1669 (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 163 in lilypond: huge (ugly) slur (both phrasing and normal)
"Graham Percival" wrote in message news:20110621091600.GA2177@gperciva-desktop... On Tue, Jun 21, 2011 at 11:10:42AM +0200, David Kastrup wrote: Graham Percival writes: > But that's not something that you need to do; the bug squad should > take care of this step. I've been told in private communication to use Windows Paint. That's not a useful option for me and takes some time (one could similarly do this in the Gimp if one likes interactive workflows). Indeed. In addition, the Bug Squad is not supposed to use images sent by users (or developers); they are instructed to generate images themselves with either -dpreview, --png, or --pdf as per http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker Manually cropping images is far too much work. Cheers, - Graham Sorry - it wasn't meant to be private - must have failed to hit replay all. I didn't tell David to use Windows Paint - I said that this is what I do. It's a 10 second operation at most - right click the image generated with -fpng, edit, select the important part, crop, exit. -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue, Jun 21, 2011 at 11:10:42AM +0200, David Kastrup wrote: > Graham Percival writes: > > > But that's not something that you need to do; the bug squad should > > take care of this step. > > I've been told in private communication to use Windows Paint. That's > not a useful option for me and takes some time (one could similarly do > this in the Gimp if one likes interactive workflows). Indeed. In addition, the Bug Squad is not supposed to use images sent by users (or developers); they are instructed to generate images themselves with either -dpreview, --png, or --pdf as per http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker Manually cropping images is far too much work. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Graham Percival writes: > On Tue, Jun 21, 2011 at 10:33:31AM +0200, David Kastrup wrote: >> >> Here is the result: uh, no it isn't. What is the preferred method for >> generating a two-system preview? > > Using a full --png, unfortunately: > http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker > But that's not something that you need to do; the bug squad should > take care of this step. I've been told in private communication to use Windows Paint. That's not a useful option for me and takes some time (one could similarly do this in the Gimp if one likes interactive workflows). What I did in the end was pngtopnm kelbl.png |pnmcut -bottom -40|pnmcrop |pnmtopng >kelbl2.png (first cutting off the foot line, then cropping down), resulting in <> -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1562 in lilypond: using \sans on Windows gives 'gs' error (2.13.53) fails to compile
Comment #36 on issue 1562 by philehol...@googlemail.com: using \sans on Windows gives 'gs' error (2.13.53) fails to compile http://code.google.com/p/lilypond/issues/detail?id=1562 This needs someone who has Windows 7 with SP1 installed to verify. James? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
On Tue, Jun 21, 2011 at 10:33:31AM +0200, David Kastrup wrote: > > Here is the result: uh, no it isn't. What is the preferred method for > generating a two-system preview? Using a full --png, unfortunately: http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-to-the-tracker But that's not something that you need to do; the bug squad should take care of this step. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1682 in lilypond: Website version links need updating
Comment #6 on issue 1682 by percival.music.ca: Website version links need updating http://code.google.com/p/lilypond/issues/detail?id=1682 what are those inconsistencies? As far as I can see, the problem described in the first report are solved, so I suggest that this issue should be closed. If you want to add new information, go ahead; I'd be tempted to add a separate issue. But in either case, I want to see information in the bug tracker about what the "additional version link inconsistencies" are. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)
Here is another real-life example (I have not been able to boil this
down to something smaller, like by omitting the chords or trying to
capture just the bars before and after the break). In this case it
would appear the insane slur slope after the line break comes from
trying to avoid the key signature.
<<
\chords { d2:m a:7 d:m a:7 d:m g:m d:m a:7
d2:m a:7 d:m a:7 d:m g:m d4:m a:7 d2:m
c1 f c f c f2 d:m a1:7 d:m
a:7 d:m c f a:7 d:m a:7 d:m }
\new Staff {
\time4/4 \key d\minor
\relative c' <<
{ a'2( bes a bes
a2 g f e)
f( g a bes
a g f4 e d2)
e1( f g a) g( f e f)
e( f g a~ a~ a~ a~ a~)
} \\
{
d,1~( d~ d~ d) d~( d~ d~ d)
c~( c~ c~ c) c~( c2 d~ d cis d1)
cis( d e f) e( d cis d)
} >>
}
>>
Here is the result: uh, no it isn't. What is the preferred method for
generating a two-system preview? -dpreview just makes the first system.
--
David Kastrup
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
