Re: partcombine bug - missplaced rest

2013-10-15 Thread Eluze 
hi Karol

anyway - I've entered a new issue in the tracker - thanks for your report!
Eluze

https://code.google.com/p/lilypond/issues/detail?id=3612thanks=3612ts=1381827371



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/partcombine-bug-missplaced-rest-tp152312p152328.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Code from manual causes compilation warning

2013-10-15 Thread Ralph Palmer 
On Thu, Oct 3, 2013 at 5:49 PM, Urs Liska lilyli...@googlemail.com wrote:

 When following the Application Usage manual to use the '-e' command line
 option
 http://www.lilypond.org/doc/**v2.17/Documentation/usage/**
 command_002dline-usage.html#**basic-command-line-options-**for-lilypondhttp://www.lilypond.org/doc/v2.17/Documentation/usage/command_002dline-usage.html#basic-command-line-options-for-lilypond

 and writing

 #(use-modules (guile-user))


 at the beginning of the document I get the following

 WARNING: #f: imported module (guile-user) overrides core binding
 `%module-public-interface'

 It is identical with different versions between 2.16.2 and 2.17.27.

 Is this warning something to care about or can I ignore it?
 In any case I think following the documentation shouldn't result in such a
 warning.

 Does this point to an issue with the recommended practice?
 Is it a false alarm that can/should be suppressed/avoided?
 Should it at least be mentioned in the documentation?


Hi, Urs -

Thanks for the email. It has been submitted as Issue 3613 :
https://code.google.com/p/lilypond/issues/detail?id=3613

Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Bagpipe docs

2013-10-15 Thread Ralph Palmer 
On Mon, Oct 7, 2013 at 3:35 AM, Noeck noeck.marb...@gmx.de wrote:

 in this section of the manual (2.16 as well as 2.17):
 http://lilypond.org/doc/v2.16/Documentation/notation/bagpipes
 the first mentioned advantage of bagpipe.ly is that \taor is short for
 \grace { \small G32[ d G e] }

 But this line is no valid syntax without bagpipe.ly (due to the G).

 The meaning of pitches with bagpipe.ly should be explained before, not
 afterwards. (A more minimal correction would be to change this line to
 usual
 lilypond syntax using , and ' .)

 In addition, the commands of ly/bagpipe.ly should be explained, at least
 on
 of each type. Right now, the user needs to read bagpipe.ly to know the
 commands.


Thanks, Noeck. This has been submitted as Issue 3614 :
https://code.google.com/p/lilypond/issues/detail?id=3614

Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement: always print key signature grobs, even for keys with no sharps or flats

2013-10-15 Thread Ralph Palmer 
On Sat, Oct 12, 2013 at 11:58 AM, Paul Morris p...@paulwmorris.com wrote:

 Greetings bug squad,

 Say you want to override all key signature grobs, either to use a
 non-standard key signature system, or to enhance the traditional key
 signature system, as in this snippet:
 http://lsr.dsi.unimi.it/LSR/Item?id=856

 ...unfortunately, for keys with no sharps or flats like C major and A
 minor, LilyPond does not always give you a key signature grob to override.

 For these keys LilyPond *does* put an empty (invisible) key signature grob
 at the beginning of the first line of music, and also any time the key
 changes to a key with no sharps or flats.  However, LilyPond does *not*
 include an empty key signature grob at the beginning of any lines of music
 after the first.


Greetings, Paul Morris -

Thanks for the email. This has been submitted as Issue 3615 :
https://code.google.com/p/lilypond/issues/detail?id=3615

Ralph
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Too low stem-thickness while using high value for fontSize

2013-10-15 Thread Thomas Morley 
Hi,

writing some educational papers I tried the code below

\version 2.17.28

  {
\set fontSize = #12
\override Stem #'length = #24
%\override Stem #'thickness = #(magstep 6)
a'8
  }

  %% Only for better viewing:
  \layout {
  \omit Staff.TimeSignature
  \omit Staff.Clef
  \omit Staff.StaffSymbol
  }

Returning a far to low stem-thickness
Seems it is factored some way, only looking at
StaffSymbol.line-thickness, disregarding the general fontSize.
Workaround is uncommenting the Stem.thickness-override.
attachment: atest-22.png___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Enhancement: always print key signature grobs, even for keys with no sharps or flats

2013-10-15 Thread Paul Morris 
Ralph Palmer-3 wrote
 Thanks for the email. This has been submitted as Issue 3615 :
 https://code.google.com/p/lilypond/issues/detail?id=3615

Thanks!  I've attached the illustration files to the issue.
-Paul



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Enhancement-always-print-key-signature-grobs-even-for-keys-with-no-sharps-or-flats-tp152184p152363.html
Sent from the Bugs mailing list archive at Nabble.com.

___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond