Incidentally, I already happened to have one of those in my patch series
where the consequences were all too bad.
Here goes: flex/bison files need, for lack of better alternatives, to be
edited in c++-mode in Emacs.
Unmatched double quotes throw all syntactic entities off terribly. So
I'd tend
2010/5/1 David Kastrup d...@gnu.org:
Incidentally, I already happened to have one of those in my patch series
where the consequences were all too bad.
Here goes: flex/bison files need, for lack of better alternatives, to be
edited in c++-mode in Emacs.
Unmatched double quotes throw all
[2.13.11; AFAIK, nothing has changed in more recent versions w.r.t.
this problem]
Look at the attached example file and its PDF output. This
title = ABCDEDCBA
and this
title = \markup { \fill-line { ABCDEDCBA } }
should have the same horizontal position, IMHO. However, this is not
On 1 May 2010 07:51, Werner LEMBERG w...@gnu.org wrote:
This seems to be a bug...
Yes, \fill-line doesn't like being nested:
http://code.google.com/p/lilypond/issues/detail?id=382
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
This seems to be a bug...
Yes, \fill-line doesn't like being nested:
http://code.google.com/p/lilypond/issues/detail?id=382
Thanks. However, this is only part of the problem. What I would
really like to do is to insert some vertical space. However, doing
subtitle = \markup { \vspace #2
On Fri, Apr 30, 2010 at 09:10:08PM -0700, Mark Polesky wrote:
There's a @knownissues at the end of
NR 1.4.2 Short repeats * Tremolo repeats
that says:
Cross-staff tremolos do not work well.
This comes immediately after a selected snippet that shows
just how well those cross-staff tremolos
Hi Werner,
Thanks. However, this is only part of the problem. What I would
really like to do is to insert some vertical space.
Look for put-mm in the archive.
HTH,
Kieren.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
On 1 May 2010 14:29, Graham Percival gra...@percival-music.ca wrote:
IIRC that warning has been around since before 2004, so I'm not
inclined to trust it. Go ahead.
It might be referring to tremolos between stemless notes; they don't
look too good since the beaming isn't centred between
On 1 May 2010 14:20, Werner LEMBERG w...@gnu.org wrote:
Thanks. However, this is only part of the problem. What I would
really like to do is to insert some vertical space. However, doing
subtitle = \markup { \vspace #2
ABCDEFGFEDCBA }
causes even worse results, as
Thanks. However, this is only part of the problem. What I would
really like to do is to insert some vertical space.
Look for put-mm in the archive.
Nice, thanks! Somehow I missed this completely inspite of reading
virtually all emails concerning lilypond. I wonder whether this
should be
On Sat, May 01, 2010 at 04:05:06PM +0200, Werner LEMBERG wrote:
Thanks. However, this is only part of the problem. What I would
really like to do is to insert some vertical space.
Look for put-mm in the archive.
Nice, thanks! Somehow I missed this completely inspite of reading
I wonder whether this should be added to the documentation...
Please, please, don't ever wonder about this. If anybody finds
anything in the archives that might possibly be useful: add it to
LSR. Don't stop to wonder. Don't think. Do not pass go. Just add
it to LSR.
Adding to the LSR
On Sat, May 01, 2010 at 06:05:36PM +0200, Werner LEMBERG wrote:
Please, please, don't ever wonder about this. If anybody finds
anything in the archives that might possibly be useful: add it to
LSR. Don't stop to wonder. Don't think. Do not pass go. Just add
it to LSR.
Adding to
Seems like nobody reads this thread anymore, or missed out on the
interesting parts. Quoted without attribution for simplicity.
I'd say, a markup-list command signature should follow the pattern:
scheme* markup* markup-list*
that is, any number of scheme arguments, then any number of
just a quick look
http://codereview.appspot.com/969046/diff/2001/3002
File lily/lexer.ll (right):
http://codereview.appspot.com/969046/diff/2001/3002#newcode542
lily/lexer.ll:542: yylval.scm = scm_car(s);
can you document the contents of s in a comment here, for old farts like
me that forgot
Hi Werner,
Kieren's solution essentially circumvents it in a nifty way.
For the record, it's not my solution -- it's Robin's.
Just giving nifty credit where it's due.
Cheers,
Kieren.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Reviewers: hanwenn,
http://codereview.appspot.com/969046/diff/2001/3002
File lily/lexer.ll (right):
http://codereview.appspot.com/969046/diff/2001/3002#newcode542
lily/lexer.ll:542: yylval.scm = scm_car(s);
On 2010/05/01 17:13:32, hanwenn wrote:
can you document the contents of s in a comment
http://codereview.appspot.com/969046/diff/7001/8002
File lily/lexer.ll (right):
http://codereview.appspot.com/969046/diff/7001/8002#newcode545
lily/lexer.ll:545: // loop will be EXPECT_NO_MORE_ARGS.
wouldnt it be clearer to have a function
void translate_markup_signature(SCM predicate_list,
Reinhold Kainhofer wrote:
this raises the question why there is no such option, enabling to setup a
user specific environment or style without having to manipulate this
crucial file (and to adapt it for each new version).
Absolutely! It would also make lilypond-book much simpler, since
hi all,
patch and an example below.
this may look academical, but I need this feature when
transcribing renaissance music - for real life examples see
http://wiki.lilynet.net/index.php/Benkop_projects
the Ockeghem and la Rue examples.
I want to handle rests also; could someone help me
with
20 matches
Mail list logo
