Am 23.01.2015 um 18:27 schrieb David Kastrup:
Urs Liska u...@openlilylib.org writes:
Am 23.01.2015 um 18:17 schrieb Urs Liska:
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it listens to implicit break events.
Urs Liska u...@openlilylib.org writes:
Am 23.01.2015 um 18:17 schrieb Urs Liska:
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it listens to implicit break events.
Probably the page breaks are even irrelevant for my
Urs Liska u...@openlilylib.org writes:
Am 23.01.2015 um 18:27 schrieb David Kastrup:
Urs Liska u...@openlilylib.org writes:
Am 23.01.2015 um 18:17 schrieb Urs Liska:
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it
Hi Urs,
On Fri, Jan 23, 2015 at 9:33 AM, Urs Liska u...@openlilylib.org wrote:
Picking up that old thread seems better than starting a new one ...
By now I've reached a different state and would like to come back to this
issue with a very concrete question:
Is it possible to determine at
On Fri, Jan 23, 2015 at 11:52 AM, David Kastrup d...@gnu.org wrote:
Urs Liska u...@openlilylib.org writes:
But when
(ly:grob-property grob 'non-musical)
evaluates to #t then
This is about the case where
(ly:grob-property grob 'non-musical) evaluates to '().
(eq? #t
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it listens to implicit break events.
Probably the page breaks are even irrelevant for my case: finding a way
to recompile individual systems.
what it doesn't do yet is
Urs,
On Fri, Jan 23, 2015 at 11:17 AM, Urs Liska u...@openlilylib.org wrote:
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it listens to implicit break events.
The only time it doesn't write to a file for me is
Am 23.01.2015 um 18:17 schrieb Urs Liska:
Hi David,
thanks, that works great.
It did *not* write to a file, but that's not the issue here.
The main point is that it listens to implicit break events.
Probably the page breaks are even irrelevant for my case: finding a
way to recompile
Picking up that old thread seems better than starting a new one ...
By now I've reached a different state and would like to come back to
this issue with a very concrete question:
Is it possible to determine at which positions (in terms of barnumber
and measure-position) the final line breaks,
