Updates:
Status: Verified
Comment #31 on issue 163 by brownian.box: huge (ugly) slur (both phrasing
and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Labels: -Patch-needs_work fixed_2_15_9
Comment #30 on issue 163 by n.putt...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
_
Updates:
Status: Fixed
Comment #29 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Pushed as 94ea10f3f341fff503599a9eb947c81f1803290f.
Cheers,
MS
___
bug
Updates:
Labels: -Patch-review Patch-needs_work
Comment #28 on issue 163 by n.putt...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Needs rebasing.
___
bug-lilypond mailing li
Updates:
Labels: -Patch-new Patch-review
Comment #27 on issue 163 by k-ohara5...@oco.net: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
The current patch has only the regtest change shown in comment 23, which is
good and intended,
Updates:
Labels: -Patch-review
Comment #26 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
___
bug-lilypond mai
Updates:
Labels: Patch-new
Comment #25 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
http://codereview.appspot.com/4810072/
___
bug-lilypond mailing lis
Updates:
Labels: -Patch-needs_work Patch-review
Comment #23 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
http://codereview.appspot.com/4810072/
Passes Make, one reg test difference - see attached
Comment #22 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
The difference in the height of generated curves is relatively drastic when
you remove the accidental.
I'm not sure if this is a good or bad thing
Comment #21 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
I changed my patch (no need to run regtests) that diminishes the changes in
the regtests and still solves all the problem cases
(http://coderevi
Comment #20 on issue 163 by hanw...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Mike,
maybe you can dig into the different examples a bit more? I think there are
multiple independent issues.
\paper {
ragged-right = ##f
Updates:
Labels: -Patch-review Patch-needs_work
Comment #19 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
___
Comment #18 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Thanks, James! Your regtest run was a big help, as all of the results you
found did not show up when I ran them (before my last update, which was
Updates:
Labels: -Patch-new Patch-review
Comment #17 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Passes Make - new reg test differences attached
Attachments:
Screenshot1.png 28.3 KB
Updates:
Labels: -Patch-needs_work Patch-new
Comment #16 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(No comment was entered for this change.)
___
bu
Updates:
Labels: -Patch-review Patch-needs_work
Comment #15 on issue 163 by colinpkc...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Mike feels this needs more work.
___
bug-
Comment #14 on issue 163 by k-ohara5...@oco.net: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Workarounds, that make the height-limit (usually 2) *larger* and 'ratio
(the preference tall heights relative to the limit) smaller :
\relati
Comment #13 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Not a prob, James!
Cheers,
MS
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.or
Updates:
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #12 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
make tests pass and reg tests look pretty good (attached differenc
Updates:
Labels: Patch-new
Comment #11 on issue 163 by pkx1...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
From Mike:
--snip--
Message:
Hey all,
This fixes issue 163. The only downside is that it adds another entry
t
On Mon 04 Jul 2011, 17:15 I wrote:
> On Mon 04 Jul 2011, 16:17 I wrote:
> > For windows I would try to start with .cmd like this:
> This seems to work (tested under VirtualBox, WinXP):
Sorry for the noise, final ("initial") version is so far:
rem --8<--
@echo off
r
On Mon 04 Jul 2011, 16:17 I wrote:
> For windows I would try to start with .cmd like this:
This seems to work (tested under VirtualBox, WinXP):
rem 8<--
rem trimtagline.bat
rem
rem get only file name, no extension:
set LY=%~n1
echo \header { tagline = ##f } | lilypond -di
On Mon 04 Jul 2011, 15:19 Neil Puttock wrote:
> On 4 July 2011 15:16, Neil Puttock wrote:
>
> > Ah, I didn't notice that (though it only applies to single-system
> > snippets where you'd usually use -dpreview).
>
> Silly me. Of course, with ragged-right = ##t the same applies to
> multi-system
On 4 July 2011 15:16, Neil Puttock wrote:
> Ah, I didn't notice that (though it only applies to single-system
> snippets where you'd usually use -dpreview).
Silly me. Of course, with ragged-right = ##t the same applies to
multi-system snippets. :)
Cheers,
Neil
On 4 July 2011 14:57, Dmytro O. Redchuk wrote:
> But this gives "wide" image, with a width of paper, I guess. (And some extra
> space at top... and bottom).
Ah, I didn't notice that (though it only applies to single-system
snippets where you'd usually use -dpreview).
Cheers,
Neil
_
On Mon 04 Jul 2011, 14:48 Neil Puttock wrote:
> On 4 July 2011 14:17, Dmytro O. Redchuk wrote:
>
> > I've not tested! I have no any windows (with lilypond and ImageMagick)
> > about.
>
> You don't need ImageMagick. The eps backend will produce a trimmed
> png (assuming the tagline's been remov
On 4 July 2011 14:17, Dmytro O. Redchuk wrote:
> I've not tested! I have no any windows (with lilypond and ImageMagick) about.
You don't need ImageMagick. The eps backend will produce a trimmed
png (assuming the tagline's been removed):
echo "\\header { tagline = ##f }" | lilypond -dinclude-se
On Mon 04 Jul 2011, 07:06 Colin Campbell wrote:
> Sorry for the delay, Dmytro! I was trying to find a bit of time to
> test whether it, or a slightly different version, would work under
> Windows. The convert command comes from ImageMagik which seems to
> have a Windows binary available.
For win
On 11-07-04 04:39 AM, Dmytro O. Redchuk wrote:
On Thu 23 Jun 2011, 14:19 Graham Percival wrote:
Colin: add this to the CG (since Dmytro isn't trained in making
patches).
Hi!
Please, Colin, would you add this to the CG?
I guess, to "8.5 Adding issues to the tracker" :)
http://lilypond.org/doc/
On Thu 23 Jun 2011, 14:19 Graham Percival wrote:
> Colin: add this to the CG (since Dmytro isn't trained in making
> patches).
Hi!
Please, Colin, would you add this to the CG?
I guess, to "8.5 Adding issues to the tracker" :)
http://lilypond.org/doc/v2.15/Documentation/contributor/adding-issues-t
On Thu 23 Jun 2011, 06:48 Colin Campbell wrote:
> A problem arises when, as I suspect, the default behaviour is
> tagline = ##t, even when not explicitly stated in the \header block.
> IOW, the absence of "tagline = " doesn't mean absence of a tagline.
> The presence of the tagline means convert mu
On 11-06-23 05:46 AM, Graham Percival wrote:
On Wed, Jun 22, 2011 at 06:52:43PM -0600, Colin Campbell wrote:
On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
I would start with this:
Looks great; Colin, could you add that to the CG in the Issues
chapter?
That's Dmytro's script, Graham! My ba
On Thu, Jun 23, 2011 at 06:48:47AM -0600, Colin Campbell wrote:
> On 11-06-23 05:46 AM, Graham Percival wrote:
> >On Wed, Jun 22, 2011 at 06:52:43PM -0600, Colin Campbell wrote:
> >>On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
> >>>I would start with this:
> >Looks great; Colin, could you add tha
On Wed, Jun 22, 2011 at 06:52:43PM -0600, Colin Campbell wrote:
> On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
> >I would start with this:
Looks great; Colin, could you add that to the CG in the Issues
chapter?
> >Do we need more options? For trimming "in place" or something else?
I don't thin
On Wed 22 Jun 2011, 18:52 Colin Campbell wrote:
> overridden if the tag exists in the destination file. Where a .ly
> file already has the tagline set, it cancels the imported one. To
Yes, right, imported tagline overrides default one only .)
This is enough for most (all?) of tests however, isn
On 11-06-22 06:52 PM, Colin Campbell wrote:
After a bit of testing, it seems that settings in \included files,
however the include is done (very smooth trick, that, David!), are
overridden if the tag exists in the destination file. Where a .ly
file already has the tagline set, it cancels t
On 11-06-22 05:47 AM, Dmytro O. Redchuk wrote:
On Wed 22 Jun 2011, 11:53 Graham Percival wrote:
ok, how about this? Your script should:
echo "\header { tagline = ##f } "> /tmp/lilypond-no-header.ly
. o O ( \\header, of course )
lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --
On Wed 22 Jun 2011, 11:53 Graham Percival wrote:
> ok, how about this? Your script should:
> echo "\header { tagline = ##f } " > /tmp/lilypond-no-header.ly
. o O ( \\header, of course )
> lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --png bug.ly
> convert bug.png -trim bug-upload.
On Wed, Jun 22, 2011 at 01:17:25PM +0200, David Kastrup wrote:
> Graham Percival writes:
>
> > ok, how about this? Your script should:
> > echo "\header { tagline = ##f } " > /tmp/lilypond-no-header.ly
> > lilypond -dinclude-settings=/tmp/lilypond-no-header.ly --png bug.ly
>
> You can write
Graham Percival writes:
> On Wed, Jun 22, 2011 at 10:05:51AM +0300, Dmytro O. Redchuk wrote:
>> On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
>> > 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),
>> >
On Wed, Jun 22, 2011 at 10:05:51AM +0300, Dmytro O. Redchuk wrote:
> On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> > 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 automatical
On Tue 21 Jun 2011, 20:53 Graham Percival wrote:
> 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!
>
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
lilyp
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
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 cod
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 a
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:
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, unfortu
"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 co
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
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/contribut
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
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 si
Comment #8 on issue 163 by mts...@gmail.com: huge (ugly) slur (both
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Badness also occurs with tuplets:
\paper { ragged-right = ##f }
\relative c'' { r2 \times 2/3 { r2 bes4 ( } \times 2/3 { a4 aes a } \times
2/3 { a
Updates:
Owner: ---
Labels: -Engraving-nitpick
Comment #7 on issue 163 by pnorcks: huge (ugly) slur (both phrasing and
normal)
http://code.google.com/p/lilypond/issues/detail?id=163
(Reproduced with 2.13.20)
Attachments:
bug.preview.png 5.0 KB
slurshape.png
Issue 163: huge (ugly) slur (both phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163
Comment #6 by v.villenave:
(Reproduced with 2.11.47)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You
56 matches
Mail list logo
