On 11.12.2016 08:37, Knut Petersen wrote:
The attached patch should solve your problem.
Thanks for having a look into it! Would you mind posting your patch as
reply under issue 4509, to keep the information in one place?
Sorry to ask so bluntly, but can it really be that simple? I thought a
s
Hi Alexander,
Am 11.12.2016 um 01:17 schrieb Alexander Kobel:
> Ah, no, here's the problem, as can be readily seen in the "Brich an, o
> schönes Morgenlicht", first full measure
I don't think so. Because for notes like the second one in the soprano
voice ("an,"), the added extender line is very s
Btw, I realized that at least visually setting the min. length to 0
already makes the non-melismata hyphens disappear even without your code
to kill them:
\layout {
\override Lyrics.LyricExtender.minimum-length = 0.0
}
{ a a( a) }
\addlyrics { A __ B __}
Cheers,
Joram
__
Am 11. Dezember 2016 08:07:04 MEZ, schrieb Werner LEMBERG :
>
>>> I just don't think I am the best person for the job.
>>
>> Roper has finally posted something I agree with.
>
>Why this unwarranted hostility? His final design was sound, and I
>think we should adapt some key elements. And even i
Noeck writes:
> Btw, I realized that at least visually setting the min. length to 0
> already makes the non-melismata hyphens disappear even without your code
> to kill them:
>
> \layout {
> \override Lyrics.LyricExtender.minimum-length = 0.0
> }
>
> { a a( a) }
> \addlyrics { A __ B __}
But
David Wright writes:
> On Tue 29 Nov 2016 at 09:37:21 (+0100), David Kastrup wrote:
>> David Wright writes:
>>
>> > On Mon 28 Nov 2016 at 21:26:17 (+), Karlin High wrote:
>> >> On 11/28/2016 2:12 PM, David Wright wrote:
>> >> > So it should be worth booting from a live linux CD to mount the
Am 11.12.2016 um 08:23 schrieb David Kastrup:
Werner LEMBERG writes:
I just don't think I am the best person for the job.
Roper has finally posted something I agree with.
Why this unwarranted hostility? His final design was sound, and I
think we should adapt some key elements. And even i
Hi Joram.
On 2016-12-11 09:28, Noeck wrote:
Hi Alexander,
Am 11.12.2016 um 01:17 schrieb Alexander Kobel:
Ah, no, here's the problem, as can be readily seen in the "Brich an, o
schönes Morgenlicht", first full measure
I don't think so. Because for notes like the second one in the soprano
voi
On 2016-12-11 11:04, Alexander Kobel wrote:
Hi Joram.
On 2016-12-11 09:28, Noeck wrote:
Hi Alexander,
Am 11.12.2016 um 01:17 schrieb Alexander Kobel:
Ah, no, here's the problem, as can be readily seen in the "Brich an, o
schönes Morgenlicht", first full measure
I don't think so. Because for
David Kastrup:
> And indeed the externally attached drive (via USB) was named /dev/sda
> while the internal drive the Linux rescue environment booted from was
> /dev/sdb. So this time round the root disk system not being able to
> mount stuff on /dev/sda* had more than one reason.
>
> But I was su
On 2016-12-10 23:33, Alexander Kobel wrote:
On 2016-12-10 20:20, Noeck wrote:
[...]
Would it be possible to have automatic extender lines? For every melisma
there is an extender line if it would be longer than the minimum-length?
Hm. Iterate over lyrics and add Extender events for each syllabl
Am 11.12.2016 um 10:08 schrieb David Kastrup:
Noeck writes:
Btw, I realized that at least visually setting the min. length to 0
already makes the non-melismata hyphens disappear even without your code
to kill them:
\layout {
\override Lyrics.LyricExtender.minimum-length = 0.0
}
{ a a( a
Hi all,
I’ve just been bit by a bug I’ve seen reference to, where
\version "2.19.52"
\include "articulate.ly"
\score {
\articulate {
<<
c'1
\\
e'1
>>
\acciaccatura c'8
c'1 |
}
\layout {}
}
fails
Hi Alexander!
Here's a first shot. Please test thoroughly...
#(define (has-hyphen? event)
(let* ((art (ly:music-property event 'articulations))
(is-hyphen? (lambda (ev) (eq? (ly:music-property ev 'name)
'HyphenEvent
(find is-hyphen? art)))
[]
Thanks a lot for that
Am 11.12.2016 um 09:05 schrieb Simon Albrecht:
On 11.12.2016 08:37, Knut Petersen wrote:
The attached patch should solve your problem.
Thanks for having a look into it! Would you mind posting your patch as reply
under issue 4509, to keep the information in one place?
No. Now and here's the
I've been using this for a while now and sometimes the lyrics are randomly
coloured black instead of being associated with the note colour. I've tried
to find a pattern to it but there doesn't seem to be one. Anyone have any
ideas?
On 27 November 2016 at 16:42, Jack Mackenzie wrote:
> Wonderful!
On 11 Dec 2016 07:23, "David Kastrup" wrote:
Werner LEMBERG writes:
>>> I just don't think I am the best person for the job.
>>
>> Roper has finally posted something I agree with.
>
> Why this unwarranted hostility? His final design was sound, and I
> think we should adapt some key elements.
>> Why this unwarranted hostility?
?
>And my view is, if
> you refuse to use JavaScript, or try to run a defunct browser, that's your
> problem.
That is my view too. I understand about your blind users, but you can
view a javascript-enabled website with a text website. It is possible.
__
On 11.12.2016 17:39, Jack Mackenzie wrote:
Anyone have any ideas?
Certainly not without an example.
Best, Simon
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
I would really love to help, but I can spend the time fighting with
every single person on the thread.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi John,
Am 11.12.2016 um 22:36 schrieb John Roper:
> I would really love to help, but I can spend the time fighting with
> every single person on the thread.
>
Please let me share some personal memories with you.
You may know that I am one of the longer-lasting and pretty active
people in the
Hi list,
on Mutopia Project and other such sites there are quite a few older (as
in version 2.12 or 2.13) lilypond sources.
convert-ly is my friend. However there regularly are settings and commands
that convert-ly does not deal with. Examples would be:
% keep 32nd notes in their beams
#(rev
On 2016-12-11 17:24, Knut Petersen wrote:
Am 11.12.2016 um 09:05 schrieb Simon Albrecht:
Sorry to ask so bluntly, but can it really be that simple? I thought a
solution must consider the x-extent of the syllable vs. the melisma as
well…
I think this is sufficiently easy to handle with the sche
On 11.12.2016 23:33, Alexander Kobel wrote:
IIUC (I didn't compile it in), your patch inhibits extenders on a
single note, correct? Is that really what we want unconditionally, or
are there reasonable use cases where one might want to have an
extender printed after a single note?
That’s a de
> >And my view is, if
> >
> > you refuse to use JavaScript, or try to run a defunct browser, that's
> > your problem.
>
> That is my view too. I understand about your blind users, but you can
> view a javascript-enabled website with a text website. It is possible.
Refusing to use javascript has n
Hi,
> That’s a design question. There are styles which use extenders on single
> notes (e.g. for very wide c.f. notes),
I also think I have seen it for long notes, for instance in a final measure.
I could also think of a situation where a voice splits up into two in
the final measure (bass voice
Hi,
I would like to mark a voice cross over on a piano staff with a
dotted/dashed line.
(I couldn't find anything related to lilypond)
Essentially I want to connect a note in the "upper" stave (played by the
right hand) with the "next" note on the lower stave (played by the left
hand) to mark tha
Hi Alexander
IIUC (I didn't compile it in), your patch inhibits extenders on a single note, correct?
Yes.
Is that really what we want unconditionally,
Currently we get a short extender ... that is imho of no use and should be
killed.
or are there reasonable use cases where one might want
I think John has accomplished a lot of useful things. Chiefly exposing
to the rest of the community the nontrivial nature of maintenance for
the LilyPond website. He also has demonstrated that we appreciate
useful progress or improvement but also are clearly interested in why
that should constitute
On 12.12.2016 00:41, Harald Christiansen wrote:
Hi,
I would like to mark a voice cross over on a piano staff with a
dotted/dashed line.
You need to have the voice cross staves using the \change command, and
use \showStaffSwitch for the lines (both are explained in Notation
Reference, 2.2.1.
Harald,
In Lilypond it is called “staff change lines.” In 2.18 it is at
http://lilypond.org/doc/v2.18/Documentation/notation/common-notation-for-keyboards#staff_002dchange-lines
MRK
From: lilypond-user [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org]
On Behalf Of Harald Chr
The table of contents seems to list its items by the order in which they
were evaluated by the parser, and not by where they actually appear in the
book... Is there a way to avoid this?
for example, even though partB comes AFTER partA in the book, and the PAGES
in the table of contents are right,
Hi Freddy,
On 12 December 2016 at 12:20, Freddy Ouellette
wrote:
> The table of contents seems to list its items by the order in which they
> were evaluated by the parser, and not by where they actually appear in the
> book... Is there a way to avoid this?
>
> for example, even though partB co
Yes... of course that works fine. But it's a workaround, not a fix. The way my
files are laid out, I have several files with individual pieces, and each of
their facsimile pages. I would like to keep these facsimile pages in the same
ly file as the music, but in the final book put all the facsim
On Sun, 11 Dec 2016 23:54:16 +0100, Michael Gerdau wrote:
> I'm fine with using javascript on any site as long as I who generally
> and deliberately disables javascript can still use that site.
I'd like to add: There is good value in javascript for web sites. However,
an astonishing number of we
35 matches
Mail list logo
