Andrew Bernard | 26 May 11:52 2016
Picon

Beaming and slurs across staves

I keep finding situations using beamed groups across staves where
adding a slur or a phrasing slur causes lilypond to fail with the
following error:

Processing `/home/andro/work/lilypond/fp/exp-slur-crash.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
/home/andro/work/lilypond/fp/exp-slur-crash.ly:15:6: warning: no
viable initial configuration found: may not find good beam slope
c32
[\( c
lilypond: /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
T Interval_t::center() const [with T = double]: Assertion `!is_empty
()' failed.

Refer to the MWE here for an example. This occurs in 2.19.41 at least.
I have not tried previous versions.

In other scenarios in my score even when the warning about not finding
a good beam slope is not emitted I still get the crash reliably in
this type of situation.

Is this a bug?

Andrew

(Continue reading)

Dan Eble | 26 May 06:47 2016
Picon

harmonicNote

The NR has this:

> harmonicNote [music] - note (music)
> Print note with a diamond-shaped note head. 

Does \harmonicNote c4 do more than c4\harmonic?  If so, it would be nice to document what.  If not, perhaps
convert-ly could replace it out of existence.

If a documentation update is undertaken, this related note seems to be untrue:

> Note: \harmonic must be placed inside a chord construct even if there is only a single note.
— 
Dan

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Stefan-W. Hahn | 25 May 17:43 2016
Picon

Importing the ToC into LaTeX

Example of importing toc not working.
Getting following error:

Compiling /home/hs/doc/weihnachtslieder.git/out/book.tex...
Writing `/home/hs/doc/weihnachtslieder.git/out/book.tex'...
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian)
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./book.tex
LaTeX2e <2016/02/01>
Babel <3.9q> and hyphenation patterns for 8 language(s) loaded.
(/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/bk11.clo))
(/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty
(/usr/share/texlive/texmf-dist/tex/latex/base/utf8.def
(/usr/share/texlive/texmf-dist/tex/latex/base/t1enc.dfu)
(/usr/share/texlive/texmf-dist/tex/latex/base/ot1enc.dfu)
(/usr/share/texlive/texmf-dist/tex/latex/base/omsenc.dfu)))
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty
(/usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf
(/usr/share/texlive/texmf-dist/tex/generic/babel/babel.def))
(/usr/share/texlive/texmf-dist/tex/generic/babel-german/ngerman.ldf
(/usr/share/texlive/texmf-dist/tex/generic/babel-german/ngermanb.ldf)))
(/usr/share/texmf/tex/latex/lm/lmodern.sty)
(/usr/share/texlive/texmf-dist/tex/latex/nopageno/nopageno.sty)
(/usr/share/texlive/texmf-dist/tex/latex/pdfpages/pdfpages.sty
(Continue reading)

Johannes Feulner | 25 May 15:01 2016

Ghostscript crashes on Japanese characters on Ubuntu 16.04

I installed lilypond 2.18.2 on a freshly installed Ubuntu Desktop 16.04
64 Bit.

Ghostscript crashes when compiling the following input:

    \version "2.12.0"

    \markup { \column {
         "First line"
          "Japanese: 日本語のページを検索"
         "Last line"
       }
    }

See lilypond's debug output below.

The culprit seems to be the font
/usr/share/fonts/opentype/noto/NotoSansCJK-Regular.ttc
Here the offending font can be downloaded:
https://www.dropbox.com/s/vj7bxwyb38u2u6b/noto.zip?dl=0

After deleting the the noto font (rm -r
/usr/share/fonts/opentype/noto/), everything works fine.

The font noto was not part of ubuntu Desktop 14.04 64 Bit, I've checked
that.

I have no idea, what might be wrong with this font, ghostscript or
lilypond. However, deleting the font is a workaround.

(Continue reading)

Ansgar | 24 May 23:35 2016
Picon
Picon

addlyrics does not work with an ossia staff

If the overall value of the second staff exhaustes the length of the part
above the following parts are spoiled:

%-----------------------
% This one works, but the added staff has only notes of value 1/2  
%-----------------------

\new Staff \relative c' 

{ e4 e e e

	<<	
		{ e2 e  }
		\new Staff { c2  }
		\addlyrics{ Ooops! } 
	>>

{d4 d d d  }

}

%-----------------------
% Now an r is added after the c2 and that spoils the following parts
%-----------------------

\new Staff \relative c' 

{ e4 e e e

	<<	
(Continue reading)

Federico Bruni | 23 May 18:10 2016

verifying issues and copy&paste problems with Firefox

I just want to share with the few persons who verify the issues that I 
just realized why gitk did not work for me recently.
When I copy a committish using Firefox, the committish seems perfectly 
selected, but actually it includes an initial space; so gitk considers 
invalid the committish. What is bad about gitk: you cannot go up and 
delete the space.

So gitk is not a good choice if you use Firefox.

A nice alternative, for those who use a recent (at least 3.18) Gnome 
desktop, is gitg, which allows to delete the space after the paste.
https://wiki.gnome.org/Apps/Gitg/
Dan Eble | 22 May 00:20 2016
Picon

Tied harmonics

%% Harmonic does not carry through a tie.
\version "2.19.42"
{ <f'\harmonic> ~ 4 }
— 
Dan

_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Federico Bruni | 20 May 10:34 2016

patch labels in CG manual

Hi

I have a few questions about the section "Patch label" in:
http://lilypond.org/doc/v2.19/Documentation/contributor/issue-classification

> Patch-new: the patch has not been checked for “obvious” mistakes. 
> When in doubt, use this tag.
> Patch-review: the patch has no “obvious” mistakes (as checked by 
> the Patch Meister), and is ready for review from main developers.
> 
> Developers with git push ability can use this category, skipping over 
> patch-new.

Recently I've followed this guide and used Patch-review immediately 
after uploading the patch, because I thought this would have saved 
manual work to James.

But I've just learned from Phil that if I skip immediately to 
Patch-review the tests won't run¹. This is confirmed by this chapter:
http://lilypond.org/doc/v2.19/Documentation/contributor/the-patch-review-cycle

I can't remember if Patchy still does (after the move to 
Allura/Sourceforge) what's described there.
Anyway, I would add a link to the-patch-review-cycle from 
issue-classification#patch-label section and I would change the above 
paragraph to say that automatic tests are run when an issue is set to 
Patch-new.

¹ https://sourceforge.net/p/testlilyissues/issues/4857/

(Continue reading)

dtsmarin | 18 May 21:33 2016
Picon

Wrong Tuplet Bracket Placement

Hi,
According to E.Gould the bracket should extend from the left edge of the
first notehead or rest to the right edge of the final notehead or rest. In
Lilypond it extends only from the first stem to the last one.

Well it's not a bug but I want to know why the developers chose this option
rather than following Gould's rule. Please fix this, or at least make it
possible to choose between the default and the recommended here.

Best,
Dimitris

--
View this message in context: http://lilypond.1069038.n5.nabble.com/Wrong-Tuplet-Bracket-Placement-tp190749.html
Sent from the Bugs mailing list archive at Nabble.com.
Urs Liska | 17 May 05:47 2016
Gravatar

Changed behaviour of point-and-click

As reported by Mark Knoop in
http://lists.gnu.org/archive/html/bug-lilypond/2016-05/msg00005.html
this commit

commit f30a8189adbbeefa2103e2c2e194040f66bc2291
Author: Urs Liska <ul <at> openlilylib.org>
Date:   Tue Jan 19 10:52:33 2016 +0100

    #4747: Remove (all) uses of is-absolute?

    The check for absolute paths in  in output-ps.scm
    and -svg.scm is unnecessary because
    (car ly:input-file-line-char-column a-location)
    always returns an absolute, slashified path

    Now is-absolute? is not used anymore by LilyPond itself.

has the side-effect of affecting the point-and-click links. If the file
path passed to LilyPond is relative the point-and-click links are
relative as well.

Of course this is an unwanted side-effect of my patch, but I would like
to discuss if this is a feature rather than a bug.

It has been brought up more than once that having full paths in the
point-and-click links *might* be considered a security issue. And much
more important, having relative point-and-click links would make the
files more portable: if you send someone a zip file with .ly and .pdf
files in it relative links would work right out-of-the-box, without
prior compilation. Or if you move/rename a working tree on your computer
(Continue reading)

Thomas Spuhler | 15 May 19:49 2016

lilypond-2.19.41-1.documentation.tar.bz2 file missing

http://lilypond.org/download/binaries/documentation/lilypond-2.19.41-1.documentation.tar.bz2 
returns a 
404 Not found
Is the link provided on the web site wrong?

--

-- 
Best regards
Thomas Spuhler

All of my e-mails have a valid digital signature
ID 60114E63
_______________________________________________
bug-lilypond mailing list
bug-lilypond <at> gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Gmane