Mark Polesky wrote Sunday, November 07, 2010 4:40 PM
Mark Polesky wrote:
Okay, I think enough votes are in to finalize the most
recent proposal:
http://lists.gnu.org/archive/html/lilypond-devel/2010-11/msg00137.html
I almost forgot... Can we have one last vote among these
two choices?
1)
Mark Polesky wrote Sunday, November 07, 2010 3:30 PM
All right, hopefully everyone here won't mind one last vote,
so please state your preference among the following:
SPACE MINIMUM-DISTANCE
-- --
1) basic-distanceminimum-distance
2)
Graham Percival wrote Sunday, November 07, 2010 12:50 PM
On Sun, Nov 07, 2010 at 12:26:59PM -, Trevor Daniels wrote:
Valentin Villenave wrote Sunday, November 07, 2010 10:35 AM
I'm not sure if we've ever used convert-ly to insert comments in
.ly
files, but I do think we should
Graham Percival wrote Sunday, November 07, 2010 1:07 PM
On Sun, Nov 07, 2010 at 12:50:20PM +, Graham Percival wrote:
The normal method would be for convert-ly to print a warning
message to the console. Why is this Dynamics thing so different
from previous changes?
Another option is to
Mark Polesky wrote Monday, November 08, 2010 1:24 AM
Instead of these two:
withingroup-staff-staff-spacing
staffgroup-staff-spacing
Let's stay with these.
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Reinhold Kainhofer wrote Monday, November 08, 2010 12:09 AM
Am Sonntag, 7. November 2010, um 20:46:54 schrieb Trevor Daniels:
I think this would be an improvement, but I don't think it's
essential. The file will be left in an erroneous state so
the user will be forced into further
Valentin Villenave wrote Monday, November 08, 2010 11:16 AM
On Mon, Nov 8, 2010 at 11:13 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
There might even be an argument for adding something
which made compilation fail - in a way that clearly
indicated the problem, of course.
Bold idea
Mark Polesky wrote Monday, November 08, 2010 7:14 PM
Keith E OHara wrote:
We will use this in context that makes that first
qualifier almost redundant :
\override Context.StaffGrouper #'withingroup-staff-staff-spacing
This is an excellent point, and in response I'd like to
propose one more
Trevor Daniels wrote Tuesday, October 19, 2010 8:34 PM
Keith E OHara wrote Monday, October 18, 2010 11:40 PM
I suggest (diff attached) removing the part about
instrumentCueName in favor of a fuller example for \killCues.
The manual teaches markup elsewhere; the challenge with cue-note
markpole...@gmail.com wrote Friday, November 12, 2010 10:48 PM
On 2010/11/12 21:53:41, Mark Polesky wrote:
I might like to keep staff-staff-spacing for the StaffGrouper
prop. I'm thinking it over, and I'll get back to you.
Guys, I'd rather not change StaffGrouper's
'staff-staff-spacing to
Mark, you wrote Saturday, November 13, 2010 12:50 AM
I think I made every suggestion except one. I didn't
change grob to layout object, just because grob
appears as a word so often in define-grob-properties.scm,
and layout doesn't appear once:
That may be so, but it's a standard term in
Mark Polesky wrote Monday, November 15, 2010 5:18 AM
These are essentially \paper variables, right?
oddHeaderMarkup
evenHeaderMarkup
oddFooterMarkup
evenFooterMarkup
You have to set them in the \paper block, it seems, so I
would like to categorize them alongside things like
This is the second time this has come up recently.
Sounds like a good candidate for an enhancement request.
Trevor
- Original Message -
From: jakob lund jakob.be...@gmail.com
To: lilypond-u...@gnu.org
Sent: Wednesday, November 17, 2010 9:22 AM
Subject: music function
Hi
I have two
Valentin Villenave wrote Wednesday, November 17, 2010 10:47 AM
On Wed, Nov 17, 2010 at 10:41 AM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Sounds like a good candidate for an enhancement request.
my brain seems to be in low-power mode today, could you help me
rephrase this request so I
Graham Percival wrote Saturday, November 20, 2010 8:40 PM
Who wants to edit the CG for this? James is away for a few days,
so there's no point leaving it as a learn how to use git
exercise. Somebody please edit the CG and push (no reitveld
necessary).
Done
Graham: please check the commit
Trevor Daniels wrote Sunday, November 21, 2010 11:58 PM
Graham Percival wrote Sunday, November 21, 2010 11:18 PM
On Sun, Nov 21, 2010 at 09:38:42AM -, Trevor Daniels wrote:
Graham Percival wrote Saturday, November 20, 2010 8:40 PM
Who wants to edit the CG for this? James is away
Reinhold Kainhofer wrote Monday, November 22, 2010 4:35 PM
I'm currently trying to make cue notes much better supported in
LilyPond. In
particular, it's not as simple as quoting the notes in a CueVoice.
In real
scores, there are several different options to take into account:
-) Transpose
Carl Sorensen wrote Monday, November 22, 2010 4:54 PM
On 11/22/10 9:35 AM, Reinhold Kainhofer reinh...@kainhofer.com
wrote:
Do you have any idea how to properly add options for the
cueDuring command in
LilyPond???
I think you define cue-during-details as a music property, and
then do
Reinhold Kainhofer wrote Monday, November 22, 2010 7:56 PM
Am Montag, 22. November 2010, um 18:57:01 schrieben Sie:
Would it not be better to define these properties using
\addInstrumentDefinition #flute ...
and then simply refer to flute in \cueDuring, as
\instrumentSwitch does?
Valentin Villenave wrote Friday, November 26, 2010 1:40 AM
On Fri, Nov 26, 2010 at 1:11 AM, Graham Percival
I don't think that @/ is appropriate. Certainly not for a short
@file{filename.ext}. I'm willing to entertain the notion of using
them inside a
Valentin Villenave wrote Friday, November 26, 2010 3:00 PM
Here's what I'm thinking (I'll update the doc guidelines if you
guys agree):
@file{} entries should not contain a @/ escape sequence, unless
these
are long enough to justify a possible line break.
Tick, as a policy statement.
Valentin Villenave wrote Friday, November 26, 2010 5:51 PM
On Fri, Nov 26, 2010 at 4:47 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Long entries are those who contain either more than one dash or
more
that :)
than one slash (not counting ../).
Er, are you suggesting that
@file
Carl Sorensen wrote Friday, November 26, 2010 6:43 PM
On 11/26/10 10:51 AM, Valentin Villenave
valen...@villenave.net wrote:
Please have a look at the attached patch:
http://dl.free.fr/pMyOkyICo
I like the new patch, I think. I believe that it
would be preferable to do this instead of
Valentin Villenave wrote Friday, November 26, 2010 10:31 PM
Thanks! I've pushed this patch, and merged translation onto master
Great! Appreciated!
On Fri, Nov 26, 2010 at 10:41 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
Ideally, yes. But who is going to look manually through
Carl Sorensen wrote Saturday, November 27, 2010 12:03 AM
On 11/26/10 4:26 PM, Valentin Villenave valen...@villenave.net
wrote:
I've fixed all @file refs that were more than 50-chars long
(there
were only a dozen or so, so this really was no big deal).
Most of these file references aren't
Carl Sorensen wrote Saturday, November 27, 2010 4:10 AM
Neil found a bug in the code. What happens when
someone requests an open string that isn't present
in the tuning?
I've got the code fixed to issue a warning. After
issuing the warning, we have two choices:
1 -- leave the improper
Graham Percival wrote Saturday, November 27, 2010 12:59 AM
On Fri, Nov 26, 2010 at 11:31:06PM +0100, Valentin Villenave
wrote:
On Fri, Nov 26, 2010 at 10:41 PM, Trevor Daniels
t.dani...@treda.co.uk wrote:
OK; I agree. Patch looks good.
Thanks! I've pushed this patch, and merged
Graham Percival wrote Monday, November 29, 2010 7:33 AM
With that in mind, I'm reopening the same question as the 24 Oct
email.
2) release 2.14 ASAP with no critical flaws, but with some kind of
code freeze.
I prefer a variant on this. Branch 2.14 now and apply only
patches to critical
Francisco Vila wrote Tuesday, November 30, 2010 2:31 PM
Hello. As you probably know, Savannah has been down for days; now
it
is almost restored but latest backups are not newer than those of
November 24th. We should look at our local repos, try to restore
the
history and find out whether
Neil
http://codereview.appspot.com/3406041/diff/6001/Documentation/notation/spacing.itely#newcode1297
Documentation/notation/spacing.itely:1297: c4 c c~ | \break %
this
\break works
On 2010/12/02 08:34:52, Trevor Daniels wrote:
indent; needs another c
adding another c will make the break
Mark Polesky wrote Wednesday, December 08, 2010 5:52 PM
But which one is better?
1)
padding – the minimum required amount of vertical whitespace
between two items, measured in staff-spaces. When
available, skylines are used in the spacing calculation.
2)
padding – the minimum required
Carl Sorensen wrote Tuesday, December 14, 2010 12:55 PM
On Dec 14, 2010, at 5:45 AM, Dmytro O. Redchuk
brownian@gmail.com wrote:
I fail to see why this test (accidental.ly) would be less
valuable
if there
would be \key c \major, let's say.
Because you want to ensure that it behaves
Graham, you wrote Thursday, December 16, 2010 5:25 PM
Could you try replacing it with an -o ? apparently -or is not
posix compliant, but it doesn't say that -o is not posix.
find Documentation/ -path 'Documentation/snippets' -prune -o -name
'*.itely' | grep rhythms
In case it's helpful,
Colin Campbell wrote Friday, December 17, 2010 4:44 AM
Hi Colin - pleased you found this easy. Just one comment ..
3. Working with source code (was section 2)
* left as is, although why do we use git on Windows if we can't
build?
If we're pointing Windows and MacOS users to lilybuntu, let's
Phil Holmes wrote Friday, December 17, 2010 10:12 AM
From: Trevor Daniels t.dani...@treda.co.uk
64 bit vista. 6 Gigs RAM. The odd 1 Gig for a VM has no effect
:-)
Lucky you ! It certainly does on my 3Gb laptop (at its maximum).
Trevor
http://lists.gnu.org/archive/html/lilypond-devel/2005-05/msg00200.html
Mark Polesky wrote Tuesday, December 21, 2010 5:12 AM
In texinfo:
@cindex foo-- add foo to the concept index
@findex foo-- add foo to the function index
@kindex foo-- add foo to the keystroke index
Valentin Villenave wrote Tuesday, December 21, 2010 8:14 PM
I've been looking at the LM 4.4.2 Placement of objects
Within-staff
objects, and I'm not sure we want to use Down/Left and
Up/Right in
the table. Yes, we all know that -1 and 1 may respectively mean
either
down or left and either
Carl Sorensen wrote Tuesday, December 21, 2010 10:22 PM
On 12/21/10 1:14 PM, Valentin Villenave valen...@villenave.net
wrote:
Oh, and by the way: we have \textSpannerDown for text spanners,
but
not \textDown for simple TextScript objects (that are quite
likely to
be needed by new users).
Federico Bruni wrote Wednesday, December 22, 2010 4:10 PM
2010/12/22 Mike Solomon mike...@ufl.edu
1) svgdance.svg (best viewed in something that's not Internet
Explorer -
click on the notes and/or accidentals and see what happens!)
Actually, only clicks on notes work here (FF4 and
Thanks Keith - checked and pushed to origin/master.
Trevor
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: carl.d.soren...@gmail.com; tdanielsmu...@googlemail.com;
percival.music...@gmail.com; lilypond-devel@gnu.org;
re...@codereview.appspotmail.com;
Janek Warchoł wrote Tuesday, December 28, 2010 3:28 PM
2010/12/27 Trevor Daniels t.dani...@treda.co.uk
I know next to nothing about ancient notation, but whoever wrote
gregorian.ly clearly intended this behaviour as the file contains
the override
\override SpacingSpanner #'packed-spacing
Reinhold Kainhofer wrote Tuesday, December 28, 2010 9:10 PM
I have now uploaded a final patch for cue notes with custom clef,
which I think
is in a state so that it can be included in lilypond master:
http://codereview.appspot.com/2726043/
Any further objectsions/suggestions? Or can I push
tdanielsmu...@googlemail.com wrote Saturday, December 25, 2010 9:07
AM
If there are no averse comments over Christmas I'll push this next
week.
Now pushed. Thanks again Keith.
http://codereview.appspot.com/3782042/
Trevor
___
Reinhold, you wrote Wednesday, December 29, 2010 12:13 PM
Am Mittwoch, 29. Dezember 2010, um 12:13:08 schrieb Trevor
Daniels:
I see this has been pushed now, but I wondered why
ambitus was removed from the space-alist of Clef?
AFAIU, the space-alist controls spacing of the current grob
Graham Percival wrote Thursday, December 30, 2010 3:56 AM
On Wed, Dec 29, 2010 at 12:32:56PM -, Phil Holmes wrote:
From: Carl Sorensen c_soren...@byu.edu
On 12/28/10 4:18 PM, Graham Percival
gra...@percival-music.ca wrote:
The difference between Phil's version and the previous version
Graham Percival wrote Friday, December 31, 2010 11:20 PM
On Thu, Dec 30, 2010 at 08:43:36PM +, Keith OHara wrote:
Trevor Daniels t.daniels at treda.co.uk writes:
Graham Percival wrote Thursday, December 30, 2010 3:56 AM
I want to keep the word intentionally, though
Graham Percival wrote Saturday, January 01, 2011 7:16 AM
Nope, for precisely the reason you gave earlier: our documentation
generally has zero input from programmers, so it's not at all a
good representation of what's intended.
We have a set of intended to be working examples. They're
Graham Percival wrote Friday, January 07, 2011 11:01 AM
I'd quite like to go with a default good output; optional poor
output but faster processing policy.
+1
Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
:?
But the first method fails on (at least) staff-staff-spacing.
Trevor
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: James Worlton jworl...@gmail.com; lilypond-u...@gnu.org
Cc: lilypond-devel@gnu.org; Trevor Daniels
t.dani...@treda.co.uk
Sent: Sunday, January 16, 2011 1
Keith OHara wrote Wednesday, January 19, 2011 7:25 AM
Follow-up patch attached.
The misleading bit was the implication that the properties always
contain alists, when one of them is by default a function
returning whichever alist is appropriate depending on whether the
staff is in a
Thanks Keith
Pushed
Trevor
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: James Lowe james.l...@datacore.com; lilypond-devel@gnu.org
Cc: Trevor Daniels t.dani...@treda.co.uk
Sent: Wednesday, January 19, 2011 7:25 AM
Subject: Re: Docs: automatic accidentals (was: Odd
Trevor Daniels wrote Wednesday, January 19, 2011 12:43 PM
Keith OHara wrote Wednesday, January 19, 2011 7:25 AM
Follow-up patch attached.
This looks fine to me. I'll push it in a day or two if there are
no adverse comments.
Pushed.
Trevor
Reinhold Kainhofer wrote Thursday, January 20, 2011 7:31 PM
In NR 2.1.1 (Multiple notes to a syllable) we have an example
for
melismaBusyProperties, which is extremely misleading, as it gives
the
expression that this property can be used to skip notes without
assigning a
lyrics syllable:
Francisco Vila wrote Sunday, January 23, 2011 10:01 AM
The patch (attached) for English docs only; compiles fine.
Not my most favourite piece of vocal music, but it
makes a fine headword!
LG to push TM.
Trevor
___
lilypond-devel mailing list
Thanks Carl.
I'll check with Mike to see how he'd like to proceed with this.
Trevor
- Original Message -
From: Carl Sorensen c_soren...@byu.edu
To: Trevor Daniels t.dani...@treda.co.uk; LilyPond-Devel list
lilypond-devel@gnu.org
Sent: Monday, January 24, 2011 2:08 AM
Subject: Re
Xavier Scheuer wrote Thursday, January 27, 2011 1:06 PM
Issue #1401: Doc: NR 2.1.2 Lyrics and repeats, improvement
proposals
http://code.google.com/p/lilypond/issues/detail?id=1401
has been opened further to my message. Could you update it
accordingly?
OK, I'll have a look.
Also Mats
Nice work!
My preference is the compromise solution too, for both stems up
and stems down
Trevor
- Original Message -
From: Janek Warchoł lemniskata.bernoull...@gmail.com
To: lilypond-devel@gnu.org; Carl Sorensen c_soren...@byu.edu;
Werner LEMBERG w...@gnu.org; Xavier Scheuer
While adding issue 1499 I inadvertently made John Mandereau the
owner. Sorry John!
Phil, could you please fix this up for me? Although I am listed as
a contributor the entry for me that appears in the pull-down list
for owner is not acceptable for some reason.
Trevor
Graham Percival wrote Tuesday, February 01, 2011 7:16 PM
On Tue, Feb 01, 2011 at 04:18:38PM -, Trevor Daniels wrote:
Phil, could you please fix this up for me? Although I am listed
as
a contributor the entry for me that appears in the pull-down list
for owner is not acceptable for some
Graham Percival wrote Tuesday, February 01, 2011 9:28 PM
On Tue, Feb 01, 2011 at 09:09:50PM -, Trevor Daniels wrote:
Any idea why my entry as contributor fails? It looks right.
If you mean why couldn't I edit that field, then I'd
double-check that you're logged in.
If you mean why
Keith wrote Thursday, February 03, 2011 7:22 AM
http://codereview.appspot.com/4126042/diff/5002/ly/music-functions-init.ly#newcode465
ly/music-functions-init.ly:465: modalInversion =
Since it is an operator, should it be a verb, modalInvert ?
The distinction between \transpose and
Graham Percival wrote Wednesday, February 02, 2011 7:38 PM
IIRC, diatonic can refer to any church mode.
Let me rephrase / alter my initial suggestion: might it be worth
having some predefined scales for actually well-defined scales?
Like \major or \locrian or the like? They could go in a
Benkő Pál wrote Thursday, February 03, 2011 3:28 PM
I think for these purposes all church modes are equivalent.
the different minor scales are truly different.
Don't some church modes have an optional flat?
For pentatonic scales there are even more in common use,
I believe. Even the five
Pal wrote Friday, February 04, 2011 5:11 PM
http://codereview.appspot.com/4126042/diff/3009/scm/modal-transforms.scm#newcode68
scm/modal-transforms.scm:68: (lambda (pivot-pitch pitch)
I'm afraid this is not a good interface, as there are inversions
where
the pivot is between two notes.
e.g.
Changes made in http://codereview.appspot.com/4079064/
- Original Message -
From: n.putt...@gmail.com
Sent: Friday, February 04, 2011 10:24 AM
Subject: Re: Add Modal transformations (issue4126042)
Changes in http://codereview.appspot.com/4079064/
From: percival.music...@gmail.com
Sent: Friday, February 04, 2011 1:43 AM
Subject: Re: Add Modal transformations (issue4126042)
LGTM. I don't think you need to wait until Sat.
Perhaps I should have waited :(
Michael Ellis wrote Saturday, February 05, 2011 4:23 PM
In practice, it will be more efficient to code it as Pal suggests,
with two index operations -- although I have no idea whether the
efficiency gain would be significant in terms of LilyPond's total
processing overhead.
I'm not unhappy
Carl Sorensen wrote Saturday, February 12, 2011 4:03 AM
In my opinion, we should never use direct formatting
commands such as @i{} in the text. We want logical
descriptors, rather than formatting descriptors.
Does anybody else agree with me?
Yes, I do. Although it was quite likely
Graham, you wrote Sunday, February 13, 2011 2:32 AM
Hey guys, could you push your patches that have passed review?
That's:
1499 Modal transformations
Still waiting for an update from Mike Ellis.
1426 Better support for beat slashes
1211 Optimizations for pure-heigh approximations
Cheers,
Carl Sorensen wrote Saturday, February 12, 2011 3:39 PM
On 2/12/11 6:39 AM, Phil Holmes m...@philholmes.net wrote:
and go to Spacing of non-staff lines and then mod that a bit,
we get the
attached file (it's a bit long for in-line, IMO). This produces
the output
attached. Don't think
percival.music...@gmail.com wrote Saturday, February 05, 2011 6:20
PM
http://codereview.appspot.com/4079064/diff/1/Documentation/notation/pitches.itely#newcode827
Documentation/notation/pitches.itely:827: it may be converted to
its
@notation{retrograde} (written backwards).
I'm not certain
percival.music...@gmail.com
http://codereview.appspot.com/4160048/diff/11001/Documentation/notation/rhythms.itely#newcode2229
Documentation/notation/rhythms.itely:2229: changed, so that when
the
time signature is set the desired
What about:
... changed, so that the desired beaming is always
Carl Sorensen wrote Saturday, February 12, 2011 9:09 PM
I've attached a .ly file and its output. I think it gives the
desired
output. I'd welcome any comments.
Looks useful.
What about adding a third argument so 'staff-affinity
becomes set within the function too?
\setLyricSpacing #25
Keith OHara wrote Wednesday, February 16, 2011 8:54 PM
On Wed, 16 Feb 2011 08:08:10 -0800, tdanielsmu...@googlemail.com
wrote:
On 2011/02/15 18:36:06, Keith wrote:
If there is /any/ protrusion on the lyrics side of the staff,
anywhere in the score, then the PaperColumn skylines used for
http://codereview.appspot.com/4079064/diff/7001/Documentation/notation/pitches.itely#newcode830
Documentation/notation/pitches.itely:830: left untransformed and a
warning given.}
I'd omit the and a warning given. I mean, the warning will be
obvious, right? Just end with ... left
http://codereview.appspot.com/4079064/diff/7001/Documentation/notation/pitches.itely#newcode861
Documentation/notation/pitches.itely:861: A scale of any length
and with
any intervals may be specified:
An ascending scale of any length ...
The octaves are linked smoothly if the scale is
Graham (or any TeX wizard)
make doc was failing for me with
TeX capacity exceeded, sorry [save size=5000].
I hacked etc/texmf/texmf.cnf to increase save size,
which allowed make doc to proceed, but what is the
correct way to fix this?
Trevor
From: percival.music...@gmail.com
Thursday, February 17, 2011 6:32 PM
Ok, it seems we're all ok with this.
Keith, please email the patch to Trevor for pushing.
http://codereview.appspot.com/4187043/
Pushed:
6d751144f402dc58ff3f65df0fcaab021a86908c
and reg tests bumped to 2.13.51:
Graham, you wrote Sunday, February 20, 2011 10:07 PM
On Thu, Feb 17, 2011 at 11:47:17PM -, Trevor Daniels wrote:
make doc was failing for me with
TeX capacity exceeded, sorry [save size=5000].
I hacked etc/texmf/texmf.cnf to increase save size,
which allowed make doc to proceed
Francisco Vila wrote Wednesday, February 23, 2011 6:38 PM
2011/2/23 Phil Holmes m...@philholmes.net:
Another change I don't understand.
Although I don't understand much about regtests, this difference
could
show that printing order of objects in the same layer (with the
same
value of the
Graham Percival wrote Wednesday, February 23, 2011 2:23 AM
On Tue, Feb 22, 2011 at 04:33:34PM +, James Lowe wrote:
Hello
)After increasing save size to 1 the doc build completed
perfectly, so
)all is OK at the moment, but as I hacked a file which says
don't hack this
)I guess it
Several regression tests fail in 2.13.52. Beams
are misplaced, some randomly in different runs,
and some fail with no beam positions? error.
Here's the output of one:
GNU LilyPond 2.13.52
Processing `collision-merge-differently-dotted.ly'
Parsing...
Interpreting music...
Preprocessing
Graham Percival wrote Monday, February 28, 2011 7:39 AM
On 2/27/11, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
Here you are. This contains all the changes and should apply
cleanly
to origin/master.
Thanks, pushed.
This commit causes many changes to the reg tests due to the
Phil Holmes m...@philholmes.net wrote in message
news:iklsd6$r1v$1...@dough.gmane.org...
lyrics-bar.png - the music now breaks over the line to accommodate
the text
(which is OK), but see the no now sitting in the stave. Anyone
know
what's going on here?
This is OK. The no is part of
Janek Warchoł wrote Wednesday, March 02, 2011 8:53 PM
2011/3/1 Trevor Daniels t.dani...@treda.co.uk
Yes, they are longer, but the stems on the full-size notes look
too long
in this context to my eye.
I've attached the output from 2.13.52.
In my opinion it is ok.
It's OK; just
Hi Phil
I did this a few days ago. No problems. I sent a note
about it to -devel, but it didn't seem to get distributed.
I've attached it.
Trevor
- Original Message -
From: Phil Holmes m...@philholmes.net
To: lilypond-devel@gnu.org
Sent: Friday, March 04, 2011 12:58 PM
Subject:
Patrick Schmidt wrote Friday, March 04, 2011 4:17 PM
Hmm, it doesn't apply for me. Could you do a git pull -r , and
then
try making the patch again?
Sorry for that. Don't know what I'm doing wrong. How about this
one?
The problem is the line endings. They are DOS but should be Unix
in
Janek Warchoł wrote Friday, March 04, 2011 11:42 PM
this is the next step of making stems and flags more beautiful:
i suggest making unbeamed 32nd stems a bit shorter than they are
now.
The main reason for doing so is to better match the stem length of
the
beamed notes.
As we know, the
Janek Warchoł wrote Saturday, March 05, 2011 12:05 PM
while i'd love to improve beaming algorithm itself so that it
would
produce perfect beams on its own, it's a task way beyond my
current
skills. Still some wrong beams bother me very much, for example
this
one
\relative c'' { b8[ a16 g]
Janek Warchoł wrote Sunday, March 06, 2011 1:54 AM
I was curious too, so i wrote it down.
Indeed it looks like he used non-default layout (by default Lily
uses
3 systems), but i won't call it non-optimal. In my opinion fitting
this music in two systems is perfectly reasonable here (and
m...@apollinemike.com wrote Saturday, March 05, 2011 11:05 PM
On Mar 5, 2011, at 17:33, Janek Warchoł
lemniskata.bernoull...@gmail.com wrote:
2011/3/5 Trevor Daniels t.dani...@treda.co.uk:
When I suggested investigating the automatic beaming I didn't
mean messing with the code
Janek Warchoł wrote Tuesday, March 08, 2011 3:42 PM
i don't see any discussion going on here, so i assume you agree to
shortening the 32nd unbeamed stem.
I attach the patch.
I'm happy with it.
Trevor
___
lilypond-devel mailing list
Hi Xavier
Thanks. Pushed to origin/master.
Trevor
- Original Message -
From: Xavier Scheuer x.sche...@gmail.com
To: lilypond-devel lilypond-devel@gnu.org
Cc: e.cauchemez e.cauche...@laposte.net
Sent: Wednesday, March 09, 2011 2:51 PM
Subject: [PATCH] ly/property-init.ly: remove
Janek Warchoł wrote Wednesday, March 09, 2011 11:11 PM
next thing is to decide what the output of { c32 c[ c] c64 c[ c] }
should
be.
Currently the stems of unbeamed notes are lenghtened to middle
line only
(current output.png).
In my opinion this looks weird, i'd suggest something like
Graham Percival wrote Wednesday, February 02, 2011 7:42 PM
On Wed, Feb 02, 2011 at 11:37:43AM -, Trevor Daniels wrote:
Graham Percival wrote Tuesday, February 01, 2011 9:28 PM
If you mean why can't I be set to be the owner of this issue,
then... I couldn't set it to you
James Lowe wrote Friday, March 11, 2011 11:34 PM
From: Trevor Daniels [t.dani...@treda.co.uk]
I just noticed that none of the new spacing properties
in spacing.itely have @funindex entries. These are
needed so people can follow-up error messages like
staff-affinities should only decrease
Janek Warchoł wrote Friday, March 18, 2011 11:41 AM
I've prepared flag touch-ups, including changes suggested by Carl.
They are here:
http://codereview.appspot.com/4273074/
I attach a simple proof-sheet showing these changes.
I prefer your suggested flags. Thanks.
Trevor
percival.music...@gmail.com wrote Monday, March 28, 2011 3:02 PM
Time for complaints is over; please push.
http://codereview.appspot.com/4309052/
Actually the time-out is 23.59 tonight. I'll wait
'til then. (But I already pushed
http://codereview.appspot.com/4313047/,
which times out
n.putt...@gmail.com wrote Monday, March 28, 2011 9:17 PM
I hope you don't mind the following late comments. :)
Not at all; I pushed it earlier than I should anyway. Thanks!
http://codereview.appspot.com/4313047/diff/1/input/regression/lyric-hyphen-grace.ly#newcode15
http://codereview.appspot.com/4323045/diff/1/ly/engraver-init.ly#oldcode424
ly/engraver-init.ly:424: instrumentName = #'()
I'm missing something from the commit message -- why are you
removing
these?
They were in the context definition twice, so I deleted
one of the duplicates. Sorry, I
601 - 700 of 1527 matches
Mail list logo
