-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 07:51:25 schrieb Graham Percival:
> Anybody feel like seeing a joke? Apply the attached patch and
> make doc.
>
> Does anybody have any clue why "texi2html --split=foo" results in
> *nothing* being stored in $Texi2HTML::Con
[moved from -user]
According to Neil's proposals and Carl's annotations, I created a patch
to enhance the automatic polyphony:
<< ... \\ .. >> constructs can now be used within
\DrumStaff, \TabStaff and \Staff constructs, without to
explicitly inserting placeholders.
I send it as a gzipped file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 02:28:39 schrieb joenee...@gmail.com:
> On 2009/08/22 00:11:34, Reinhold wrote:
> > http://codereview.appspot.com/109070/diff/1/2
> > File lily/general-scheme.cc (right):
> >
> > http://codereview.appspot.com/109070/diff/1/2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 20. August 2009 00:19:41 schrieb Neil Puttock:
> 2009/8/14 Reinhold Kainhofer :
> > I tried adding various classes to the quotedEventTypes list, e.g.
> > override- property-event general-music override-property OverrideProperty
> > prope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 11:15:13 schrieb Reinhold Kainhofer:
> Am Samstag, 22. August 2009 07:51:25 schrieb Graham Percival:
> > Anybody feel like seeing a joke? Apply the attached patch and
> > make doc.
> >
> > Does anybody have any clue why "te
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 13:06:59 schrieb Reinhold Kainhofer:
> Am Donnerstag, 20. August 2009 00:19:41 schrieb Neil Puttock:
> > 2009/8/14 Reinhold Kainhofer :
> > > I tried adding various classes to the quotedEventTypes list, e.g.
> > > override-
If we're covering shell variables for Windows, like $ for *ix, we'd need
to escape "%" character, too.
That way we'd handle cmd variables like %HOME% or %PATH%.
http://codereview.appspot.com/109070/diff/15/16
File lily/general-scheme.cc (right):
http://codereview.appspot.com/109070/diff/15/16#n
2009/8/22 Reinhold Kainhofer :
> Actually, the Engraver_Group receives and processes them perfectly well. The
> real problem is that each \override (without \once) is immediately followed by
> a corresponding Revert event, of course rendering that override ineffective:
Hmm, it looks like the prop
On 8/22/09 3:47 AM, "Marc Hohl" wrote:
> [moved from -user]
>
> According to Neil's proposals and Carl's annotations, I created a patch
> to enhance the automatic polyphony:
>
> << ... \\ .. >> constructs can now be used within
> \DrumStaff, \TabStaff and \Staff constructs, without to
> expl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 02:28:39 schrieb joenee...@gmail.com:
> On 2009/08/22 00:11:34, Reinhold wrote:
> > On 2009/08/21 22:59:33, joeneeman wrote:
> > > Don't forget to escape $. Or else use single quotes rather than double
> > > quotes.
>
> > Go
brief comments:
- can you include the front-end work in the patch too? It makes it
easier to see what is going on
- get_porperty_setting() should take SCMs rather than const char* , so
you save runtime lookups.
On Sat, Apr 11, 2009 at 7:28 PM, Reinhold
Kainhofer wrote:
> -BEGIN PGP SIGNED M
I understand texinfo needs 2 spaces after ".", but if the "." is
the last thing on a line, do I need to put 2 spaces somewhere?
After the "." on the same line? At the beginning of the next line?
Or is it not needed in that situation?
I did my "homework", too, but I couldn't find the answer here:
h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Samstag, 22. August 2009 19:19:18 schrieb Han-Wen Nienhuys:
> brief comments:
>
> - can you include the front-end work in the patch too? It makes it
> easier to see what is going on
I copied the would-be new definitions of cresc, dim and decresc to
Mark Polesky writes:
> I understand texinfo needs 2 spaces after ".", but if the "." is
> the last thing on a line, do I need to put 2 spaces somewhere?
> After the "." on the same line? At the beginning of the next line?
> Or is it not needed in that situation?
Not needed. Period at newline is
Carl Sorensen schrieb:
On 8/22/09 3:47 AM, "Marc Hohl" wrote:
[moved from -user]
According to Neil's proposals and Carl's annotations, I created a patch
to enhance the automatic polyphony:
<< ... \\ .. >> constructs can now be used within
\DrumStaff, \TabStaff and \Staff constructs, with
Jay Anderson schrieb:
[...]
So what do you think? Should the "SmallStaff" just
be left as a snippet?
If it is a snippet ideally I'd want to do something like:
\include "small_staff.lyi"
\score {
\new SmallStaff {...}
}
How would one make small_staff.lyi so this worked? This way it would
be
On 8/22/09 11:34 AM, "Reinhold Kainhofer" wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Samstag, 22. August 2009 19:19:18 schrieb Han-Wen Nienhuys:
>> brief comments:
>>
>> - can you include the front-end work in the patch too? It makes it
>> easier to see what is going on
All of the @sourceimage commands are causing build problems:
introduction.itexi
download.itexi
I've commented them out to continue my work, since I don't know how they are
supposed to work!
Andrew
___
lilypond-devel mailing list
lilypond-devel@gnu.o
On 8/22/09 12:11 PM, "Marc Hohl" wrote:
> Carl Sorensen schrieb:
>>
>> On 8/22/09 3:47 AM, "Marc Hohl" wrote:
>>
>>
>>> [moved from -user]
>>>
>>> According to Neil's proposals and Carl's annotations, I created a patch
>>> to enhance the automatic polyphony:
>>>
>>> << ... \\ .. >> cons
On Sat, Aug 22, 2009 at 02:34:40PM -0600, Andrew Hawryluk wrote:
>All of the @sourceimage commands are causing build problems:
> introduction.itexi
> download.itexi
>
>I've commented them out to continue my work, since I don't know how they
>are supposed to work!
Why are you
On Sat, 2009-08-22 at 13:01 +0200, Reinhold Kainhofer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am Samstag, 22. August 2009 02:28:39 schrieb joenee...@gmail.com:
> > On 2009/08/22 00:11:34, Reinhold wrote:
> > > http://codereview.appspot.com/109070/diff/1/2
> > > File lily/gener
On Sat, Aug 22, 2009 at 02:24:22PM -0600, Carl Sorensen wrote:
>
> On 8/22/09 11:34 AM, "Reinhold Kainhofer" wrote:
>
> > Graham does not want any syntax changes prior to 2.14, so this won't go into
> > spanner-init.ly. But these three definitions is all that is to be said about
> > the frontend
On Sat, Aug 22, 2009 at 11:29:49AM +0200, Reinhold Kainhofer wrote:
> Am Samstag, 22. August 2009 11:15:13 schrieb Reinhold Kainhofer:
> > How are you calling texi2html exactly? My guess is that your call looks
> > like texi2html --init=web-texi2html.init --split=foo general.texi
Yes, true. Figur
On 8/22/09 5:13 PM, "Graham Percival" wrote:
> On Sat, Aug 22, 2009 at 02:24:22PM -0600, Carl Sorensen wrote:
>>
>> On 8/22/09 11:34 AM, "Reinhold Kainhofer" wrote:
>>
>>> Graham does not want any syntax changes prior to 2.14, so this won't go into
>>> spanner-init.ly. But these three defin
On Sat, Aug 22, 2009 at 4:53 PM, Graham Percival
wrote:
> On Sat, Aug 22, 2009 at 02:34:40PM -0600, Andrew Hawryluk wrote:
> >All of the @sourceimage commands are causing build problems:
> > introduction.itexi
> > download.itexi
> >
> >I've commented them out to continue my work,
25 matches
Mail list logo
