On Wed, 02 Jul 2014 23:56:20 -0700, janek.lilyp...@gmail.com wrote:
you should try
to make the change consistently everywhere ?
Yes, that's what i'm aiming for. However, as you remember, some of
these changes produce unwanted side-effects
I remember you said there were side effects, but
https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely
File Documentation/changes.tely (right):
https://codereview.appspot.com/108130043/diff/90001/Documentation/changes.tely#newcode68
Documentation/changes.tely:68: Add support for @code{\once}@code{\unset}
https://codereview.appspot.com/106160043/diff/20001/ROADMAP
File ROADMAP (right):
https://codereview.appspot.com/106160043/diff/20001/ROADMAP#newcode21
ROADMAP:21: | | Note: Snippets and Internals Reference are
auto-generated
| | Note: Snippets and Internals Reference are
| |
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Thursday, July 03, 2014 7:08 PM
Subject: Re: Line spacing ( was Re: Incipits )
Phil Holmes m...@philholmes.net writes:
David,
Thanks for the info: I'm working
Hi list,
in the following example, I want to align the FretBoards to the
bar lines. Now they are centered over the first beat in each measure.
TIA,
Marc
---
\version 2.19.0
\paper {
indent = 0
ragged-right = ##f
}
frets = {
d'\3 g'\2 b'\1 1 | g\4 cis'\3 e'\2 | cis'\3 fis'\2 a'\1
Am 04.07.2014 09:46, schrieb Marc Hohl:
Hi list,
sorry, wrong list ... I re-posted this question on -user, sorry for the
noise.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
https://codereview.appspot.com/104520043/diff/1/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (right):
https://codereview.appspot.com/104520043/diff/1/Documentation/notation/notation-appendices.itely#newcode1489
https://codereview.appspot.com/106320046/diff/1/Documentation/snippets/new/printing-bar-numbers-with-changing-regular-intervals.ly
File
Documentation/snippets/new/printing-bar-numbers-with-changing-regular-intervals.ly
(right):
Phil Holmes m...@philholmes.net writes:
I resent it with the correct image, but it does not appear to have
arrived. Here it is again.
Oh, it did, but we sent our mails more or less simultaneously. Won't be
able to react before next week since my father is turning 80 today.
--
David Kastrup
Reviewers: Mark Polesky,
https://codereview.appspot.com/104520043/diff/1/Documentation/notation/notation-appendices.itely
File Documentation/notation/notation-appendices.itely (right):
https://codereview.appspot.com/104520043/diff/1/Documentation/notation/notation-appendices.itely#newcode1489
Reviewers: janek, Keith, dak,
Message:
I've rewritten the \applyContext description, and this new patch is
about 40% shorter than the previous one. Please review.
Thanks,
Mark
Description:
The documentation on \applyContext is pretty slim. I'm just mentioning
some new tricks I recently
https://codereview.appspot.com/106320046/diff/1/Documentation/snippets/new/printing-bar-numbers-with-changing-regular-intervals.ly
File
Documentation/snippets/new/printing-bar-numbers-with-changing-regular-intervals.ly
(right):
I happened to notice one little thing while I was skimming through this
(i.e. not a full review, for which I'm not really qualified).
https://codereview.appspot.com/103890046/diff/280001/scm/music-functions.scm
File scm/music-functions.scm (right):
- Original Message -
From: David Kastrup d...@gnu.org
To: Phil Holmes m...@philholmes.net
Cc: lilypond-devel@gnu.org
Sent: Thursday, July 03, 2014 3:57 PM
Subject: Re: Incipits
I don't really have an idea where the scale of ly:grob-layout is
actually coming from, but it would appear
Here's another nasty bug that's hindering progress on my \magnifyMusic
function:
https://code.google.com/p/lilypond/issues/detail?id=3990
Any help is appreciated!
Thanks,
Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
Hi Mark,
do you have any objections against putting this patch on countdown?
As i wrote, this is a transitional phase: the patch improves the
situation, but i intend to make more changes when it becomes clear how
they should look like.
best,
Janek
PS i've fixed whitespace/ordering issues in the
LGTM, thanks!
https://codereview.appspot.com/110060045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2014/07/04 10:29:15, J_lowe wrote:
The problem is (else I would have done what you suggested) is that one
cannot
just use
\clef moderntab { c1 } and it will print like \clef tab { c1 }, so I
was trying
to show that to get that specific clef you must (so it seems) use the
\new
On 2014/07/04 20:47:24, janek wrote:
Hi Mark,
do you have any objections against putting this patch on countdown?
No objections, but I'll leave it to someone else to give the green light
since I'm not qualified to evaluate the C++ code.
As i wrote, this is a transitional phase: the patch
Hi Keith,
2014-07-04 9:07 GMT+02:00 Keith OHara k-ohara5...@oco.net:
On Wed, 02 Jul 2014 23:56:20 -0700, janek.lilyp...@gmail.com wrote:
you should try
to make the change consistently everywhere ?
Yes, that's what i'm aiming for. However, as you remember, some of
these changes produce
I'm sorry, i mistakenly clicked send too early...
2014-07-04 23:26 GMT+02:00 Janek Warchoł janek.lilyp...@gmail.com:
That's actually not what i want to do; I apologize for being unclear.
I *want* the columns to behave the same way in case of both
accidentals and lyrics (and everything else).
2014-07-04 23:21 GMT+02:00 markpole...@gmail.com:
On 2014/07/04 20:47:24, janek wrote:
Hi Mark,
do you have any objections against putting this patch on countdown?
No objections, but I'll leave it to someone else to give the green light
since I'm not qualified to evaluate the C++ code.
ok,
https://codereview.appspot.com/101690043/diff/20001/Documentation/notation/editorial.itely
File Documentation/notation/editorial.itely (right):
https://codereview.appspot.com/101690043/diff/20001/Documentation/notation/editorial.itely#newcode310
Documentation/notation/editorial.itely:310:
On 2014/07/04 21:12:38, Mark Polesky wrote:
On 2014/07/04 10:29:15, J_lowe wrote:
The problem is (else I would have done what you suggested) is that
one cannot
just use
\clef moderntab { c1 } and it will print like \clef tab { c1 }, so I
was
trying
to show that to get that specific clef
24 matches
Mail list logo
