James | 1 Oct 09:16 2014
Picon

Re: how to compile many .ly files with one command

On 30/09/14 22:04, lilypond-user-request <at> gnu.org wrote:>
>> > It works both on Windows and Linux. BTW. it should documented in
'1.2 Command-line usage', shouldn't it?
> It would not hurt to document it, but it is a basic functionality of the
> shell and not directly of LilyPond. You can do it with any program:
>
> ls *
> mv * ../otherdirectory/
>
> and so on. The functionality of LilyPond that contributes to this, is
> that the lilypond command accepts not only a single file but also a list
> of files.
> In this sense, you are right:
>
> 1. The documentation could tell the reader that multiple files are
possible.
>
> 2. As there is already a section that explains standard behaviour of the
> shell, the * file globbing [1] could be added there.
>
>
http://lilypond.org/doc/v2.18/Documentation/usage/command_002dline-usage.html#invoking-lilypond
>
> Cheers,
> Joram

Good idea!

http://code.google.com/p/lilypond/issues/detail?id=4147

(Continue reading)

Malte Meyn | 30 Sep 11:48 2014
Picon

Please add German documentation reference on arpeggio brackets with connectArpeggios.

> I'm not top posting.

The English documentation writes
“The simple way of setting parenthesis-style arpeggio brackets does not work
for cross-staff arpeggios; see Cross-staff stems.”

This reference to the section about cross-staff stems isn’t present in the
German notation reference:
“Die Arpeggios im Klammer-Stil funktionieren nicht über mehrere Notensysteme.”
This sounds like “it isn’t possible at all” to me so I first didn’t even try
to find a solution ;)

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Dan Eble | 30 Sep 02:32 2014
Picon

implicitTimeSignatureVisibility

>I'm not top posting.
% I'm not sure if this is a defect in functionality, nomenclature,
% documentation, or all three.
% 
% It is not clear what is "implicit" about
% "implicitTimeSignatureVisibility", since it has the same effect
% whether the time signature is omitted or specified.
%
% The notation reference says that "implicitTimeSignatureVisibility"
% is "break visibility for the default time signature", yet it has the
% same effect whether the time signature is the default 4/4 or
% something else.
%
% What it does appear to do is control the visibility of the first
% time signature.
\version "2.19.14"

\score {
  \relative { c'1^"Default, Implicit (Visible)" }
}

\score {
  \relative {
    \set Score.implicitTimeSignatureVisibility = #all-invisible
    c'1^"Default, Implicit"
  }
}

\score {
  \relative { 
(Continue reading)

Stu McKenzie | 29 Sep 21:36 2014
Picon

DrumStaff.drumStyleTable is not applied to (acciaccatura) grace notes

> I'm not top posting.

\version "2.18.0"

% DrumStaff.drumStyleTable is not applied to
% (acciaccatura) grace notes if the grace notes
% are the first notes in a score.
%
% Also, the stem direction of the first grace notes
% does not comply with the "voiceOne" direction
% This can be forced to comply by adding "\stemDown".

#(define mydrums '(
  (hihat cross #f 5)
))

CymbalsA = \drummode {
% \stemDown   % force stem direction
% These grace notes are placed in the default position
  \acciaccatura { hh16[ hh] } hh8
% These grace notes are placed in the new style's position
  \acciaccatura { hh16[ hh] } hh8
  r4 r2
}

\score {
  \new DrumStaff <<
    \set DrumStaff.drumStyleTable = #(alist->hash-table mydrums)
    \new DrumVoice { \voiceOne \CymbalsA }
  >>
(Continue reading)

Simon Albrecht | 29 Sep 19:33 2014
Picon

LSR 265

Hello,

I find the current coding of LSR snippet 265 leaves much room for 
improvement, especially by using \set stanza for the braces and the more 
convenient commands \left-brace and  \right-brace.
Attached is my new version. I hope you like it ;-)

Best, Simon
Attachment (lsr265.ly): text/lilypond-source, 879 bytes
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Malte Meyn | 29 Sep 18:00 2014
Picon

Cross staff stems don’t work with shifted notes

> I'm not top posting.

The following won’t shift the C (or the A) horizontally and connect the
stems of G and C.

\version "2.19.13"

\new PianoStaff \with {
  \consists #Span_stem_engraver
}
<<
  <<
    a'
    \\
    \crossStaff g' %change this to f' and it will work
  >>
  c''
>>

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Urs Liska | 29 Sep 14:49 2014

Ugly collision between dynamics and crossStaff stem

Hi bug-squad,

attached you'll find source and image of an ugly collision between 
dynamics and a cross-staff stem.
The image is from current master but the issue is the same with 2.18.2.

Thanks for adding an issue report.

Urs
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Pierre Perol-Schneider | 29 Sep 11:15 2014
Picon

4th finger moves slur

>I'm not top posting.

Hi Squad,

See how the third slur is misplaced here :

\version "2.19.15"

{
  \key a\major
  \clef "G_8"
 <<
    {
      | % mes.9
          <cis''-2>8*2/3( <d''-3> <cis''-2>) <b'-2>( <cis''-4> <b'-2>)
          <a'-2> %-\tweak color #red
          % here's the problem with 4th finger :
          (<b'-4> %% other fingering works fine.
          <a'-2>) <gis'-2>( <a'-3> <gis'-2>)
    }
    \\
    {
      | % mes.9
          a,2 <cis-1>
    }
  >>
}

\layout {
  \context {
(Continue reading)

James | 27 Sep 17:12 2014
Picon

Fwd: Re: Composer not right-aligned


-------- Forwarded Message --------
Subject: Re: Composer not right-aligned
Date: Sat, 27 Sep 2014 17:12:01 +0200
From: Aurélien Bello <pub <at> aurelienbello.com>
To: James <pkx166h <at> gmail.com>

Hi James,
thanks for your answer.
I’m using 2.19.14 und I saw that the bug is already known and will be
corrected in 2.19.15.
Sorry!
Thanks,
Greetings
Aurélien

Le 27 sept. 2014 à 16:19, James <pkx166h <at> gmail.com> a écrit :

> On 27/09/14 10:49, Aurélien Bello wrote:
>> Composer's name ist not right-aligned, but under the title.
>> It only gets normal if you specify a poet and an instrument as well.
>> 
>> 
>> _______________________________________________
>> bug-lilypond mailing list
>> bug-lilypond <at> gnu.org
>> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>> 
> 
> which version are you using?
(Continue reading)

Aurélien Bello | 27 Sep 11:49 2014

Composer not right-aligned

Composer's name ist not right-aligned, but under the title.
It only gets normal if you specify a poet and an instrument as well.
Martin Tarenskeen | 22 Sep 10:03 2014
Picon

misplaced composer field


Hi,

Using Lilypond 2.19.14 I see the "composer" field is completely misplaced 
in the output.

%%%% short example showing misplaced composer field %%%%

\version "2.19.14"

\header {
   title = "title"
   subtitle = "subtitle"
   poet = "poet"
   meter = "meter"
   piece = "piece"
   composer = "composer"
   arranger = "arranger"
   opus = "opus"
}

\score {
   \new Staff {
     { s1 }
   }
   \layout {}
}

(Continue reading)


Gmane