If you look at the MWE example I provided to illustrate what I believe is
misleading information about a ‘FATAL’ error, then it has plain text which it
ignores, claims a fatal error and proceeds to make a perfectly good PDF. Based
on this it means one can have blocks of text as comments or docum
Hi David,
Unaware of such issue. Can you let me know what mail client you are
using so I can test, so as to avoid this?
Andrew
On 17 April 2016 at 12:29, David Wright wrote:
> Please can you quote in a way that's visible in text clients,
> not just HTML ones.
__
On Fri 15 Apr 2016 at 10:23:55 (+0200), David Kastrup wrote:
> "Phil Holmes" writes:
> > - Original Message -
> > From: "David Kastrup"
> > Sent: Friday, April 15, 2016 8:04 AM
> >> Simon Albrecht writes:
> >>> On 15.04.2016 00:51, Thomas Morley wrote:
> (1) The TupletNumbers are a
Please can you quote in a way that's visible in text clients,
not just HTML ones.
On Sat 16 Apr 2016 at 20:42:45 (+1000), Andrew Bernard wrote:
> I have not used any language of complaint, merely observation and puzzlement.
> It was also not I that mentioned it is a regular source of confusion. O
2016-04-16 16:30 GMT+02:00 Trevor Daniels :
>
> Thomas Morley wrote Friday, April 15, 2016 11:25 PM
>
>> Agreed. I never considered to disallow tuplets over line-break.
>> Gould has nothing to say about it? (I still don't own the book...)
>
> She has a complete chapter devoted to tuplets. She talk
2016-04-16 21:40 GMT+02:00 mj :
> Hi Thomas, (Harm?)
Both alias...
>
> Thanks for the alternatives! :-)
You're welcome,
Harm
>
> MJ
>
>
> On 04/14/2016 10:36 PM, Thomas Morley wrote:
>>
>> 2016-04-14 12:02 GMT+02:00 mj :
>>
>>> I am surprised to see that this:
>
> \parenthesize { c
Hi Thomas, (Harm?)
Thanks for the alternatives! :-)
MJ
On 04/14/2016 10:36 PM, Thomas Morley wrote:
2016-04-14 12:02 GMT+02:00 mj :
I am surprised to see that this:
\parenthesize { c8 c }
does not work to get two notes between two parenthesis?
What's the logic behind that?
Well, the m
2016-04-16 21:30 GMT+02:00 matpen3@gmail :
> Hi David ,
>
> Many thanks. I tried but I’m a newbie and it’s not so clear…
> I typed again and recompiled with ‘update syntax’ but I receive the same
> error.
>
> The code was on a 2.11.13 version.
>
>
> Matteo
Have a look at:
http://lilypond.org/doc
Hi David ,
Many thanks. I tried but I’m a newbie and it’s not so clear…
I typed again and recompiled with ‘update syntax’ but I receive the same error.
The code was on a 2.11.13 version.
Matteo
> Il giorno 16 apr 2016, alle ore 21:13, David Kastrup ha
> scritto:
>
> "matpen3@gmail" writ
"matpen3@gmail" writes:
> Hi all,
>
> I’m trying to shorten the line of consecutive trills to keep them on the same
> line.
> I found a very old thread with a solution:
>
> \once \override TrillSpanner #'bound-details #'right #’padding = #10
>
> but the syntax seems obsolete and I get an error.
Hi all,
I’m trying to shorten the line of consecutive trills to keep them on the same
line.
I found a very old thread with a solution:
\once \override TrillSpanner #'bound-details #'right #’padding = #10
but the syntax seems obsolete and I get an error.
Could you help me?
Many thanks
Matteo
Thomas Morley wrote Friday, April 15, 2016 11:25 PM
> Agreed. I never considered to disallow tuplets over line-break.
> Gould has nothing to say about it? (I still don't own the book...)
She has a complete chapter devoted to tuplets. She talks of tuplets
across barlines (can be sub-divided with
Hello all,
I think I might have found some kind of bug with \partCombine, hoping this is
not useless noise. I did find a workaround, so it's no big problem, but maybe
somebody can shed light on what is wrong.
I'm using a \tag marker in a voice context, because I want the MIDI output to
behav
Hi,
Am 16.04.2016 um 12:52 schrieb Urs Liska:
> There should be *some* sort of order of severity, like "warning",
> "serious error", "fatal error".
Yes. And the wording not only concerns the error itself. But also the
rest of the message. If I compile:
\version "2.19.80"
{ a }
I get a perfectly
Am 16.04.2016 um 12:42 schrieb Andrew Bernard:
> I have not used any language of complaint, merely observation and
> puzzlement. It was also not I that mentioned it is a regular source of
> confusion. Others do seem to think so.
It is probably the first time this *specific* issue has been report
I have not used any language of complaint, merely observation and puzzlement.
It was also not I that mentioned it is a regular source of confusion. Others do
seem to think so. As to being the first, I may possibly be the first to write a
lilypond compile server where I need to understand clearly
The wording 'fatal error' is perhaps a bit strong if a pdf is still
produced. But I always liked it (especially as a beginner) that LilyPond
tries hard to keep on going and produces output if it can, despite
(partially) severe input errors on the user side.
>From my experience, the return code ind
Andrew Bernard writes:
> So gentlemen, since this is a regular source of confusion,
You are the first to have complained.
> and it certainly has had me glued up for many days wondering what is
> wrong with my code, should this not be raised as a defect, or at the
> very least the adjetctive ‘fa
On Sat, 2016-04-16 at 12:14 +1000, Andrew Bernard wrote:
> So gentlemen, since this is a regular source of confusion, and it
> certainly has had me glued up for many days wondering what is wrong
> with my code, should this not be raised as a defect, or at the very
> least the adjetctive ‘fatal’ rem
19 matches
Mail list logo
