On 2/6/11 8:14 AM, "Mike Solomon" wrote:
> Hey all,
>
> In the attached png, you'll see that the feathered beam resets to 0 feather @
> the line break. Actually, it even regresses a bit: you'll see that it's
> actually fatter at the linebreak than it is a couple beats after, after which
> it
On Feb 7, 2011, at 8:18 AM, Jan Warchoł wrote:
> 2011/2/7 m...@apollinemike.com :
>>
>> On Feb 6, 2011, at 6:19 PM, Jan Warchoł wrote:
>>
>>> 2011/2/6 :
I can't really speak to the font stuff.
>>>
>>> Why not? Every one has his own personal preferences.
>>> And the font stuff is what matt
> What would possibly be more useful to doc volunteers, and more
> productive of developers' time, might be to post a draft, outline, or
> series of bullet points, probably on bug-, so the doc people can take
> the patch process from the start. With devs putting doc patches on
> Reitveldt, at lea
On 2/6/11 7:10 AM, "Janek Warchoł" wrote:
> 2011/2/6 Janek Warchoł :
>
> Now i see that there is a warning about vim, only it's somewhere else
> (CG 3.3.4 "commit messages"), not in "uploading patch for review".
> Sorry for whining.
No problem. You've identified another place where we shoul
On Mon, Feb 07, 2011 at 11:02:16AM -, Trevor Daniels wrote:
>
> I think the spacing controls are now so complex that
> they really do need a 'learning' approach to help
> users understand how to approach page layout.
I'm probably missing something because I don't know what the new
spacing con
Janek Warchoł writes:
> 2011/2/7 Carl Sorensen :
>>
>> On 2/6/11 4:44 PM, "Janek Warchoł" wrote:
>>> As for now, i've already reset my git repository (that is i clicked
>>> "Abort changes - reset to origin" in lily-git) and made the changes
>>> again. So now i call
>>>
>>> git status (everythi
Hi Francisco,
On Mon, Feb 7, 2011 at 4:58 PM, Francisco Vila wrote:
> - Chinese translations for the following items are required into
> Documentation/lilypond-texi2html.init
>
> (big HTML)
> Changes
> Contributor
> (did not exist in 2.12)
> Doc tarball for
> Essay
> Extending
> Internal
This comment of mine from Mark's patch still applies, even after these
changes:
I've looked at the compiled version now. It's nicely
written, but my concern is that this is no longer written
in 'reference' style. To me, parts of it seem more
suited to the LM. The idea of the NR is that people
New patch set uploaded.
http://codereview.appspot.com/4134041/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sun, 2011-02-06 at 10:32 -0500, Mike Solomon wrote:
> To round out my feature/bug tryptych (yes, this is the day that I make my
> score not look crappy...sorry for all the traffic @ once...)
>
>
> \relative c'' { b1 \stopStaff \override Staff . StaffSymbol #'line-count = #1
> \startStaff \te
On Mon, Feb 7, 2011 at 1:03 PM, Mike Solomon wrote:
> http://codereview.appspot.com/4080057 is the real deal.
>
>
> This still adds noteheads from the same voice as the beam.
>
>
> + for (vsize i=0; i < covered_grobs_.size (); i++) + for (vsize j=0; j <
> active_beams_.size (); j++) + { + bool my
On Sun, 2011-02-06 at 23:43 -0500, Mike Solomon wrote:
> Colin - I sent a thing about ties out to the list as well - I bet these are
> part of the same issue.
>
> Cheers,
> MS
It certainly shows the same sort of symptoms, Mike. I was waiting to
see if your message got a response, but I believe
On 2/6/11 4:44 PM, "Janek Warchoł" wrote:
> 2011/2/6 Carl Sorensen :
>>
>>> What shall i do now? I can copy modified files, delete whole
>>> lilypond-git directory, download source again and make changes again,
>>> but is there some better way?
>>> Why is it not working? Is it because i didn'
You need to set the tempo's X-extent to 0.
On Sun, Feb 6, 2011 at 8:32 AM, Mike Solomon wrote:
> To round out my feature/bug tryptych (yes, this is the day that I make my
> score not look crappy...sorry for all the traffic @ once...)
>
>
>
>
> \relative c'' { b1 \stopStaff \override Staff . Staf
My first attempt at this, and I hope it is what Reinhold is looking for.
http://codereview.appspot.com/4129053/diff/1/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4129053/diff/1/Documentation/notation/input.itely#newcode1341
D
Hi Francisco,
On Sun, Feb 6, 2011 at 4:46 AM, Francisco Vila wrote:
>>
>> OK, here is a preview.
>> http://paconet.org/lilypond/out-website/website/index.html
>>
>
> Here http://paconet.org/lilypond/out-website/website/easier-editing.cs.html
> and here http://paconet.org/lilypond/out-website/webs
LGTM, please push.
http://codereview.appspot.com/4133044/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/4132045/diff/1/Documentation/notation/simultaneous.itely
File Documentation/notation/simultaneous.itely (right):
http://codereview.appspot.com/4132045/diff/1/Documentation/notation/simultaneous.itely#newcode842
Documentation/notation/simultaneous.itely:842: if one o
%% Reported on LilyPond French Users mailing list
%%
http://lilypond-french-users.1298960.n2.nabble.com/Arrangement-vertical-encore-une-petite-amelioration-tp5982503p5998593.html
%%
%% StaffGrouper properties does not apply to "second level" StaffGroup ,
%% i.e. when this StaffGroup is itself
Phil Holmes philholmes.net> writes:
> [...]typography-demo.ly [...] used to occupy 3 lines - it's now 4
> lines. Don't believe this counts as a regression.
>
This one doesn't have its images compared in a make check, so I hadn't noticed
that change. My patch prevents the fermata from overla
2011/2/7 Carl Sorensen :
>
> On 2/6/11 4:44 PM, "Janek Warchoł" wrote:
>> As for now, i've already reset my git repository (that is i clicked
>> "Abort changes - reset to origin" in lily-git) and made the changes
>> again. So now i call
>>
>> git status (everything looks fine, 3 files i've chang
On Feb 6, 2011, at 6:19 PM, Jan Warchoł wrote:
> 2011/2/6 :
>> Great work!
>
> Thank you!
>
>> I can't really speak to the font stuff.
>
> Why not? Every one has his own personal preferences.
> And the font stuff is what matters the most for me :)
> Of course some changes are very subtle. It'
2011/2/7 m...@apollinemike.com
>
> On Feb 7, 2011, at 8:18 AM, Jan Warchoł wrote:
>
> > 2011/2/7 m...@apollinemike.com :
> >>
> >> http://codereview.appspot.com/4134041/diff/1/lily/stem.cc#newcode728
> >> lily/stem.cc:728: }
> >> Same - arrays can be used here (see above for how to handle else if)
hi Francisco,
I translated all items in manual.itexi. Please add this in trunk if possible.
I have another question, do I need to translate "words" in @ref{words}
and @rprogram{words}?
benluo
manuals.itexi
Description: Binary data
___
lilypond-devel
Xavier Scheuer gmail.com> writes:
>
> The only difference I see between GrandStaff and the others is that
> GrandStaff does not have "Vertical_align_engraver" .
>
[...]
> Could we add \consists "Vertical_align_engraver" to GrandStaff in
> "ly/engraver-init.ly"?
>
Absolutely, yes.
I a
Hello,
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Trevor
Daniels [t.dani...@treda.co.uk]
Sent: 07 February 2011 11:02
To: percival.music...@gmail.com; pkx1...@gmail.com
Am Montag, 7. Februar 2011, um 16:03:45 schrieb David Kastrup:
> Janek Warchoł writes:
> > 2011/2/7 Carl Sorensen :
> >> If you want to make it part of the previous commit, you can do so with
> >> git commit -a --amend
> >>
> >> But I don't recommend doing that.
> >
> > Aha. Ok.
>
> Rule of thu
On Sat, Feb 5, 2011 at 1:51 PM, Mike Solomon wrote:
>>> True, although I think it's important to account for all beaming cases if
>>> possible.
>>
>> This is a performance optimization, ie. a way to run collision
>> detection without performance impact if the object does not really
>> collide, s
Yikes! Sorry...
http://codereview.appspot.com/4080057 is the real deal.
Cheers,
MS
On Feb 7, 2011, at 9:30 AM, han...@google.com wrote:
> looks like this patch grew some erroneous edits from other commits.
>
> http://codereview.appspot.com/4128059/
__
On Mon, Feb 07, 2011 at 01:41:45PM +, James Lowe wrote:
> Where my skill falls down is if the new section names cannot be
> moved lock stock and barrel over to the LM and I have to end up
> making new nodes. Otherwise I can easily just cut/paste edited
> chunks into the existing LM texi/tely fi
On Sun, 2011-02-06 at 10:14 -0500, Mike Solomon wrote:
> Hey all,
>
> In the attached png, you'll see that the feathered beam resets to 0 feather @
> the line break. Actually, it even regresses a bit: you'll see that it's
> actually fatter at the linebreak than it is a couple beats after, after
On Mon, 2011-02-07 at 14:07 +0100, Reinhold Kainhofer wrote:
> > What would possibly be more useful to doc volunteers, and more
> > productive of developers' time, might be to post a draft, outline, or
> > series of bullet points, probably on bug-, so the doc people can take
> > the patch process f
bin/gub darwin-x86::glib
... dies...
vi target/darwin-x86/log/glib.log
/main/src/gub/target/darwin-x86/root/usr/cross/bin/i686-apple-darwin8-ld:
Undefined symbols:
_res_9_dn_expand
_res_9_init
_res_9_query
_res_9_search
related solutions:
http://bugs.php.net/49332
http://www.openldap.org/faq/data/
See this related snippet:
http://lsr.dsi.unimi.it/LSR/Item?id=301
The only fix I have found is to set the X-extent to 0 and to use
offsets to get the mark back to its original vertical position, if
needed. Collisions, yes, but it's a hack that fixes the issue.
On Sun, Feb 6, 2011 at 9:46 PM, C
LGTM.
http://codereview.appspot.com/4014041/diff/1/lily/key-engraver.cc
File lily/key-engraver.cc (right):
http://codereview.appspot.com/4014041/diff/1/lily/key-engraver.cc#newcode92
lily/key-engraver.cc:92: || (ly_scm2rational (scm_cdr (new_alter_pair))
- old_alter) * old_alter
indent (use tab
On Mon, Feb 7, 2011 at 12:43 PM, Mike Solomon wrote:
> Yikes! Sorry...
>
> http://codereview.appspot.com/4080057 is the real deal.
This still adds noteheads from the same voice as the beam.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
_
LGTM other than the language suggestions Colin made. I mean, the
suggestions are good, so the patch wasn't perfect. I mean... you know
what I mean.
http://codereview.appspot.com/4129053/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://l
Speak now* or forever hold your piece.
(* now = before 6pm GMT on Tuesday, 8 Feb)
Make KeyCancellation independent of extraNatural
http://codereview.appspot.com/4014041/
Reinstate an event for \tempo, instead of relying on context property changes.
http://codereview.appspot.com/2145047/
Chee
http://codereview.appspot.com/2145047/diff/6001/scm/define-music-display-methods.scm
File scm/define-music-display-methods.scm (right):
http://codereview.appspot.com/2145047/diff/6001/scm/define-music-display-methods.scm#newcode927
scm/define-music-display-methods.scm:927: (format #f "\\tempo ~{
Am Sonntag, 6. Februar 2011, um 16:40:28 schrieb Neil Thornock:
> You need to set the tempo's X-extent to 0.
Unfortunately, this might lead to collisions... I don't see any reason why a
\tempo after a \startStaff should not use the new settings. But then, I don't
know the internals leading to th
beambug.ly
Description: Binary data
probably not the most minimal example in the world, but it gets the job done!
Cheers,
MS
On Feb 6, 2011, at 11:35 PM, Colin Campbell wrote:
> On Sun, 2011-02-06 at 10:14 -0500, Mike Solomon wrote:
>> Hey all,
>>
>> In the attached png, you'll see that the
On Sun, Feb 06, 2011 at 07:33:15PM +0100, Francisco Vila wrote:
> 2011/2/6 Jan Warchoł :
> > http://paconet.org/lilypond/out-website/website/features.cs.html
> >
> > ("Spojení not a textu" column is too narrow)
> > (WinXP, Chrome)
>
> I see this, too. Firefox on GNU/Linux. Looking at the code, wh
On 7 February 2011 00:43, Reinhold Kainhofer wrote:
>
> Dear all,
> Here are three patches for some features that I implemented during the 2.13
> cycle so far.
>
> http://codereview.appspot.com/4133044/
> http://codereview.appspot.com/4129053/
> http://codereview.appspot.com/4132045/
>
> As I wrot
Hi Francisco,
On Sun, Feb 6, 2011 at 8:30 AM, Francisco Vila wrote:
>
> Thank you. Check the preview in a few minutes, I'm uploading it now.
>
It seems work. I will translate others few by few.
benluo
___
lilypond-devel mailing list
lilypond-devel@gn
Dear all,
Here are three patches for some features that I implemented during the 2.13
cycle so far.
http://codereview.appspot.com/4133044/
http://codereview.appspot.com/4129053/
http://codereview.appspot.com/4132045/
As I wrote in my other mail to the bug list, I prefer it if the developer
wri
looks like this patch grew some erroneous edits from other commits.
http://codereview.appspot.com/4128059/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sun, 2011-02-06 at 10:21 -0500, Mike Solomon wrote:
> Well, no, I lied, just plain bug. I can't imagine this being a feature.
> But, before I start working on it, does anyone have a clean work-around to
> get the bendAfter spanning the line break correctly?
>
> Cheers,
> MS
>
> \score {
>
On Feb 7, 2011, at 10:00 AM, Han-Wen Nienhuys wrote:
> On Mon, Feb 7, 2011 at 12:43 PM, Mike Solomon wrote:
>> Yikes! Sorry...
>>
>> http://codereview.appspot.com/4080057 is the real deal.
>
> This still adds noteheads from the same voice as the beam.
+ for (vsize i=0; i < covered_grobs_.siz
argh, I just sent the 48-hour notice before checking the regtests.
Minor issue:
input/regression/display-lily-tests.log
no longer prints a warning for "test 90 unequal".
I know that you know \displayMusic better than anybody else, so I'm not
worried about this. :)
http://codereview.appspot.com
2011/2/6 :
> Great work!
Thank you!
> I can't really speak to the font stuff.
Why not? Every one has his own personal preferences.
And the font stuff is what matters the most for me :)
Of course some changes are very subtle. It's best to open pdfs called
"flag testing" side-by-side on a big res
Is it supposed to be repositioned so high on the staff?
Cheers,
MS
On Feb 7, 2011, at 1:20, Keith OHara wrote:
> Mike Solomon ufl.edu> writes:
>
>> While trying to eradicate the bug that's been giving me problems today,
>> I found this:
>> http://lilypond.org/doc/v2.13/Documentation/extendi
wrote Sunday, February 06, 2011 8:41
PM
On 2011/02/06 17:48:56, Trevor Daniels wrote:
This comment of mine from Mark's patch still applies, even after
these
changes:
> I've looked at the compiled version now. It's nicely
> written, but my concern is that this is no longer written
> in
On 2011/02/06 21:13:34, nicolas.sceaux wrote:
http://codereview.appspot.com/2145047/diff/6001/scm/define-music-display-methods.scm
File scm/define-music-display-methods.scm (right):
http://codereview.appspot.com/2145047/diff/6001/scm/define-music-display-methods.scm#newcode927
scm/define-mus
2011/2/6 Carl Sorensen :
>
>> What shall i do now? I can copy modified files, delete whole
>> lilypond-git directory, download source again and make changes again,
>> but is there some better way?
>> Why is it not working? Is it because i didn't do it before making
>> changes in source files?
>
> Y
Mike Solomon ufl.edu> writes:
> While trying to eradicate the bug that's been giving me problems today,
> I found this:
> http://lilypond.org/doc/v2.13/Documentation/extending/difficult-tweaks
>
> I think it's the same issue. Das ist nicht gut :(
>
If you are talking about the example under
While trying to eradicate the bug that's been giving me problems today, I found
this:
http://lilypond.org/doc/v2.13/Documentation/extending/difficult-tweaks
I think it's the same issue. Das ist nicht gut :(
Should I git-bisect, or is someone already working on this?
~Mike
2011/2/6 Ben Luo :
> hi Francisco,
>
> I translated all items in manual.itexi. Please add this in trunk if possible.
>
> I have another question, do I need to translate "words" in @ref{words}
> and @rprogram{words}?
in @ref{node_name}, you can leave it as is in English if the target
node name is
On Mon, 2011-02-07 at 00:43 +0100, Reinhold Kainhofer wrote:
> Dear all,
> Here are three patches for some features that I implemented during the 2.13
> cycle so far.
>
> http://codereview.appspot.com/4133044/
> http://codereview.appspot.com/4129053/
> http://codereview.appspot.com/4132045/
>
>
2011/2/6 Jan Warchoł :
> I see another problem here:
>
> http://paconet.org/lilypond/out-website/website/features.cs.html
>
> ("Spojení not a textu" column is too narrow)
> (WinXP, Chrome)
I see this, too. Firefox on GNU/Linux. Looking at the code, what can be done?
--
Francisco Vila. Badajoz (
On Feb 6, 2011, at 6:19 PM, Jan Warchoł wrote:
> 2011/2/6 :
>> Great work!
>
> Thank you!
>
>> I can't really speak to the font stuff.
>
> Why not? Every one has his own personal preferences.
> And the font stuff is what matters the most for me :)
> Of course some changes are very subtle. It'
2011/2/7 Mike Solomon :
> Is it supposed to be repositioned so high on the staff?
>
> Cheers,
> MS
I see 'extra-offset '(-2 . 5) and the tie is just about 2 staffspaces
to the left and 5 staffspaces above its default position, so it looks
all right to me...
cheers,
Janek
On Feb 7, 2011, at 12:18 PM, Jan Warchoł wrote:
> 2011/2/7 Mike Solomon :
>> Is it supposed to be repositioned so high on the staff?
>>
>> Cheers,
>> MS
>
> I see 'extra-offset '(-2 . 5) and the tie is just about 2 staffspaces
> to the left and 5 staffspaces above its default position, so it loo
On 2/7/11 6:07 AM, "Janek Warchoł" wrote:
> Well, i've uploaded yet another patch now (that uses some arrays
> instead of switches and if..elses).
> I suppose that if only one file changed then i'm not supposed to
> include all files in patch.
No, you will always do a git-cl upload master
git-cl
Hello,
A new patch set has just been uploaded. Sorry for my delay.
Felipe
2011/1/29 Felipe Gonçalves Assis :
> Right,
>
> I will have a look at that.
>
> Thanks!
>
> Felipe
>
> On 28 January 2011 12:17, wrote:
>> Hi Felipe,
>>
>> I'm very sorry about the delay, but at least I'm looking at it n
On 2011/02/06 17:48:56, Trevor Daniels wrote:
This comment of mine from Mark's patch still applies, even after these
changes:
> I've looked at the compiled version now. It's nicely
> written, but my concern is that this is no longer written
> in 'reference' style. To me, parts of it seem mor
New patch set uploaded.
The coding still needs some work, but i need some sleep now ;)
I have an idea how this could work better if i knew how to calculate
something div ((length - basic_length), increments [i])
(my problem is: div wants integers and these arguments are Reals).
Good night :)
htt
2011/2/6 Graham Percival :
> On Sun, Feb 06, 2011 at 07:33:15PM +0100, Francisco Vila wrote:
>> 2011/2/6 Jan Warchoł :
>> > http://paconet.org/lilypond/out-website/website/features.cs.html
>> >
>> > ("Spojení not a textu" column is too narrow)
>> > (WinXP, Chrome)
>>
>> I see this, too. Firefox on
Hi Joe, dear developers,
On the LilyPond French Users mailing list a user asked how to increase
the space between a GrandStaff and the following staff (within a
system).
I suggested to use
\new GrandStaff \with {
\override StaffGrouper #'staffgroup-staff-spacing #'basic-distance = #20
}
2011/2/7 m...@apollinemike.com :
>
> On Feb 6, 2011, at 6:19 PM, Jan Warchoł wrote:
>
>> 2011/2/6 :
>>> I can't really speak to the font stuff.
>>
>> Why not? Every one has his own personal preferences.
>> And the font stuff is what matters the most for me :)
>> Of course some changes are very sub
Hello,
After a couple of rounds of improvements and fixes on Chezh and
Chinese web pages, I am performing a cold build of all the docs and
webpages against a merge onto master. If all goes well, I'll push.
Thanks to Ben Luo and Pavel Fric for their work and patience! I think
it would be fine if y
On 2/6/11 4:19 PM, "Jan Warchoł" wrote:
> 2011/2/6 :
>> And I see that you've wiped a lot of the
>> tabbing in the original code. You may want to start by copying a fresh
>> version of the file into your git repository and then copying and
>> pasting the new code into that to save you the heada
On Mon, Feb 07, 2011 at 06:37:29PM -0700, Carl Sorensen wrote:
> I tried to get that policy implemented, but was not successful. Our current
> policy is "do whatever Emacs does". Emacs can do it either way.
Correction: our current policy is to defer any policy decisions
until GOP. Source format
all pretty now
http://codereview.appspot.com/4014041/diff/1/lily/key-engraver.cc
File lily/key-engraver.cc (right):
http://codereview.appspot.com/4014041/diff/1/lily/key-engraver.cc#newcode93
lily/key-engraver.cc:93: < Rational (0))
On 2011/02/07 22:10:35, Neil Puttock wrote:
indent (align wit
Xavier Scheuer writes:
The only difference I see between GrandStaff and the others is that
GrandStaff does not have "Vertical_align_engraver" .
[...]
Could we add \consists "Vertical_align_engraver" to GrandStaff in
"ly/engraver-init.ly"?
I didn't see a pending patch where this fit
74 matches
Mail list logo
