Dr. Tobias Quathamer | 25 Jun 14:45 2016
Picon

Better support of guile v2 in configure.ac

Hi,

I'm currently working on a Debian package of the current unstable
lilypond version. I suggest the following patch to configure.ac, similar
to the version check in STEPMAKE_GUILE_DEVEL a couple of lines above.
Without this patch, at least for me the build fails if guile-1.8 is not
available on the system.

Regards,
Tobias
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni | 23 Jun 13:36 2016

--include requires absolute paths

Should we say explicitly in the doc that -I or --include option 
requires absolute path(s)?
Paragraph to be modified is in Usage 1.2:

 -I, --include=directory

    Add directory to the search path for input files.

    Multiple -I options may be given. The search will start in the 
first defined directory, and if the file to be included is not found 
the search will continue in subsequent directories.

Perhaps a warning like "~ cannot be used, use absolute path" may be 
also helpful.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

$ ~/.local/bin/lilypond --include=~/Documenti/spartiti/ly 
Aggressive-Lady.ly
GNU LilyPond 2.19.43
Processing `Aggressive-Lady.ly'
Parsing...
Aggressive-Lady.ly:2:10: error: cannot find file: `myStyle.ly'
(search path: 
`/home/fede/.local/lilypond/usr/share/lilypond/current/fonts/svg/:/home/fede/.local/lilypond/usr/share/lilypond/current/fonts/type1/:/home/fede/.local/lilypond/usr/share/lilypond/current/fonts/otf/:/home/fede/.local/lilypond/usr/share/lilypond/current/scm:/home/fede/.local/lilypond/usr/share/lilypond/current/ps:/home/fede/.local/lilypond/usr/share/lilypond/current/ly:~/Documenti/spartiti/ly:')
\include
         "myStyle.ly"
Aggressive-Lady.ly:13:19: error: unknown escaped string: `\I'

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
(Continue reading)

Paul Hodges | 23 Jun 01:23 2016

Wrongly combined note heads

> I'm not top posting.

% Note heads in different voices are combined
% even though they have different accidentals

\version "2.19.42"
\language "english"

<<
  { g'4 gs'4 }
\\  
  { gs'4 g'4 }
>>

Result: https://cassland.org/images/PWH-wrongly-combined-noteheads.png
Ansgar | 21 Jun 12:23 2016
Picon
Picon

Wrong MIDI-output when notes of the same pitch appear in different voices


%In the first bar the MIDI-output is as desired.

%In the second bar, the first a'4 is changed to a'8 a'8. 
%The created PDF is fine.
%However, the MIDI-output cuts the following Note, a'2, down to a quater.
%I.e. it ends, where the a'2 from voiceTwo ends.

\score {
	\new Staff {

		
		<<	\new Voice{\voiceOne a'4 a'2 a'4}
			\new Voice {\voiceTwo a'2  f' }
		>>

		<<	\new Voice{\voiceOne a'8 a'8 a'2 a'4}
			\new Voice {\voiceTwo a'2  f' }
		>>

	}	
	\layout {}
	\midi {}
}

\version "2.19.42"
Malte Meyn | 19 Jun 10:30 2016
Picon

New scheme list/identifier syntax has undocumented side-effects

Hi list,

the German LilyPond forum discovered a side effect of the new identifier 
syntax: additional to

\version "2.19.40"
FOO = { c d e }
\FOO

there are now more cases where you cannot use a variable immediately 
after it’s definition:

\version "2.19.40"
FOO = "This is a markup"
\FOO
BAR = "test.ly"
\include \BAR

This comes from commit 2a66e23f3 and should be documented in the changes 
IMO because probably that’s nothing that convert-ly can handle.

Malte

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Andrew Bernard | 16 Jun 02:12 2016
Picon

Tuplet numbet text

When setting the tuplet number text, in a piece that uses the full fraction
throughout, when temporarily set to just the denominator on a nested
tuplet, if the nested tuplet comes first the out tuplet text is also set to
the inner setting. This does not occur if the inner tuplet comes later.

Is this indeed a bug?

Andrew

== snip

\version "2.19.43"

{
  \override TupletNumber.text = #tuplet-number::calc-fraction-text
  \tuplet 7/8 { c'' \tuplet 3/2 { d'' d'' d'' }  c'' c'' c'' c'' } |

  \tuplet 7/8 {
    \once \override TupletNumber.text =
#tuplet-number::calc-denominator-text
    \tuplet 3/2 { d'' d'' d'' }  c'' c'' c'' c'' c''
  } |

  \tuplet 7/8 {
    c''
    \once \override TupletNumber.text =
#tuplet-number::calc-denominator-text
    \tuplet 3/2 { d'' d'' d'' }  c'' c'' c'' c''
  } |
}
(Continue reading)

Dag Odenhall | 14 Jun 19:11 2016
Picon
Gravatar

musicxml2ly: AttributeError: PartGroupInfo instance has no attribute 'set_part_information'

Hello list,

I get this traceback trying to convert the Reunion demo score from
MuseScore:

musicxml2ly: Reading MusicXML from Reunion.xml ...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Converting to LilyPond expressions...
musicxml2ly: Converting to LilyPond expressions...
Traceback (most recent call last):
  File "/usr/bin/musicxml2ly", line 2986, in <module>
    main()
  File "/usr/bin/musicxml2ly", line 2981, in main
    voices = convert (filename, options)
  File "/usr/bin/musicxml2ly", line 2896, in convert
    update_score_setup (score, part_list, voices)
  File "/usr/bin/musicxml2ly", line 2794, in update_score_setup
    score_structure.set_part_information (part_id, staves_info)
  File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1941, in
set_part_information
    self.contents.set_part_information (part_id, staves_info)
  File "/usr/share/lilypond/2.19.43/python/musicexp.py", line 1780, in
set_part_information
    c.set_part_information (part_name, staves_info)
AttributeError: PartGroupInfo instance has no attribute
'set_part_information'

(Continue reading)

David Kastrup | 13 Jun 13:00 2016
Picon
Picon

Texinfo indexing


In my current Texinfo manual I read:

       For the printed output, you may specify an explicit sort key for an
    index entry using ' <at> sortas' immediately following the index command.
    For example: ' <at> findex  <at> sortas{\} \  <at> r{(literal \ in  <at> code{ <at>  <at> math})'
    sorts the index entry this produces under backslash.

       To reduce the quantity of sort keys you need to provide explicitly,
    you may choose to ignore certain characters in index entries for the
    purposes of sorting.  The characters that you can currently choose to
    ignore are '\', '-', '<' and ' <at> ', which are ignored by giving as an
    argument to the ' <at> set' command, respectively, 'txiindexbackslashignore',
    'txiindexhyphenignore', 'txiindexlessthanignore' and
    'txiindexatsignignore'.  For example, specifying ' <at> set
    txiindexbackslashignore' causes the '\mathopsup' entry in the index for
    this manual to be sorted as if it were 'mathopsup', so that it appears
    among the other entries beginning 'M'.

Now obviously this might _finally_ make it possible for us to clean up
indexing and have entries like \tweak sorted under "t" while the index
entry properly is '\tweak'.

I don't know to what degree the HTML index would be affected.  This
would require a reasonably recent version of Texinfo and/or texinfo.tex.
I believe that Gub is still stuck at version 4.something because of
efficiency considerations (Texinfo 4 is written in C rather than Perl
and thus faster).  This indexing issue, however, might well be a
reasonable incentive to bite the bullet and move to a current Texinfo
version.
(Continue reading)

Simon Albrecht | 12 Jun 13:44 2016
Picon

Failed assertion: script with neutral direction

Hello,

it would appear sensible for scripts to have neutral direction in a 
Dynamics context. However, it results in a failed assertion:

%%%%%%%%%%%%
\version "2.19.25"

\new Dynamics {
   s->
}

\layout {
   \context {
     \Dynamics
     \override Script.direction = 0
   }
}
%%%%%%%%%%%%

=>

lilypond:

/home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily/lily-guile.cc:157: 
scm_unused_struct* index_get_cell(SCM, Direction): Assertion `d' failed.

It works in 2.19.16 (or did it only seem to work?), but not from .25 onward.

Best, Simon
(Continue reading)

Hans Åberg | 11 Jun 23:55 2016
Picon

Lilypond 2.19.43 font issue

The code below produces, using lilypond-2.19.43-1.darwin-x86 on OS X 10.11.6, the diagnostic:
Finding the ideal number of pages...Fontconfig warning: ignoring UTF-8: not a valid region tag

And the title fonts becomes sans-serif. It happens also in 2.19.42, but not in 2.19.18.

\version "2.19.43"

music = {a}

\score {\music\layout{}}
Andrew Bernard | 11 Jun 04:28 2016
Picon

Parenthesized accent

When parenthesizing an accent on a cross staff note, the parentheses are
drawn incorrectly. Is this a bug?

Andrew

== snip

\version "2.19.42"

treble = {
  \clef treble
  \crossStaff { c''4-\parenthesize^> } c''
}

bass =  {
  \clef bass
  \stemDown
  c4 c
}

\score {

  \new PianoStaff
  <<
    \new Staff { \treble }
    \new Staff { \bass }
  >>
}

== snip
(Continue reading)


Gmane