Graham Percival wrote Sunday, January 15, 2012 8:23 AM
I believe this will work out-of-the-box for any .TELY file,
regardless of whether texi2pdf is in the path or not. Please
test.
http://lilypond.org/~graham/lilypond-2.15.25-4.mingw.exe
Well, not quite. Two problems:
1. should be output
Graham, you wrote Sunday, January 15, 2012 9:32 AM
I believe this will at least produce the default line-widths
out-of-the-box for any texinfo or latex file, regardless of
whether texi2pdf is in the path or not. Please test.
http://lilypond.org/~graham/lilypond-2.15.25-5.mingw.exe
I believe
Carl, Although I'm not a current developer, I'd like to comment.
In general I agree, but with the caveats below:
Carl Sorensen wrote Tuesday, January 17, 2012 1:27 AM
So after hearing from most of the currently-active developers, I think a
reasonable goal for 2.16 would be:
1) Work through
David, you wrote Friday, January 27, 2012 2:01 PM
David Kastrup writes:
It would be possible to let q set a parser variable that will optimize
this pass away when unset. The drawback would be that ChordRepeat
events entering via different channels (#{ q #} uses its own
parser, and generat
David Kastrup wrote Tuesday, January 31, 2012 12:47 PM
What would you expect the following to do?
\new StaffGroup { \relative c' { \relative c' { c2 } c } }
It does pretty much what I expected, but then I have been explaining the
drawbacks of implicit contexts for some years now.
I can't
David Kastrup wrote Tuesday, January 31, 2012 2:31 PM
"Trevor Daniels" writes:
No, me neither, but leaving Voice contexts to be implied usually works
well, eg with Staff rather than StaffGroup.
Why would you want to have the above end up in _two_ different voices?
If you w
David Kastrup wrote Tuesday, January 31, 2012 10:13 PM
Any suggestion of how to do the documentation part of issue 2263
differently? That \new Voice sticks out like a wart.
From Documentation/notation/simultaneous.itely (as proposed):
Since nested instances of @code{\relative} don't affect o
Eluze wrote Tuesday, January 31, 2012 10:58 PM
Trevor Daniels wrote:
David Kastrup wrote Tuesday, January 31, 2012 2:31 PM
"Trevor Daniels" writes:
No, me neither, but leaving Voice contexts to be implied usually works
well, eg with Staff rather than StaffGroup.
Why would y
David Kastrup wrote Wednesday, February 01, 2012 7:00 AM
"Trevor Daniels" writes:
David Kastrup wrote Tuesday, January 31, 2012 10:13 PM
Any suggestion of how to do the documentation part of issue 2263
differently? That \new Voice sticks out like a wart.
From Documentatio
Janek Warchoł wrote Thursday, March 01, 2012 12:01 AM
The bad news is that for scores containing a lot of lyrics (like my
SATB pieces) compilation times are now 3-4 times longer than wiith
master. For instrumental scores the situation look better, it's 1.5-2
times longer. I can live with thes
Valentin Villenave wrote Thursday, March 01, 2012 11:05 PM
On Thu, Mar 1, 2012 at 11:26 PM, Graham Percival
wrote:
Umm, no? I mean, literally no? Other than the first+last
releases of each stable branch, those files are gone.
Then I'm sorry to hear that. In case my honest opinion matters (
Valentin, you wrote Friday, March 02, 2012 10:05 AM
On Fri, Mar 2, 2012 at 12:29 AM, Trevor Daniels
wrote:
Valentin - could they not be retrieved from backup if you ask
nicely?
I hope so, but Graham seemed to imply that there actually was NO backup.
Surely the hosting site would take
I've just pushed some fixes to auxiliar/doc-section.sh to staging, as
several things seemed to have gone wrong with it since I last used it. The
script is intended to be used for quickly checking changes made to the
English docs. It compiles a section of the docs to html in a minute or so
and
Hi Phil, you wrote Saturday, March 10, 2012 10:16 AM
Once you have a successful make doc, you might be surprised how little
time it takes to remake to check changes now. On my admittedly quick
machine, make -j9 CPU_COUNT=9 LANGS='' doc takes about 5 seconds.
It's certainly a lot better than
Phil Holmes wrote Sunday, March 11, 2012 3:10 PM
I think I have GUB running properly. I gave up trying to get it working on
64-bit Ubuntu and created a new VirtualBox VM with lilydev 1.1 as the OS.
Congratulations! One of the select few!
Trevor
__
Phil Holmes wrote Sunday, March 11, 2012 4:11 PM
I've just run my pixel comparator and discovered that the regtest
whiteout.ly has a habit of changing between releases - sometimes the not
stem is there, sometimes it's whited out. The description says:
The whiteout command underlays a white
Trevor Daniels wrote Sunday, March 11, 2012 4:23 PM
Phil Holmes wrote Sunday, March 11, 2012 4:11 PM
I've just run my pixel comparator and discovered that the regtest
whiteout.ly has a habit of changing between releases - sometimes the not
stem is there, sometimes it's whited out.
Keith, you wrote Tuesday, March 13, 2012 5:53 AM
Subject: Re: Doc: Learning: Use voices in the intended order. (issue
5507050)
On 2012/03/10 12:36:05, Trevor Daniels wrote:
I could see no reason for this patch causing problems
I had mis-spelled the option to ignore-collisions, which
Julien Rioux wrote Wednesday, March 14, 2012 10:37 AM
On Wed, Mar 14, 2012 at 9:56 AM, Phil Holmes wrote:
- Original Message - From: "Julien Rioux"
To: "Phil Holmes"
The problem with this one is that Lilypond (like Sibelius...) only
provides
4 voices to allow notes to avoid co
Phil Holmes wrote Wednesday, March 14, 2012 12:00 PM
From: "Trevor Daniels"
To: "Julien Rioux" ; "Phil Holmes"
Cc: ;
Sent: Wednesday, March 14, 2012 11:41 AM
Subject: Re: Various updates to reduce make doc output (issue 5727055)
Julien Rioux wrote Wedn
Carl Sorensen wrote Wednesday, March 14, 2012 6:01 PM
On 3/14/12 11:48 AM, "Phil Holmes" wrote:
I've looked at midi2ly and it uses explicit instantiation of voices,
which
is what we normally advise. My understanding is that there are only 4
explicit voices - voiceFive does not exist, AFAIK.
Phil Holmes wrote Thursday, March 15, 2012 8:59 AM
From: "Trevor Daniels"
Carl Sorensen wrote Wednesday, March 14, 2012 6:01 PM
So it would be nice to have a feature added to midi2ly that would
automatically create voiceFive, voiceSix, etc. if needed.
Exactly! Having disc
Hi Janek
An impressive collection of suggested enhancements! I hope your exams don't
suffer!
Most look excellent to me, but I have comments on a couple of them which
I'll add to the issues themselves.
Trevor
- Original Message -
From: "Janek Warchoł"
To: "LilyPond Developmet Tea
Aleksandr Andreev wrote Monday, April 09, 2012 12:39 AM
Looks like the trick with stencil-whiteout does not work in all cases.
Here are two examples.
[snip]
In the second example, the bar line is whited out. But in the first
example, it isn't. Anyone have any pointers as to how to debug this?
Carl Sorensen wrote Monday, April 23, 2012 9:40 PM
Congratulations on having your Lyrics project accepted for Google Summer
of Code!
Wow, congratulations from me too! You really did put the hours in to
generate a great submission - in the middle of your exams too - so you
definitely deserve
Graham Percival wrote Thursday, April 26, 2012 7:07 AM
The Birmingham Amateur Theatre is presenting "Penzance Pirates",
starring our documentation editor Trevor Daniels as the talking lion![1]
[1] this is (probably) not true.
Amazingly, there's an element of truth in it. Re
Werner LEMBERG wrote Friday, April 27, 2012 6:29 AM
I've received a couple e-mails from colleagues and one nudge from
Valentin about:
http://concours.afim-asso.org/
Aah, very nice! Yes, participating in this contest would be a good
thing; and thanks for your offer to writing up the applicat
wrote Friday, April 27, 2012 8:39 AM
On 27 avr. 2012, at 09:33, Trevor Daniels wrote:
But it seems the closing date has passed - wasn't it 25 April?
It's extended till the 29th.
Ah, good! If they needed to do that the chance
of winning is somewhat increased :
wrote Friday, May 04, 2012 8:43 PM
Ok, everybody will love me for my late thinking again. But here we go:
:)
we have two cases of footnotes: one that will attach itself to whatever
happens at a given point of time, being an independent event.
I propose we _always_ let
them try to attach
David Kastrup wrote Sunday, May 06, 2012 2:57 AM
In fact, isn't <> generally prettier than s1*0? Should we be using it
in code and documentation rather than s1*0?
Definitely prettier, but maybe not so transparent as s1*0.
It is not intuitively obvious that an empty chord takes no
time and do
David Kastrup wrote Sunday, May 06, 2012 9:34 AM
Quick: tell me what you would expect without too much thinking (imagine
you are a naive user) from the following:
\new Staff <<
\relative c'' { c4 d e f s1*0-\markup Oops c d e f g1 } \\
\relative c' { c4 d e f <>-\markup Wow c d e f g1 }
Tha
David Kastrup wrote Sunday, May 06, 2012 4:44 PM
"Trevor Daniels" writes:
Actually, I don't think s1*0 appears in the docs.
Documentation/notation/vocal.itely: s1*0^\markup { \right-align { \tiny
"Flute" } }
Documentation/notation/vocal.itely: s1*0_\markup { \r
Graham Percival wrote Sunday, May 06, 2012 10:24 PM
I'm still not happy with an empty chord, especially in the
Learning Manual. I think it leads to the "perlization" of
lilypond, where we end up looking like a ridiculous language like
Haskell.
My point really is that <> exists now, so there
James wrote Monday, May 07, 2012 9:11 AM
Also isn't this a really a GLISS topic?
No. You miss the point: we're not talking about something
new: <> has been valid syntax for years, but its semantics
are not documented. They should be.
Trevor
Graham Percival wrote Monday, May 07, 2012 10:29 AM
Leaving that question aside, we're talking about the preferred
method of having something which does not tamper with the current
duration but does take post-events.
A number of people think that <> is the ideal tool for a
non-duration post-ev
Nicolas Sceaux wrote Monday, May 07, 2012 8:32 PM
Le 7 mai 2012 à 13:58, David Kastrup a écrit :
\relative c' {
e2\p\< d\> s1*0\!
} \addlyrics { Oh no }
\relative c' {
e2\p\< d\> <>\!
} \addlyrics { Oh yes }
I think that closes the s1*0 vs. <> debate.
Because of its unexpected side effects
Keith OHara wrote Tuesday, May 08, 2012 3:48 AM
Trevor Daniels treda.co.uk> writes:
Yes, I now agree. We can't continue to advocate s1*0
in the docs now we are aware of these pitfalls.
I suggest we mention that <> takes no time in NR 1.5.1
Chorded Notes, but avoid it i
David Kastrup wrote Tuesday, May 08, 2012 11:06 AM
"Trevor Daniels" writes:
Keith OHara wrote Tuesday, May 08, 2012 3:48 AM
I suggest we mention that <> takes no time in NR 1.5.1 Chorded
Notes, but avoid it in the examples.
Most of the visible uses of s1*0 in the docs we
Łukasz Czerwiński wrote Sunday, April 29, 2012 12:18 PM
Thanks all three of you for your immediate reply! :) I didn't know
about the glossary. One problem with it is that for musical
terms, except for notes and rests, it works only it the opposite
direction: English -> other language, while th
m...@mikesolomon.org
From: Thierry Coduys
The jury wishes to congratulate you on your LilyPond open source software,
that won the First Prize at the LoMus 2012 contest.
A cheque or bank transfer of 2000 € will be sent to you by the AFIM
w00t!
Mazal tov to everyone!
Belated
Graham Percival wrote Wednesday, June 13, 2012 3:52 AM
> If you were a lilypond developer at any point in time, was your
> motivation to work on lilypond reduced due to "problematic
> reasons" which you are comfortable sharing with us in this
> pseudo-anonymous fashion? What were those reasons o
> Comment #16 on issue 2607 by d...@gnu.org: Patch: Allow immediate Scheme
> expressions to take multiple values
> http://code.google.com/p/lilypond/issues/detail?id=2607
>
> Good idea documenting this, though. That way people have a chance to
> notice.
:) I've noticed, and I've read it, t
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
http://lists.gnu.org/
es the property:"?
But the first method fails on (at least) staff-staff-spacing.
Trevor
- Original Message -
From: "Keith OHara"
To: "James Worlton" ;
Cc: ; "Trevor Daniels"
Sent: Sunday, January 16, 2011 1:09 AM
Subject: Re: global staff-staff sp
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 group
Thanks Keith
Pushed
Trevor
- Original Message -
From: "Keith OHara"
To: "James Lowe" ;
Cc: "Trevor Daniels"
Sent: Wednesday, January 19, 2011 7:25 AM
Subject: Re: Docs: automatic accidentals (was: Odd output)
On Sat, 18 Dec 2010 15:56:25 -0800, Kei
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.
T
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
li
Thanks Carl.
I'll check with Mike to see how he'd like to proceed with this.
Trevor
- Original Message -
From: "Carl Sorensen"
To: "Trevor Daniels" ; "LilyPond-Devel list"
Sent: Monday, January 24, 2011 2:08 AM
Subject: Re: Pentatonic Diat
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 poi
Nice work!
My preference is the "compromise" solution too, for both stems up
and stems down
Trevor
- Original Message -
From: "Janek Warchoł"
To: ; "Carl Sorensen" ;
"Werner LEMBERG" ; "Xavier Scheuer"
Sent: Saturday, January 29, 2011 11:14 PM
Subject: fine-tuning new flags - fe
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'r
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 \transpositio
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 n
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 bl
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:
Sent: Friday, February 04, 2011 10:24 AM
Subject: Re: Add Modal transformations (issue4126042)
http://codereview.appspot.com/4126042/diff/3009/Documentation/notation/pitches.itely#newcode914
Documenta
Changes in http://codereview.appspot.com/4079064/
From:
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 :(
http://codereview.appspot.com/4126042/diff/3009/Documenta
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 wi
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 n
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 that
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" 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 that's what we shou
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
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 used for that
time
signat
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,
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
note-spacing are built as if
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 untransform
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 asce
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:
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:
6ca2619b3ae13ae94b8f43b124e92d86e
Benkő Pál wrote Tuesday, February 22, 2011 10:56 AM
should I move retrograde into its own section now or is there a
volunteer who can improve the documentation on transpose and
inversion as well after pushing as is?
I'm happy to fix up the documentation, so I will
apply this as-is if I hear n
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, but
Francisco Vila wrote Wednesday, February 23, 2011 6:38 PM
2011/2/23 Phil Holmes :
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 layer property) is
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 graphi
Omitted to cc -devel ...
- Original Message -
From: "Trevor Daniels"
To:
Sent: Sunday, February 27, 2011 7:53 PM
Subject: Re: Regression test failure in 2.13.52
Mike
Looks good now. The problem I reported looks to be
fixed, and some misplaced beams apparent in 2.13.51
Graham Percival wrote Monday, February 28, 2011 7:39 AM
On 2/27/11, Janek Warchoł
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 small
increase in some of the stems
"Phil Holmes" 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 the lyrics to t
Janek Warchoł wrote Wednesday, March 02, 2011 8:53 PM
2011/3/1 Trevor Daniels
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 not optimum whe
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"
To:
Sent: Friday, March 04, 2011 12:58 PM
Subject: VirtualBox
I use VirtualBox to run the Li
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 pa
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 optim
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 maybe
wrote Saturday, March 05, 2011 11:05 PM
On Mar 5, 2011, at 17:33, Janek Warchoł
wrote:
2011/3/5 Trevor Daniels :
When I suggested investigating the automatic beaming I didn't
mean messing with the code. But there are a number of
parameters
in the #'details property of beam w
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
lilypond-deve
Hi Xavier
Thanks. Pushed to origin/master.
Trevor
- Original Message -
From: "Xavier Scheuer"
To: "lilypond-devel"
Cc: "e.cauchemez"
Sent: Wednesday, March 09, 2011 2:51 PM
Subject: [PATCH] ly/property-init.ly: remove cautionary accidentals
inimprovisation
Hello dear develope
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
"s
Hi James
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"
Do you fancy adding them, or shall I do it?
Trevor
_
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
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 dec
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 at
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
input/regression/lyric-
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 sho
From:
Personally, I think that an association with some respective
higher
context (aka inheritance) is such a common type of operation that
we
should rather try thinking about how to provide a general
mechanism for
this kind of thing rather than a one-shot special mechanism just
for
lyrics
801 - 900 of 1600 matches
Mail list logo
