2008/8/13 Carl Sorensen <[EMAIL PROTECTED]>:
> 1) At the end of Single staff polypohony:
>
> "This is a better construct to keep control of the voices, for example,
> to ease a consistent assign of lyrics to the proper voice context."
>
> might be better worded as
>
> "This construct keeps a voice
Francisco wrote Thursday, August 14, 2008 11:05 AM
@lilypond [guote, verbatim, relative =1]
<<
\new Staff {
\context Voice = "mel" {
c4
<<
{
\voiceOne g' g
}
\new Voice {
\voiceTwo e e
}
>>
\oneVoice
g
}
}
\new Lyri
2008/8/14 Trevor Daniels <[EMAIL PROTECTED]>:
>
> \new Voice is definitely better here. This is not
> a good place to explain \context, but I think it would be good to say a
> little more about explicitly
> instantiating voices. Just a sentence with a ref
> to that section in the Learning Manual
On 8/14/08 4:05 AM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/8/13 Carl Sorensen <[EMAIL PROTECTED]>:
>>
>> @lilypond [guote, verbatim, relative =1]
>> <<
>> \new Staff {
>>\context Voice = "mel" {
>> c4
>> <<
>>{
>> \voiceOne g' g
>>}
>>
2008/8/14 Trevor Daniels <[EMAIL PROTECTED]>:
> \new Voice is definitely better here. This is not
> a good place to explain \context, but I think it would be good to say a
> little more about explicitly
> instantiating voices. Just a sentence with a ref
> to that section in the Learning Manual wo
I obtain this message when trying to compile the docs:
error: failed files: "b9/lily-50c2d14a.ly 39/lily-fb53c11d.ly
e3/lily-de1b891c.ly"
I have found these files in
./input/regression/musicxml/out-www/b9/lily-50c2d14a.ly
./input/regression/musicxml/out-test/39/lily-fb53c11d.ly
./input/regress
On Thu, Aug 14, 2008 at 9:13 AM, Francisco Vila <[EMAIL PROTECTED]> wrote:
> I obtain this message when trying to compile the docs:
>
> error: failed files: "b9/lily-50c2d14a.ly 39/lily-fb53c11d.ly
> e3/lily-de1b891c.ly"
>
> I have found these files in
>
> ./input/regression/musicxml/out-www/b9/li
Le 14.08.2008 18:13, Francisco Vila disait :
I obtain this message when trying to compile the docs:
error: failed files: "b9/lily-50c2d14a.ly 39/lily-fb53c11d.ly
e3/lily-de1b891c.ly"
I have found these files in
./input/regression/musicxml/out-www/b9/lily-50c2d14a.ly
./input/regression/musicx
Jean-Charles,
Your latest commit adds backslashes back into the node name.
We had a recent discussion on the problems of having
backslashes in node names:
http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/16894
The result of the discussion was a determination that if
section names had a bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 14. August 2008 schrieb Francisco Vila:
> I obtain this message when trying to compile the docs:
>
> error: failed files: "b9/lily-50c2d14a.ly 39/lily-fb53c11d.ly
> e3/lily-de1b891c.ly"
>
> I have found these files in
>
> ./input/regre
2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
>> How can I skip this part and compile eg NR or LM only?
>
> go into to the Documentation/ directory and run 'make web' only there. This
> will build everything below Documentation, but not files outside this
> directory.
Yes, this works for my pu
On Thu, Aug 14, 2008 at 10:02 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> Jean-Charles,
>
> Your latest commit adds backslashes back into the node name.
>
> We had a recent discussion on the problems of having
> backslashes in node names:
>
> http://thread.gmane.org/gmane.comp.gnu.lilypond.de
On Wed, Aug 13, 2008 at 1:06 AM, Trevor Daniels <[EMAIL PROTECTED]> wrote:
>
> Patrick McCarty wrote Wednesday, August 13, 2008 4:21 AM
>>
>> I have a couple of questions regarding my section (NR 1.6):
>>
>> *NR 1.6.2.1 Staff symbol
>>
>> This section is describing every single way to modify the pr
Please have a look at the attached image, produced by the following
code:
\version "2.11.55"
\relative c'' {
\time 2/4 c2 |
<< { c2 }
\new Staff \with {
\remove "Time_signature_engraver"
}
{ c2 } >> |
<< { c2 }
\new Staff \with {
\remove "Time_signature
> Please have a look at the attached image, produced by the following
> code:
Oops, here it is.
Werner
<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Le 14.08.2008 19:02, Carl D. Sorensen disait :
Jean-Charles,
Your latest commit adds backslashes back into the node name.
We had a recent discussion on the problems of having
backslashes in node names:
http://thread.gmane.org/gmane.comp.gnu.lilypond.devel/16894
The result of the discussion wa
On 8/14/08 12:20 PM, "Jean-Charles Malahieude" <[EMAIL PROTECTED]> wrote:
> Le 14.08.2008 19:02, Carl D. Sorensen disait :
>> Jean-Charles,
>>
>> Your latest commit adds backslashes back into the node name.
>>
>> We had a recent discussion on the problems of having
>> backslashes in node names:
On Thu, Aug 14, 2008 at 11:46 AM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
>
> On 8/14/08 12:20 PM, "Jean-Charles Malahieude" <[EMAIL PROTECTED]> wrote:
>
>> Le 14.08.2008 19:02, Carl D. Sorensen disait :
>>> Jean-Charles,
>>>
>>> Your latest commit adds backslashes back into the node name.
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 14. August 2008 schrieb Patrick McCarty:
> On Thu, Aug 14, 2008, Carl D. Sorensen <[EMAIL PROTECTED]> wrote:
> > I think it is to take the backslash off the node, isn't it?
>
> The issue is with getting the @ref{...} calls to work with
>
On 8/14/08 9:47 AM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/8/14 Trevor Daniels <[EMAIL PROTECTED]>:
>> \new Voice is definitely better here. This is not
>> a good place to explain \context, but I think it would be good to say a
>> little more about explicitly
>> instantiating voice
2008/8/14 Han-Wen Nienhuys <[EMAIL PROTECTED]>:
> Go ahead.
OK, all done.
Cheers,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Thu, 14 Aug 2008 19:08:03 +0200
"Francisco Vila" <[EMAIL PROTECTED]> wrote:
> 2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> >> How can I skip this part and compile eg NR or LM only?
> >
> > go into to the Documentation/ directory and run 'make web' only
> > there. This will build everythi
2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> The only solution I can think of right now is the attached patch: It adds a
> two-parameter macro @rusernamed in addition to @ruser (and similar commands
> for all other ref macros), which allows to give a displayed link text for
> those nodes, wh
2008/8/14 Werner LEMBERG <[EMAIL PROTECTED]>:
> IMHO, the second ossia staff should stop right at the barline, similar
> to the first one. This looks like a bug, especially because the time
> signature engraver has been removed.
Greetings Werner,
may I ask why you posted this to -devel? Do you
2008/8/14 Francisco Vila <[EMAIL PROTECTED]>:
> Yes, this works for my purpose. I can't help being surprised how can I
> be the only one person having problems like these
You're not, but in this case I silently clean everything and rebuild
the binary and the docs, like Jean-Charles.
> isn't the
> > IMHO, the second ossia staff should stop right at the barline,
> > similar to the first one. This looks like a bug, especially
> > because the time signature engraver has been removed.
>
> may I ask why you posted this to -devel? Do you want this to be
> added to the tracker?
Because I'm no
2008/8/11 Valentin Villenave <[EMAIL PROTECTED]>:
> AFAICR, John chose not to have such pages because there was (and still
> isn't) no manual entirely translated in any language (and he refused
> to have a semi French/semi English HTML big page or PDF manual). But
> this is (hopefully) likely to ch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 14. August 2008 schrieben Sie:
> 2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> > The only solution I can think of right now is the attached patch: It adds
> > a two-parameter macro @rusernamed in addition to @ruser (and similar
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 14. August 2008 schrieb John Mandereau:
> 2008/8/14 Francisco Vila <[EMAIL PROTECTED]>:
> > Yes, this works for my purpose. I can't help being surprised how can I
> > be the only one person having problems like these
>
> You're not, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 14. August 2008 schrieb Valentin Villenave:
> 2007/7/8 Dewdman42 <[EMAIL PROTECTED]>:
> > I can't seem to find anything in the Lilypond manual about creating harp
> > pedal symbols. I would think this issue has been covered a lot by use
2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> Here's my attempt, which defines a \harp-pedal #"^v-|^--v" markup command
> (plus a version, which takes a list of 1, 0, -1 and #\| - unfortunately that
> version has some caveats as detailled in the .ly file).
Gee, you're fast. I never had a ch
On 8/14/08 4:21 PM, "Valentin Villenave" <[EMAIL PROTECTED]> wrote:
>
> One more possible improvement: if you look well at the jpeg sample
> Steve provided us with in the first place, you'll see that the
> vertical line is actually at the middle of the horizontal line (hence
> my problems with
2008/8/14 Carl D. Sorensen <[EMAIL PROTECTED]>:
> I've looked at the new change, and I think it's understandable. Perhaps it
> would be clearer if we started with single-staff polyphony with named and
> explicitly created voices, along with the \voiceOne through \voiceFour
> properties.
>
> We cou
On 8/14/08 5:21 PM, "Francisco Vila" <[EMAIL PROTECTED]> wrote:
>
> That said, I don't see when could I seriously start working on Vocal
> music. I have two choices: a) Reword or reorder the section and leave
> Vocal to Trevor or any other GDP hero. b) Leave Simultaneous as is for
> 2.12 and tr
Thank you very much, this is very helpful.
I beg your pardon, but it is a bit funny to see that every person here
has his own esotheric liturgia, as wizards trying to dominate the
beast by different formulae.
This grown-up makefile does its work, but the whole process looks to
me a bit fuzzy (in t
On Thu, Aug 14, 2008 at 1:45 PM, John Mandereau
<[EMAIL PROTECTED]> wrote:
> 2008/8/14 Reinhold Kainhofer <[EMAIL PROTECTED]>:
>> The only solution I can think of right now is the attached patch: It adds a
>> two-parameter macro @rusernamed in addition to @ruser (and similar commands
>> for all oth
2008/8/15 Carl D. Sorensen <[EMAIL PROTECTED]>:
> http://hometown.aol.com/loudfonts/ThesiFnt.htm#7
Here is another one:
http://www.rpmseattle.com/coda/imx/logos/HarpTitle.jpg
--
Francisco Vila. Badajoz (Spain)
http://www.paconet.org
___
lilypond-devel
2008/8/15 Francisco Vila <[EMAIL PROTECTED]>:
> That said, I don't see when could I seriously start working on Vocal
> music. I have two choices: a) Reword or reorder the section and leave
> Vocal to Trevor or any other GDP hero. b) Leave Simultaneous as is for
> 2.12 and try to gain some advance
2008/8/15 Valentin Villenave <[EMAIL PROTECTED]>:
> IIRC, I had mentioned I could take Vocal when I'm done with Text. As
> I'm finishing my opera I'm progressing quite slowly right now, but be
> assured if you don't do Vocal, then someone will (namely me, if we
> haven't found anybody else until th
I've been working on tracking down the loss of functionality for
Forbid_line_break_engraver.
To do this I have to check out various commits and see if they have the
functionality.
>From time to time I need to blast out the object files because make gives me
an error.
So I've been doing "make cle
The code below
%
\paper{
ragged-right=##f
line-width=3\cm
indent=0\cm
}
\new Voice \with {
\remove "Note_heads_engraver"
\consists "Completion_heads_engraver"
%\remove "Forbid_line_break_engraver"
}
\relative c' {
e4 e e e2 % Line break should be forbidden here, but it's not
f4 f f
On Fri, 15 Aug 2008 03:03:48 +0200
"Valentin Villenave" <[EMAIL PROTECTED]> wrote:
> 2008/8/15 Francisco Vila <[EMAIL PROTECTED]>:
>
> > That said, I don't see when could I seriously start working on Vocal
> > music. I have two choices: a) Reword or reorder the section and
> > leave Vocal to Trev
> I've just found a wonderful example which demonstrates what I want to
> fix. Look at the fourth and fifth quarter: It's *really* ugly.
>
> On the other hand I'm not sure whether this is a different spacing
> bug. Joe?
This is indeed a different bug, caused by my special setup using an
invisib
On Fri, Aug 15, 2008 at 3:03 AM, Werner LEMBERG <[EMAIL PROTECTED]> wrote:
>> I've just found a wonderful example which demonstrates what I want to
>> fix. Look at the fourth and fifth quarter: It's *really* ugly.
>>
>> On the other hand I'm not sure whether this is a different spacing
>> bug. Jo
> > Attached are two files which show the difference. Again, I'm posting
> > it here to the list and not to the bug tracker so that either Han-Wen
> > or Joe can confirm the problem. Maybe this was an intentional change,
> > and I just missed to adjust my data accordingly.
>
> 2.11.20 to 2.11.55
45 matches
Mail list logo
