On 13 sept. 2012, at 08:31, David Kastrup d...@gnu.org wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
On 12 sept. 2012, at 15:54, Phil Holmes em...@philholmes.net wrote:
Results from my pixel comparator. Some good, some in need of consideration:
Am 12.09.2012 23:59, schrieb Graham Percival:
On Mon, Sep 10, 2012 at 02:28:36PM +0100, James wrote:
Mark,
On 10 September 2012 14:15, Marc Hohl m...@hohlart.de wrote:
Is there a way to rename the patch description that shows up in the
issue tracker? I think I have seen something like this in
c'1-{ s4 s\ s2 z\! }
This looks nice. No idea whether it works, but something into this
directions looks right.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
c'1-{ s4 s\ s2 z\! }
c-d-.
Which one gets the accent?
What should `c-d' mean? AFAIK, there is only one `anchor', namely the
note pitch (which would be `c' in your example). A pitch attached to
a pitch doesn't make sense to me.
If you provide counterexamples, which is good, please
I rather suggest to handle the -{ ... } construct specially, for
example, to allow only `s' and Graham's proposed `z', together with
constructions which work like articulations.
Actually, if we have -{ ... }, we don't need `z' at all:
c'1-{ s4 s\ s2 s\! }
fully does the job, by
Graham Percival gra...@percival-music.ca writes:
On Thu, Sep 13, 2012 at 07:18:50AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
Here's a few imaginary ways of writing the same music:
\at 4 \ \at 1 \! c'1
c'1 y4 y\ y z\!
c'1- y4 y\ y z\!
Werner LEMBERG w...@gnu.org writes:
I rather suggest to handle the -{ ... } construct specially, for
example, to allow only `s' and Graham's proposed `z', together with
constructions which work like articulations.
Actually, if we have -{ ... }, we don't need `z' at all:
c'1-{ s4 s\ s2
Graham Percival gra...@percival-music.ca writes:
On Thu, Sep 13, 2012 at 07:29:35AM +0200, David Kastrup wrote:
Graham Percival gra...@percival-music.ca writes:
With that view (which is evidently not universal), it seems natural to
me to write the pitch and duration first, and then all
m...@mikesolomon.org m...@mikesolomon.org writes:
On 13 sept. 2012, at 08:31, David Kastrup d...@gnu.org wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
Just a note that Les Nereides will go back to its old state w/ the
revert of the fix for 2801. I still need help debugging it,
- Original Message -
From: Keith OHara k-ohara5...@oco.net
To: lilypond-devel@gnu.org; Phil Holmes m...@philholmes.net
Sent: Thursday, September 13, 2012 3:14 AM
Subject: Re: 2.17.2 regtests
On Wed, 12 Sep 2012 12:59:25 -0700, Phil Holmes m...@philholmes.net
wrote:
From: Keith
On 13 sept. 2012, at 10:17, David Kastrup d...@gnu.org wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
On 13 sept. 2012, at 08:31, David Kastrup d...@gnu.org wrote:
m...@mikesolomon.org m...@mikesolomon.org writes:
Just a note that Les Nereides will go back to its old state w/
2012/9/8 Francisco Vila paconet@gmail.com:
Hi John,
as things are today, can we keep doing the usual merges of
translation--staging and master--translation?
I still had no response, but now I have a request. The translation
branch is still in 'stable' status. I think it should be kept so
2012/9/13 Francisco Vila paconet@gmail.com:
therefore if we want to
sync our translations to master, we have no way of knowing what to
translate and what not to.
Sorry, I meant
'If we want to sync our translations with stable, after merging master
(which is development branch) into
Actually, if we have -{ ... }, we don't need `z' at all:
c'1-{ s4 s\ s2 s\! }
fully does the job, by registering the fact that a final `s' comes at
a moment which is equal the anchor's duration (sloppily formulated).
If it does, so does
c'1 { s4 s\ s2 s\! }
Yes.
Or are you
Werner LEMBERG w...@gnu.org writes:
Actually, if we have -{ ... }, we don't need `z' at all:
c'1-{ s4 s\ s2 s\! }
fully does the job, by registering the fact that a final `s' comes at
a moment which is equal the anchor's duration (sloppily formulated).
If it does, so does
c'1 { s4
Il giorno gio, 13/09/2012 alle 10.44 +0200, Francisco Vila ha scritto:
2012/9/8 Francisco Vila paconet@gmail.com:
Hi John,
as things are today, can we keep doing the usual merges of
translation--staging and master--translation?
I still had no response,
I think the message that
2012/9/13 John Mandereau john.mander...@gmail.com:
I think the message that started this thread stated it clearly: From
now on, translation branch at the repository on Savannah should no
longer be merged with master and into staging; instead, it should be
merged with stable/2.16.
Well, right.
2012/9/13 Graham Percival gra...@percival-music.ca:
IIRC, the old style in lilypond was:
(c c)
Students whish this came back, I think. No matter how many times I
insist on it, they always ^H^H^H^H usually fail to remember the
correct form c( c)
I find funny that the solution they figured out
Francisco Vila paconet@gmail.com writes:
2012/9/13 Graham Percival gra...@percival-music.ca:
IIRC, the old style in lilypond was:
(c c)
Students whish this came back, I think. No matter how many times I
insist on it, they always ^H^H^H^H usually fail to remember the
correct form c(
On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote:
Werner LEMBERG w...@gnu.org writes:
Actually, if we have -{ ... }, we don't need `z' at all:
c'1-{ s4 s\ s2 s\! }
This is a little bit unclear, since the final s\! would have the
same duration as the previous s2, and thus
Graham Percival gra...@percival-music.ca writes:
I don't follow this. If we can produce an unambiguous expansion
of
c'1- s4 s\ s2 z\!
into
{ c'1 } { s4 s\ s2 z\! }
then surely it can be expressed as music functions.
\displayLilyMusic would have no chance reconstructing the input.
I think there's still a need for a event
after the previous duration, i.e.
c'1-{ s4 s\ s2 \! }
c'1-{ s4 s\ s2 z\! }
Mhmm. If we have
anchor-{ skip1 skip2 ... skipn skipx }
with
duration(skip1) + duration(skip2) + ... duration(skipn) =
duration(anchor)
then skipx can have
[...]
This is a quantum leap backwards in making LilyPond and Scheme
expressions and variables and functions and arguments in the parser
work and combine in a predictable manner.
I am working hard on stopping the Scheme layer from being something
entirely different and interacting in
Werner LEMBERG w...@gnu.org writes:
[...]
This is a quantum leap backwards in making LilyPond and Scheme
expressions and variables and functions and arguments in the parser
work and combine in a predictable manner.
I am working hard on stopping the Scheme layer from being something
On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote:
I am working hard to get expressions like { s4 s\ s1 s\! } parseable
and recognizable without context, and obliterate the need to write - for
anything except accent shorthands. This is pretty much unavoidable if
you want to get
On Thu, Sep 13, 2012 at 08:56:26PM +0200, David Kastrup wrote:
Graham's and my suggestions are very restrictive, and we are just
playing around with possible syntax forms.
How about considering how they are supposed to translate to and from
Scheme?
Woah. Is the syntax supposed to support
David, please relax. I've typeset hundreds of pages with lilypond,
including complicated piano and organ music; I don't lightly
suggest syntactic stuff just to annoy you.
We are getting most certainly nowhere if people don't even bother
understanding the technical points of my replies.
I
In stepmake/stepmake/help2man-rules.make, I ran across the following:
# We must invoke the generated $(outdir)/help2man script instead of
# the help2man.pl source, which means that the scripts/build directory
# must be built first.
#
# From the perlrun man-page:
#
# If the #! line does not
Graham Percival gra...@percival-music.ca writes:
On Thu, Sep 13, 2012 at 08:56:26PM +0200, David Kastrup wrote:
Graham's and my suggestions are very restrictive, and we are just
playing around with possible syntax forms.
How about considering how they are supposed to translate to and from
Graham Percival gra...@percival-music.ca writes:
On Thu, Sep 13, 2012 at 12:37:00PM +0200, David Kastrup wrote:
I am working hard to get expressions like { s4 s\ s1 s\! } parseable
and recognizable without context, and obliterate the need to write - for
anything except accent shorthands.
On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup d...@gnu.org wrote:
Take a look at the \tempo command. Everybody and their dog tells me
that this is just what a musician wants in syntax. Whenever I do
significant work on the parser, \tempo pitches in with a few dozen
reduce/reduce errors and
For 20:00 MDT Sunday September 16
Enhancement:
Issue 2834
http://code.google.com/p/lilypond/issues/detail?id=2834: Patch: Remove
Brace found at end of markup. warning in lexer - R 6506106
http://codereview.appspot.com/6506106/
Issue 2717
On Thu, Sep 13, 2012 at 11:23:43PM -0300, Han-Wen Nienhuys wrote:
On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup d...@gnu.org wrote:
Take a look at the \tempo command. Everybody and their dog tells me
that this is just what a musician wants in syntax. Whenever I do
significant work on the
Graham Percival gra...@percival-music.ca writes:
On Thu, Sep 13, 2012 at 11:23:43PM -0300, Han-Wen Nienhuys wrote:
On Thu, Sep 13, 2012 at 7:00 PM, David Kastrup d...@gnu.org wrote:
Take a look at the \tempo command. Everybody and their dog tells me
that this is just what a musician wants
Looks better than what is currently in master.
On 2012/09/11 21:03:13, benko.pal wrote:
dots in outer spaces was inspired by your comment
http://codereview.appspot.com/6488097#msg7
I was talking about a tab staff with larger staff-space, but with just
two staff-positions for each line.
35 matches
Mail list logo
