Re: interactive Lilypond
Guido on Debian wrote:
>
> Il giorno dom, 28/05/2006 alle 16.03 +0200, Nicolas Sceaux ha scritto:
>> Guido Amoruso <[EMAIL PROTECTED]> writes:
>>
>> > 2. Creation of music expression. I'd like to be able to do something
>> >like
>> >
>> > "(define music (parse-string "{c'' dd'}")"
>> >
>> >in order to build scores both interactively and programmatically. I
>> >know there is "ly:parse-string", but I don't understand how it
>> >should work. This would be sure interesting in non interactive
>> >use cases, too.
>>
>> Look at scm/parser-ly-from-scheme.scm, where the #{ #} syntax is
>> implemented.
>> (define music #{ c'' dd' #}) should do it.
>
> Anyway, that does work from file only: in the interactive session it
> segfaults, perhaps I'm missing some initialization, because
> "(ly:output-def-parser $defaultpaper)" returns a Parser without a Lexer:
> #
> I'm getting the wrong parser? Or can I initialize the lexer, too? Can it
> be fixed? Maybe I'm still missing something else...
>
>
I'm building from git on Gentoo, and although this scenario doesn't segfault
for me, I am unable to get the read-hash-extended syntax to work
interactively. It is no better if I embed the call to readline into a file.
Is there a way to work with the parser from an interactive guile session?
This looks as though it may be a regression, since I've seen examples from
earlier releases that imply that this approach worked at one time.
If I type
guile> (display-scheme-music #{ \relative c { c } #})
I get a (wrong-type-arg) error complaining about the parser being #f
Sorry if this is a dup. I didn't see a bug report on this.
--
View this message in context:
http://www.nabble.com/interactive-Lilypond-tf1694638.html#a12265390
Sent from the Gnu - Lilypond - Dev mailing list archive at Nabble.com.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Broken Spanish documentation
El mar, 21-08-2007 a las 10:13 +0200, John Mandereau escribió: > Maybe this is caused by your recent change to @documentencoding in > es/user/lilypond.tely (UTF-8 -> utf-8) -- why did you want to write the > encoding lower-case? Mmm... let's have a closer look to the originals and their translations. Documentation/user$ grep -i documentencoding * lilypond-program.tely:@documentencoding utf-8 lilypond.tely:@documentencoding utf-8 music-glossary.tely:@documentencoding UTF-8 This gives 2-1 for lowercase vs. uppercase. Documentation/es/user$ grep -i documentencoding * lilypond.tely:@documentencoding utf-8 1-0 for lowercase, but the other two files do not exist in the es/user directory. Documentation/es/user$ grep utf * Here the results vary randomly between the two following versions: @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*- @c -*- coding: utf-8; mode: texinfo; -*- The GREP-ing in the originals gives only the second of these, of course. And now Documentation/user$ grep UTF * The only meaningful result here is music-glossary.tely:@documentencoding UTF-8 Is this all of any usefulness? -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Broken Spanish documentation
El mar, 21-08-2007 a las 10:13 +0200, John Mandereau escribió: > Le lundi 20 août 2007 à 20:15 +0200, Paco a écrit : > > Hello all, > > > > I don't really if in 2.11.29 the link to the Spanish HTML manual worked, > > but now in 2.11.30 it is broken. > > Sorrry, I have no time to fix it now, because I have no more Internet > connection from now to Friday, or maybe Monday, because I'm leaving home > again. > > > > Also, the Spanish PDF lacks of accented characters at all, maybe my last > > patches were not properly coded as UTF-8? > > Maybe this is caused by your recent change to @documentencoding in > es/user/lilypond.tely (UTF-8 -> utf-8) -- why did you want to write the > encoding lower-case? Because it is that way in the original! This line is just copypasted from there. -- Francisco Vila. Badajoz (Spain) http://www.paconet.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \markup placement (Was: Re: collision barline with accidental)
The positioning has nothing to do with if you use ^\markup{c} or ^"c".
I the 2.11.x version, the text scripts are placed on several lines if
they don't
fit on the same line with the default note spacing.
You can change this with the \fatText macro (see the definition in
ly/property-init.ly if you want to include the setting in \neumeDemoLayout)
so that the note spacing is increased to make room for the text scripts.
/Mats
Juergen Reuter wrote:
Hi all,
while you are at it (I mean, the placement/spacing code, though I am
not sure if this is anyhow related)...
I noticed that in Manual Sect. 7.7.10.2 ("Gregorian square neumes
ligatures") the placement of the letters in the neumes table changes
from almost each version of the lily 2.11.x series to the next
release: sometimes, the letters appear above the glyph, sometimes
below, sometimes they are stacked upon each other, sometimes they
appear in a horizontal row, with these flavors mixing even within the
same version of lily... Is this intended behavior? (N.B.: In lily
2.10.29, the letters are placed consistently above the glyphs and in
horizontal rows.)
Btw., I do not mind where the letters actually appear, as long as the
placement is somewhat consistent and it gets clear that each letter is
associated with a glyph. Maybe the letters should not be typeset with
the \markup command, as it is currently done?
Greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
\markup placement (Was: Re: collision barline with accidental)
Hi all,
while you are at it (I mean, the placement/spacing code, though I am not
sure if this is anyhow related)...
I noticed that in Manual Sect. 7.7.10.2 ("Gregorian square neumes
ligatures") the placement of the letters in the neumes table changes from
almost each version of the lily 2.11.x series to the next release:
sometimes, the letters appear above the glyph, sometimes below, sometimes
they are stacked upon each other, sometimes they appear in a horizontal
row, with these flavors mixing even within the same version of lily... Is
this intended behavior? (N.B.: In lily 2.10.29, the letters are placed
consistently above the glyphs and in horizontal rows.)
Btw., I do not mind where the letters actually appear, as long as the
placement is somewhat consistent and it gets clear that each letter is
associated with a glyph. Maybe the letters should not be typeset with the
\markup command, as it is currently done?
Greetings,
Juergen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Broken Spanish documentation
Le lundi 20 août 2007 à 20:15 +0200, Paco a écrit : > Hello all, > > I don't really if in 2.11.29 the link to the Spanish HTML manual worked, > but now in 2.11.30 it is broken. Sorrry, I have no time to fix it now, because I have no more Internet connection from now to Friday, or maybe Monday, because I'm leaving home again. > Also, the Spanish PDF lacks of accented characters at all, maybe my last > patches were not properly coded as UTF-8? Maybe this is caused by your recent change to @documentencoding in es/user/lilypond.tely (UTF-8 -> utf-8) -- why did you want to write the encoding lower-case? Cheers, John ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: collision barline with accidental
> > Shall I file a bug report w.r.t. the other accidental issue I've > > mentioned, or are you going to fix this soon too? > > I don't know exactly what's causing the other problem, so it might > be a little while before I fix it. A bug report would remind me of > its existence. Done. Cf. issue #418. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: collision barline with accidental
On Tuesday 21 August 2007 15:30, Werner LEMBERG wrote: > > > [git 2007-08-19 13d78fe] > > > > > > While Joe's latest changes to the horizontal spacing are giving > > > good results, here's a special case where it fails. > > > > Thanks, the spacing part of this issue is fixed. > > Thanks too! Shall I file a bug report w.r.t. the other accidental > issue I've mentioned, or are you going to fix this soon too? I don't know exactly what's causing the other problem, so it might be a little while before I fix it. A bug report would remind me of its existence. Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
