(no subject)
http://bit.ly/a3gyBD ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1244 in lilypond: Change to the new website
Comment #4 on issue 1244 by percival.music.ca: Change to the new website
http://code.google.com/p/lilypond/issues/detail?id=1244
By "the top-level menu", do you mean the box that says "Note: these are
unstable development... we urge you to use the stable _Download_, and read
the stable _manuals_" ?
I'm not opposed to highlighting the "stable" part... evidently there's some
confusion over this, and the extra clarity wouldn't hurt anything. Come to
think of it, at the very least we should include the "stable" in the link.
I'll do this tomorrow noon if nobody does it before me. (i.e.
@ref{Download, stable download})
... but as I re-read your message, I'm starting to doubt myself. What do
you mean by "menu item" ? Is there some weird CSS thing happening with
your version of IE?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1244 in lilypond: Change to the new website
Comment #3 on issue 1244 by tdanielsmusic: Change to the new website http://code.google.com/p/lilypond/issues/detail?id=1244 On the development page, http://lilypond.org/development.html, if I want to download the latest development version for Windows there are two potentially promising clickable links: one off the bottom of the visible page in the Download panel and one labelled Download in the top-level menu. The panel link works as advertised, but the more obvious "Download" menu item brings up the download page for the stable release. This button should either be disabled on this page, labelled "Stable" or simply do nothing. The situation with Manuals is even worse, with the development manuals way off the bottom of the page. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Comment #4 on issue 1269 by tdanielsmusic: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 We don't add bugs which are in the tracker to @knownissues unless they are marked postponed. There are too many of them, and it would be wasted efort if they are quickly fixed. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 815 in lilypond: Enhancement: AJAX-powered search auto-completion for the online documentation
Comment #14 on issue 815 by v.villenave: Enhancement: AJAX-powered search auto-completion for the online documentation http://code.google.com/p/lilypond/issues/detail?id=815 OK, I'm opening Issue 1270 about that. (Were it up to me, I'd reopen this one instead, but Graham does have precious hair.) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1270 in lilypond: AJAX-powered search on the official online docs.
Status: Accepted Owner: v.villenave Labels: Type-Other Priority-Low Usability website New issue 1270 by v.villenave: AJAX-powered search on the official online docs. http://code.google.com/p/lilypond/issues/detail?id=1270 Reinhold has implented AJAX-powered search: see Issue 815. However, we still have to make sure that it is safe enough to be enabled on the official lilypond.org website. It has been tested for a couple of years, with a relatively low traffic, on Reinhold's server. Lilynet could be another place were we could test it more thoroughly. Anyhow, we need solid data. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Comment #3 on issue 1269 by percival.music.ca: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 Yes, but an undocumented new feature is not a Critical issue. :) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Comment #2 on issue 1269 by brownian.box: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 Shouldn't any new feature be documented? Ok, i'm fine with Medium actually :-) Sorry. I messed something, again, probably. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
(no subject)
http://qomuxodu.t35.com/ ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1231 in lilypond: New clefs collide with compressed multimeasure rests
Updates: Status: Verified Comment #5 on issue 1231 by PhilEHolmes: New clefs collide with compressed multimeasure rests http://code.google.com/p/lilypond/issues/detail?id=1231 Checked on the regtests (the regtest has been altered to test this, I believe) and shown good. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1263 in lilypond: MetronomeMark can not be aligned on note if MMR in another voice
Comment #6 on issue 1263 by brownian.box: MetronomeMark can not be aligned on note if MMR in another voice http://code.google.com/p/lilypond/issues/detail?id=1263 I'm quite fine with Medium, of course. From user's perspective: if something (aligning MM over notehead) became impossible... .) Neil, thank you for your workaround :-) Yes, i knew that nothing is impossible with lilypond! I waited for some feedback actually (Carl, thank you). I've just reported another one, issue 1269 and marked it as critical. Hope it'll be easy to fix. I'm sorry, i'm far away from stable internet access these days. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Updates: Labels: -Priority-Critical Priority-Medium Comment #1 on issue 1269 by percival.music.ca: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 Why is this Critical? It's not something that worked deliberately in the past, so it's not Critical. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1269 in lilypond: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented
Status: Accepted Owner: Labels: Type-Documentation Priority-Critical New issue 1269 by brownian.box: Doc: using #'non-break-align-symbols = #'() to align MetronomeMark should be documented http://code.google.com/p/lilypond/issues/detail?id=1269 Issue 1263 should be mentioned as "known issue" in the manual and workaround should be documented. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1244 in lilypond: Change to the new website
Comment #2 on issue 1244 by percival.music.ca: Change to the new website http://code.google.com/p/lilypond/issues/detail?id=1244 New website is "live" now. At first glance, I think I've done everything, but I'm not marking this fixed yet because I want to double-check when I'm more alert. If anybody else wants to check stuff and report problems, by all means do so. :) ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1173 in lilypond: LilyPond crash when using showFirstLength/showLastLength with \compressFullBarRests
Comment #9 on issue 1173 by percival.music.ca: LilyPond crash when using showFirstLength/showLastLength with \compressFullBarRests http://code.google.com/p/lilypond/issues/detail?id=1173 slight correction: I'm going ahead with the alpha test now, and then I'm switching web. So rather: this is the last critical issue remaining before we can have a release candidate and begin the two-week waiting period. I'll send an explanation of the current release process plan to -devel once .34 is uploaded; I will accept objections and possibly modify the plans. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
lilypond-book safe mode
Dear list,
This is a feature request for a safe mode for lilypond-book.
One can run lilypond with the -dsafe switch to avoid a security risk
when compiling .ly files including evil scheme code. There is no
equivalent switch for lilypond-book, and using --process leads to errors.
I'll post below a simple example.
Thanks,
Julien
---
$ cat docu.lytex
\documentclass{article}
\begin{document}
\begin{lilypond}
{c' d' e'}
\end{lilypond}
\end{document}
$ lilypond-book --process="lilypond -dsafe -dbackend=eps" docu.lytex
lilypond-book (GNU LilyPond) 2.12.3
Reading docu.lytex...
Running latex...This is pdfTeX, Version 3.1415926-1.40.10 (TeX Live
2009/Debian)
restricted \write18 enabled.
entering extended mode
(/tmp/tmpgwVO1K.tex
LaTeX2e <2009/09/24>
Babel and hyphenation patterns for english, usenglishmax,
dumylang, noh
yphenation, french, basque, ngerman, german, german-x-2009-06-19,
ngerman-x-200
9-06-19, ukenglish, loaded.
(/usr/share/texmf-texlive/tex/latex/base/article.cls
Document Class: article 2007/10/19 v1.4h Standard LaTeX document class
(/usr/share/texmf-texlive/tex/latex/base/size10.clo))
No file tmpgwVO1K.aux.
textwidth=345.0pt
columnsep=10.0pt
(./tmpgwVO1K.aux) )
No pages of output.
Transcript written on tmpgwVO1K.log.
Dissecting...
Writing snippets...
Processing...
Running lilypond...GNU LilyPond 2.12.3
Processing `/scratch/examples/Test/snippet-map--1168004333.ly'
Parsing...
/scratch/examples/Test/snippet-map--1168004333.ly:4:1: error: GUILE
signaled an error for the expression beginning here
#
(ly:add-file-name-alist '(("d6/lily-79fd5fcc.ly" . "docu.lytex")
Unbound variable: ly:add-file-name-alist
/scratch/examples/Test/snippet-map--1168004333.ly:0: warning: no
\version statement found, please add
\version "2.12.3"
for future compatibility
Processing `/scratch/examples/Test/d6/lily-79fd5fcc.ly'
Parsing...
/scratch/examples/Test/d6/lily-79fd5fcc.ly:3:9: error: include files are
not allowed in safe mode
\include
"lilypond-book-preamble.ly"
/scratch/examples/Test/d6/lily-79fd5fcc.ly:13:3: error: GUILE signaled
an error for the expression beginning here
#
(define dump-extents #t)
Wrong type argument in position 1: #40) (column . 7) (filename .
"/usr/share/lilypond/2.12.3/ly/music-functions-init.ly"))>
/scratch/examples/Test/d6/lily-79fd5fcc.ly:17:22: error: GUILE signaled
an error for the expression beginning here
force-assignment = #
""
Wrong type argument in position 1: #40) (column . 7) (filename .
"/usr/share/lilypond/2.12.3/ly/music-functions-init.ly"))>
/scratch/examples/Test/d6/lily-79fd5fcc.ly:18:16: error: GUILE signaled
an error for the expression beginning here
line-width = #
(- line-width (* mm 3.00))
Wrong type argument in position 1: #40) (column . 7) (filename .
"/usr/share/lilypond/2.12.3/ly/music-functions-init.ly"))>
/scratch/examples/Test/d6/lily-79fd5fcc.ly:0: warning: no \version
statement found, please add
\version "2.12.3"
for future compatibility
Interpreting music...
Preprocessing graphical
objects.../usr/share/lilypond/2.12.3/scm/titling.scm:9:34: In procedure
ly:paper-get-number in expression (ly:paper-get-number layout (quote
line-width)):
/usr/share/lilypond/2.12.3/scm/titling.scm:9:34: Wrong type (expecting
real number): #
command failed: lilypond -dsafe -dbackend=eps -I
"/scratch/examples/Test" --formats=eps -deps-box-padding=3.00
-dread-file-list -dno-strip-output-dir
"/scratch/examples/Test/snippet-names--1168004333.ly"
Child returned 1
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
\displayMusic does not properly quote cons lilypond properties
I'm trying to get the \displayMusic for the following:
c1^\markup {
\caps \center-align
\override #'(box-padding . 0.5)
\box "V. S."}
It results, partially, in this:
(markup
#:line
(#:caps
(#:center-align
(#:override (box-padding . 0.5) (#:box "V. S."
Note that
(box-padding . 0.5)
should be
'(box-padding . 0.5)
I believe this is a bug.
Thank you. Let me know if there's anything else I can do.
PS. Thanks to Carl Sorensen for helping me discover this.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
