Dan Eble | 1 Aug 19:35 2015
Picon

missing/empty files

I have a couple of related suggestions.  These would be minor conveniences—so minor that I don’t care
enough at the moment to implement them myself.

let convert-ly remain silent about files which contain only whitespace (or which are empty) rather than
issuing an error that there is no \version statement

add a variant of \include which does nothing if the file does not exist (eliminating one reason to have empty
files in the first place)
— 
Dan

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht | 31 Jul 15:10 2015
Picon

BreathingSign and NoteHead collide

\paper { line-width = 10 }
{ f'' \breathe \bar "|" }

The collision occurs with both 2.18.2 and 2.19.23.

Thank you,
Simon
to7m | 29 Jul 20:33 2015
Picon

Re: Cross-system tied accidentals not hidden

>> % The 2nd system's accidental is correctly hidden, but the 4th system's is
>> % incorrectly present. The 6th system uses the workaround of placing the
>> % hide-tied-accidental-after-break bit in the voice. The direction of the
>> % ties is different too.
>>
>>
>> \version "2.18.2"
>>
>> { \override Accidental #'hide-tied-accidental-after-break = ##t
>>   { \break ges1~
>>     \break ges
>>     \break << { ges1~
>>     \break ges } \\ >>
>>     \break << { \override Accidental #'hide-tied-accidental-after-break =
>> ##t ges1~
>>     \break ges } \\ >>
>>   }
>> }

> That's behaving as expected.  The properties in the default Voice are
> independent from the properties in Voice = "1" and Voice = "2".

My bad. Here's one that seems to work score-wide, in case anyone gets stuck
on it.

\version "2.18.2"

\score {
  { \break ges1~
    \break ges
(Continue reading)

Federico Bruni | 26 Jul 10:28 2015

lyluatex [Fwd: Re: Lilypond and LaTeX - margins]

Should this be added somewhere in the docs?
In the easier editing page of the website there's no section for this. 
I think that this chapter of Usage would be better:
http://lilypond.org/doc/v2.19/Documentation/usage/lilypond-output-in-other-programs

https://github.com/jperon/lyluatex/blob/master/README.en.md

---------- Messaggio inoltrato ----------

Da: Marc Hohl <marc <at> hohlart.de>
Oggetto: Re: Lilypond and LaTeX - margins
Data: Sat, 25 Jul 2015 21:43:27 +0200
A: lilypond-user <at> gnu.org

Am 25.07.2015 um 18:12 schrieb Víctor:
> On a separate subject, I'd like to recommend you to use lyluatex
> <https://github.com/jperon/lyluatex> instead of Lilypond-book. I've
> found it to be a cleaner way to work as it is a LuaLaTeX package
> (developed by the Gregorio team!) and not an engine.

That's interesting indeed - thanks for sharing!
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Simon Albrecht | 24 Jul 11:51 2015
Picon

Holidays

Hello list,

I’ll be mostly offline for the next two weeks and can’t take over my 
Tuesday’s and Wednesday’s shifts, unfortunately.
A very nice summer to all of you,

Simon

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Xavier Scheuer | 23 Jul 11:00 2015
Picon

Grace prevents \voiceOne when set at the same time

> I'm not top posting.

Hi,

I do not know if this was already reported (I did not find it in the
tracker).

\grace (and similar \acciaccatura etc.) prevents \voiceOne (and similar
\stemUp etc.) when they are both set at the same time.

I doubt such an issue would remain unreported for such a long time, so
probably either it is already in the tracker, either this issue is
a regression compared to an older version of LilyPond.

\version "2.18.0"

% Issue: grace prevents \voiceOne
\relative c'' {
  c1 \voiceOne \grace c8 c2 c2  % \voiceOne not activated
}

% Works: \voiceOne inserted before or after grace
\relative c'' {
  \voiceOne c1 \grace c8 c2 c2  % works (\voiceOne activated)
}

Cheers,
Xavier

--

-- 
(Continue reading)

markdblackwell | 23 Jul 01:02 2015
Picon

`Help Us' section duplicated

The first (front matter) page of the Contributor's Guide manual (version
2.19.23, in the second paragraph) refers people to a very important section,
'Help Us' located in another manual: the Web/General Information manual.

In the PDF version: `For more information about different jobs, see Section
“Help us” in General Information.'

In the HTML version: `For more information about different jobs, see _Help
us_.'

Its underlying HTML (reformatted for clarity) is:

However, currently the Contributor's Guide also incorporates a duplicate
copy of this 'Help us' subsection, plainly visible near the top of the
index. Its text exactly matches that in the Web/General Information manual,
and includes the same, detailed discussions of `Simple tasks' and `Advanced
tasks'.

The duplication extends all the way from:

    Help us/We need you!

down through:

    Bugfixes or new features: read Section “Programming work” in
Contributor’s Guide.

This, combined with referring the reader (as it turns out) to the same
content, yet in another manual, might somewhat confuse readers as to why.
(It did so, for me.)
(Continue reading)

markdblackwell | 23 Jul 00:46 2015
Picon

`Help Us' section

The first (front matter) page of the Contributor's Guide manual (version
2.19.23, in the second paragraph) refers people to a very important section,
'Help Us' located in another manual: the Web/General Information manual.

In the PDF version: `For more information about different jobs, see Section
“Help us” in General Information.'

In the HTML version: `For more information about different jobs, see _Help
us_.'

Its underlying HTML (reformatted for clarity) is:

However, currently the Contributor's Guide also incorporates a duplicate
copy of this 'Help us' subsection, plainly visible near the top of the
index. Its text exactly matches that in the Web/General Information manual,
and includes the same, detailed discussions of `Simple tasks' and `Advanced
tasks'.

The duplication extends all the way from:

    Help us/We need you!

down through:

    Bugfixes or new features: read Section “Programming work” in
Contributor’s Guide.

This, combined with referring the reader (as it turns out) to the same
content, yet in another manual, might somewhat confuse readers as to why.
(It did so, for me.)
(Continue reading)

Malte Meyn | 20 Jul 18:00 2015
Picon

StemTremolo collides with natural Accidental

> I'm not top posting.

Hello list,

for StemTremolos in short durations the length of a Stem is increased. But
it is not long enough when a natural Accidental is directly placed in front
of the note, so they collide:

\version "2.19.22"

{
  b'!2:16 % default stem length, doesn’t collide
  b'!2:32 % stem length increased but not enough
}

Flats don’t collide and the collision with sharps is very small but exists.

Malte
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Karol Majewski | 20 Jul 16:37 2015
Picon

Incorrect cropping with lilypond-book-preamble.ly

% With lilypond-book-preamble.ly included
% some scores are cropped incorrectly.
% Here, articulation mark (accent) is out of area.

\version "2.19.23"

\include "lilypond-book-preamble.ly"

one = {
  s8
}

two = {
  \voiceOne a16[ _> \change Staff = "one" \voiceTwo a'16]

}

\score {
  \new PianoStaff <<
    \new Staff = "one" \one
    \new Staff = "two" \two
  >>
}
to7m | 20 Jul 03:04 2015
Picon

Cross-system tied accidentals not hidden

% The 2nd system's accidental is correctly hidden, but the 4th system's is
% incorrectly present. The 6th system uses the workaround of placing the
% hide-tied-accidental-after-break bit in the voice. The direction of the
% ties is different too.

\version "2.18.2"

{ \override Accidental #'hide-tied-accidental-after-break = ##t
  { \break ges1~
    \break ges
    \break << { ges1~
    \break ges } \\ >>
    \break << { \override Accidental #'hide-tied-accidental-after-break =
##t ges1~
    \break ges } \\ >>
  }
}

Gmane