Kieren MacMillan wrote:
Hi Rune,
I don't understand what you mean - we already list the default
values today:
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-internals/
Clef
Okay then... without looking anywhere except that page, tell me the
default setting(s) for Clef
Hi Mats,
This discussion is getting more and more confused.
Sorry... that comes from
(a) not really knowing the internal workings of Lilypond as well
as I probably should; and,
(b) putting my 2 cents in while simultaneously doing 42 other
things...
=\
- The list for each grob
On 9/11/07, Mats Bengtsson [EMAIL PROTECTED] wrote:
Trevor Bača wrote:
Criterion 1: There's a *complete* enumeration of acceptable values for
each property, and
Criterion 2: There's a working, one-line example of each value for
each property of each grob
I guess you haven't
a
webpage that links to the regression checks and the comparisons. Link
to it from... well, wherever you want. Probably either devel/ or
devel/participating.
devel/participating/ looks like the right place. We should also move
there comparison links from documentation.
Advanced users
John Mandereau wrote:
Le mardi 11 septembre 2007 à 13:15 -0700, Graham Percival a écrit :
Please make a
webpage that links to the regression checks and the comparisons. Link
to it from... well, wherever you want. Probably either devel/ or
devel/participating.
devel/participating/ looks
2007/9/11, Rune Zedeler [EMAIL PROTECTED]:
Possibly... but an *automated* page -- containing a listing exactly as
Trevor outlined BUT WITH ONLY THE DEFAULT SETTING/VALUE -- would keep up
*precisely* with development, since it would be scripted into the main
compilation process.
Yep
Hi all,
Han-Wen Nienhuys wrote:
listing default values is easy
This is actually pretty hard.
Okay... EOT for me.
If -- as Mats suggested -- we might (easily) print out the settable
*properties* (without values) on a single page, that would be fantastic.
Cheers,
Kieren.
Hi Joe,
I'm not sure this has to deal with your patch about insane spring
constant, but latest make web chokes on /input/regression/beam-quarter.ly.
Latest logs are:
Traitement de «
/home/jcharles/GIT/Fabrik/input/regression/out-www/lily-c89d90d97c.ly
Joe,
I'm not sure this has to deal with your patch about insane spring
constant, but latest make web chokes on /input/regression/beam-quarter.ly.
Latest logs are:
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
lilypond
To any developers,
If you add a new feature but don't feel like writing an entry for the
manual (or the feature is too small to merit such an entry), please
consider adding a small file to input/tolsr/ . You should probably
still add something to input/regression/ , but now that directory
Hi Joe,
good to have a x-staff tuplet example. Can you also add a docstring to
the example, ie
\header { texidoc = ... }
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
I'm currently removing all see also links to input/regression/*.ly
from the docs. These files will be categorized (or directorized),
placed in LSR, and will appear in the new Snippets infrastructure.
The relevant doc pages in the manual will point to the appropriate
directory.
Please don't
Joe Neeman escreveu:
This is with latest git:
$ ./out/bin/lilypond input/regression/lyric-extender-no-heads.ly
http://extender-no-heads.ly
GNU LilyPond 2.11.10
Processing `input/regression/lyric- extender-no-heads.ly
http://extender-no-heads.ly'
Parsing...
Interpreting music... [1
This is with latest git:
$ ./out/bin/lilypond input/regression/lyric-extender-no-heads.ly
GNU LilyPond 2.11.10
Processing `input/regression/lyric-extender-no-heads.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...Segmentation fault (core dumped
Erik,
I think it was you who've changed the tuplet implementation. Please
look at this regression report:
http://code.google.com/p/lilypond/issues/detail?id=159
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http
Erik Sandberg [EMAIL PROTECTED] writes:
On Saturday 23 September 2006 17:49, Nicolas Sceaux wrote:
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
/**
testFunction =
#(define-music-function (parser location) ()
On Tuesday 26 September 2006 23:54, Han-Wen Nienhuys wrote:
Erik Sandberg schreef:
Hi,
You should use ly:clone-parser to avoid this problem:
#(define-music-function (parser location) ()
(ly:parser-parse-string (ly:clone-parser parser) \\include
\test-data.ly\)
(make-music
Erik Sandberg schreef:
The new thing now is that also 0-ary functions are subject to the same
problem: We need to read an extra token to see whether an EXPECT_XXX comes.
If you like, I can fix this particular case by adding a special token for
0-ary functions (but this will not fix the
On Saturday 23 September 2006 17:49, Nicolas Sceaux wrote:
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
/**
testFunction =
#(define-music-function (parser location) ()
;; test-data.ly contains music variable
Erik Sandberg schreef:
On Saturday 23 September 2006 17:49, Nicolas Sceaux wrote:
Hi,
Using LilyPond from CVS, the following snippet causes a syntax error,
which 2.9.18 did not:
/**
testFunction =
#(define-music-function (parser location) ()
;; test-data.ly
If one of the official regression tests is broken (such as
input/regression/metronome-marking.ly
in 2.9.18)
should I file the bug in the google issue tracker, or just send an email
to bug- ?
- Graham
___
lilypond-devel mailing list
lilypond-devel
Graham Percival schreef:
If one of the official regression tests is broken (such as
input/regression/metronome-marking.ly
in 2.9.18)
should I file the bug in the google issue tracker, or just send an email
to bug- ?
issue tracker. Simply a report with the file name will do.
--
Han-Wen
Han-Wen Nienhuys wrote:
Graham Percival schreef:
If one of the official regression tests is broken (such as
input/regression/metronome-marking.ly
in 2.9.18)
should I file the bug in the google issue tracker, or just send an
email to bug- ?
issue tracker. Simply a report with the file name
On Fri, 2006-07-21 at 11:44 +, Han-Wen Nienhuys wrote:
CVSROOT: /cvsroot/lilypond
Module name: lilypond
Changes by: Han-Wen Nienhuys hanwen 06/07/21 11:44:59
snip
Log message:
* scm/output-lib.scm (grace-spacing::calc-shortest-duration): new
function.
- Original Message -
From: Graham Percival [EMAIL PROTECTED]
To: Eduardo Vieira [EMAIL PROTECTED]
Cc: lilypond-devel@gnu.org
Sent: Wednesday, April 26, 2006 8:06 AM
Subject: Re: Regression Tests: lyric-combine-polyphonic.ly
Thanks! I think the lyrics are supposed to be placed
Hello developers,
I noticed that the example lyric-combine-polyphonic.ly doesn't display the
lyrics: Do mi nus ex. In order to show them, the line with \lyricsto needs
to be placed below \new Voice as in the example below:
\layout { ragged-right = ##t}
{
\clef violin
\time 8/8
Han-Wen Nienhuys writes:
A lot of them don't test typography, but other aspects of Lily. If we
change the name in any direction, I would recommend simply renaming it
to test
I do not see what we gain by removing `regression'; I think regression
test is a good name.
To clarify: a test
Hi!
Is there some reason for using term regression tests? There is a more
accurate term proofs which is used in typography.
If the latter term is preferred, I would cultivate it in several places
in the Documentation.
Greetings,
Heikki Junes
Hi!
Is there some reason for using term regression tests? There is a more
accurate and shorter term proofs which is used in typographical contex.
If the latter term is preferred, I would cultivate it in several places
in the Documentation.
Greetings,
Heikki Junes
Heikki Johannes Junes wrote:
Hi!
Is there some reason for using term regression tests? There is a more
accurate term proofs which is used in typography.
A lot of them don't test typography, but other aspects of Lily. If we
change the name in any direction, I would recommend simply
On Wed, 22 Feb 2006, Erik Sandberg wrote:
Hi Juergen,
IIRC, mensural notation is contributed supported by you. A regression test
is broken:
There seem to be some problems with regression/mensural-ligatures.ly. At least
two problems exist:
- Dots are handled incorrectly.
- Notes take up too
On Wednesday 22 February 2006 12.58, Juergen Reuter wrote:
Mensural notation has always been and still is in a highly experimental
state (and I think I once explicitly stated it exactly that way somewhere
in the documentation). I am sorry, but I fear I can not really help on
these issues, at
Hi Juergen,
IIRC, mensural notation is contributed supported by you. A regression test
is broken:
There seem to be some problems with regression/mensural-ligatures.ly. At least
two problems exist:
- Dots are handled incorrectly.
- Notes take up too much horizontal space.
- lily spits out tons
+++ lilypond/ChangeLog Thu Aug 18 13:43:05 2005
@@ -1,5 +1,7 @@
2005-08-18 Han-Wen Nienhuys [EMAIL PROTECTED]
+ * input/regression/*.ly: remove superfluous \score blocks. Reindent.
Are you sure about this one?
I actually question if it was a good idea to make the \score{...}
optional. It may
- Original Message -
From: Han-Wen Nienhuys [EMAIL PROTECTED]
To: Mats Bengtsson [EMAIL PROTECTED]
Cc: lilypond-devel@gnu.org
Sent: Thursday, August 18, 2005 10:15 AM
Subject: Re: The optional \score? was: lilypond
./ChangeLoginput/regression/accidenta...
Mats Bengtsson wrote
On 2-Jul-05, at 12:53 AM, Matevz Jekovec wrote:
http://lilypond.org/doc/v2.6/Documentation/user/out-www/lilypond/
source/input/regression/out-www/lily-52311572.ly
In 3rd and 6th measure, noteheads in first voice collide with rests in
the second.
Thanks for the report. For the record
hi
Here are a piece of documentation for #{ ... #} syntax, a
regression test for it, and a patch for ly-from-scheme.scm.
Is the doc OK? May I commit it?
Index: Documentation/user/programming-interface.itely
===
RCS file: /cvsroot
A rest seems to be missing in this regression test.
--
Heikki Junes
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
The accidentals are not deal the right way in the case of
quarter-accidentals. This can be seen in two files:
input/regression/key-signature-scordatura.ly
1) signature eih, no natural sign for e
2) signature gis+eeh, no natural sign for e and g
input/regression/keys.ly
1
[EMAIL PROTECTED] writes:
After the last header file (I checked it was alphabetically the last file
in .../regression/ -directory) compiling stopped:
make: *** [web-doc] Error 2
error: Bad exit status from /home/hjunes/rpm/tmp/rpm-tmp.33367 (%build)
It would be nice to be able to compile
401 - 440 of 440 matches
Mail list logo
