On 2014/10/09 08:11:29, uliska wrote:
On 2014/10/08 05:01:40, Keith wrote:
> Why not store the common music in a variable, and show
> \score {\music}
> \discaredOriginalBreaks
> \score {\music}
> ?
Because it wouldn't work that way. \discardOriginalBreaks
would be interpreted when the comma
2014-10-09 11:38 GMT+02:00 Urs Liska :
> Because one wouldn't want to *finally* produce a version of the score with
> the breaks of the original score. If that's my interest (which then would
> actually be a "rather specific situation") I can simply use hardcoded
> \break commands.
>
> The whole p
2014-10-09 12:41 GMT+02:00 Graham Percival :
> On Thu, Oct 09, 2014 at 10:21:45AM +, tdanielsmu...@googlemail.com
> wrote:
> > I've not followed the corresponding email discussion closely, and maybe
> > I've missed something, but how is this better than simply using \obreak
> > for an original
On 2014/10/09 10:21:45, Trevor Daniels wrote:
It would also be trivial to remove all these editing aids finally with
a simple
global edits.
I think the basic point was to get different aspects of the same
document _without_ doing any edits on it.
https://codereview.appspot.com/150670043/
_
On Thu, Oct 09, 2014 at 10:21:45AM +, tdanielsmu...@googlemail.com wrote:
> I've not followed the corresponding email discussion closely, and maybe
> I've missed something, but how is this better than simply using \obreak
> for an original break, and \nbreak for a new, required, break, having
>
I've not followed the corresponding email discussion closely, and maybe
I've missed something, but how is this better than simply using \obreak
for an original break, and \nbreak for a new, required, break, having
defined
obreak = \break
nbreak = <>
in order to obtain the original breaks. And t
Am 09.10.2014 11:27, schrieb David Kastrup:
Urs Liska writes:
Am 09.10.2014 10:44, schrieb David Kastrup:
Urs Liska writes:
And I would really love to see that being part of LilyPond itself and
not only possible to implement in a library.
Firstly because I would like *all* LilyPond users
Urs Liska writes:
> Am 09.10.2014 10:44, schrieb David Kastrup:
>> Urs Liska writes:
>>
>>> And I would really love to see that being part of LilyPond itself and
>>> not only possible to implement in a library.
>>> Firstly because I would like *all* LilyPond users to have that
>>> available and
Am 09.10.2014 10:44, schrieb David Kastrup:
Urs Liska writes:
And I would really love to see that being part of LilyPond itself and
not only possible to implement in a library.
Firstly because I would like *all* LilyPond users to have that
available and secondly because I would like to add th
Urs Liska writes:
> And I would really love to see that being part of LilyPond itself and
> not only possible to implement in a library.
> Firstly because I would like *all* LilyPond users to have that
> available and secondly because I would like to add this as a Layout
> Control Option to Fresc
Am 08.10.2014 00:30, schrieb nine.fierce.ball...@gmail.com:
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
Important:
* There should be regression tests.
OK. (but only *if* the patch sh
https://codereview.appspot.com/150670043/diff/1/Documentation/notation/spacing.itely
File Documentation/notation/spacing.itely (right):
https://codereview.appspot.com/150670043/diff/1/Documentation/notation/spacing.itely#newcode1857
Documentation/notation/spacing.itely:1857: @end lilypond
On 201
For this particular task, you should also show the user that he can
define at the top of the input, or in a header file if he uses one,
originalBreak = \break
and insert before music where we are done with the original breaks,
originalBreak = {} %\break
That is easy enough to understand, and
On 2014/10/07 22:30:53, Dan Eble wrote:
* When using original breaks, wouldn't one also want original page
size, staff
size, etc.?
That would not map well to tags. Not without additional facilities, I
guess. Still, I think that tags at least address a large enough problem
space that making
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
On 2014/10/07 08:37:06, uliska wrote:
Important:
* There should be regression tests.
Musing:
* Why not use tags? (Example below.)
* Does this implementation make it possible to s
Reviewers: ,
Description:
Add original-breaks.ly commands
The commands defined in this patch allow the user to insert breaks
(line and page) from the original manuscript that are conditionally
respected or discarded. This is very useful for entering and
proof-reading music from larger scores.
A
16 matches
Mail list logo
