On 8/16/09 5:30 PM, "Joe Neeman" wrote:
> On Sun, 2009-08-16 at 14:05 -0700, Mark Polesky wrote:
>> \version "2.13.4"
>>
>>
>> % QUESTION 1
>>
>> % "quoted string" is STRING
>> strA = "quoted string"
>>
>> % #"hash-quoted string" is SCM_TOKEN
>> strB = #"hash-quoted string"
>>
> I think that the two boxes
>
> 11
> 11
>222++222
>2 11 2
>222++222
> 11
> 11
>
> should suffice for most practical purposes...
Maybe. This is something which should be tested as soon as someone is
going to write support for it
Are we going to give a name to 2.14?
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/107046/diff/1/3
File lily/staff-symbol-referencer-scheme.cc (right):
http://codereview.appspot.com/107046/diff/1/3#newcode45
Line 45: " with @var{grob}.")
fix indents
http://codereview.appspot.com/107046
___
lilyp
On Sun, 2009-08-16 at 19:31 +0200, Michael Käppler wrote:
> Michael Käppler wrote:
> > Hi Joe,
> >> get_paper is called more than once for each paper block. The first time
> >> is probably from parser.yy:847, which actually _creates_ the first paper
> >> block (so no variables have been parsed at a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Sonntag, 16. August 2009 18:52:59 schrieb Nicolas Sceaux:
> Le 14 août 09 à 21:40, Reinhold Kainhofer a écrit :
> > Does anyone have any idea how I can insert a scheme score
> > into the current book using only scheme without the parser?
>
> I'm doi
On 2009-08-16, Mark Polesky wrote:
> Ha! I've never seen this one before...
Hehe. Chances of this happening were higher due to the fact that the
internal clock in the laptop was ~2 minutes behind GMT.
So there was a three minute window for you. :-)
Resyncing now...
Thanks,
-Patrick
Ha! I've never seen this one before...
<>___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi,
I've uploaded a patch to Rietveld which implements
ly:note-head::brew-ez-stencil in scheme.
Please review it here: http://codereview.appspot.com/107046/show
Thanks,
Neil
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/
On Sun, 2009-08-16 at 14:05 -0700, Mark Polesky wrote:
> \version "2.13.4"
>
>
> % QUESTION 1
>
> % "quoted string" is STRING
> strA = "quoted string"
>
> % #"hash-quoted string" is SCM_TOKEN
> strB = #"hash-quoted string"
>
> % these are both 'unexpected STRING_IDENTIFIER's:
> % \
On 2009-08-16, Graham Percival wrote:
> On Sun, Aug 16, 2009 at 04:20:26PM -0700, Patrick McCarty wrote:
> > On 2009-08-16, Graham Percival wrote:
> > > We need png versions of the svg images in Documentation/pictures/.
> > > The current web branch stores pngs in git (see site/graphics/).
> > > Thi
On Sun, Aug 16, 2009 at 04:20:26PM -0700, Patrick McCarty wrote:
> On 2009-08-16, Graham Percival wrote:
> > We need png versions of the svg images in Documentation/pictures/.
> > The current web branch stores pngs in git (see site/graphics/).
> > This is obviously my preference, since it simplifie
On 2009-08-16, Graham Percival wrote:
> We need png versions of the svg images in Documentation/pictures/.
> The current web branch stores pngs in git (see site/graphics/).
> This is obviously my preference, since it simplifies the build
> process.
Just one comment about this...
I see that annota
We need png versions of the svg images in Documentation/pictures/.
The current web branch stores pngs in git (see site/graphics/).
This is obviously my preference, since it simplifies the build
process.
If that's not acceptable, then could somebody add a rule to
Documentation/pictures/GNUmakefile
Mark Polesky wrote Saturday, August 15, 2009 3:26 AM
3) Make the "command index" strictly a *command* index.
Add a separate "property index" strictly for properties. It
could even be on the same page -- just the existence of a menu
with the two different node names should be enough to hel
2009/8/16 Patrick McCarty :
> I suspect this is because LilyPond treats "foo" and #"foo" the same in
> this isolated context.
I think that's correct: all strings are stored as scheme objects since
it simplifies memory allocation (they don't have to be deleted at the
end of their life thanks to Gu
Hi Mark,
I'm not very familiar with LilyPond's parser/lexer, so I can't provide
any specifics. But here are some guesses.
On 2009-08-16, Mark Polesky wrote:
> \version "2.13.4"
>
>
> % QUESTION 1
>
> % "quoted string" is STRING
> strA = "quoted string"
>
> % #"hash-quoted string"
On 2009-08-16, Mark Polesky wrote:
> Should Flex be added to CG 8.2 LilyPond programming languages?
Sure. Bison is already listed there, so it makes sense to include
Flex as well.
-Patrick
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http:/
2009/8/16 Mark Polesky :
> I didn't really ask anything in the previous post. What I
> meant to ask was: Are there any predicates here that I
> *shouldn't* add to the alist? Any objections to including
> all the "C++ predicates"? If no one objects, I'll make a
> patch that includes everything.
Mi
\version "2.13.4"
% QUESTION 1
% "quoted string" is STRING
strA = "quoted string"
% #"hash-quoted string" is SCM_TOKEN
strB = #"hash-quoted string"
% these are both 'unexpected STRING_IDENTIFIER's:
% \strA \strB
% Why isn't \strB an 'unexpected SCM_IDENTIFIER'?
% QU
Le samedi 15 août 2009 à 09:43 +0200, Jan Nieuwenhuizen a écrit :
> - And also, please go read the texi2html script and see if you
>come out alive on the other end. If I saw someone saying this
>was great, I might not even want to *see* their printed notation
>output?
I read it a few
Should Flex be added to CG 8.2 LilyPond programming languages?
- Mark
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
I propose to add this section on the Features page, just after
"Text-based input" (and before "Mix music and text").
- Mark
Accessibility
Text-based input also makes score-writing possible for users with
severe physical disabilities. Dexterity-impaired users who are
unable to type or control a
Michael Käppler wrote:
Hi Joe,
get_paper is called more than once for each paper block. The first time
is probably from parser.yy:847, which actually _creates_ the first paper
block (so no variables have been parsed at all). Perhaps a better place
for normalize() would be after parser.yy:830, wh
Le 14 août 09 à 21:40, Reinhold Kainhofer a écrit :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Apparently Nicolas' commit da383997e929d8301424e9d320e3f5ada7cf6a58
two years
ago (yeah, a long time ago, but I hadn't use that functionality
until today,
when I had to create dozens of exampl
2009/8/16 Jonathan Kulp :
> I seem to recall Valentin saying he'd be willing to make a 1-page snippet
> from his opera. He probably forgot. Maybe it's time for a gentle reminder so
> we'll have something decent there.
Don't worry, I'm still here :)
I've just been visiting my in-laws for a few days
Andrew Hawryluk writes:
> On Sat, Aug 15, 2009 at 4:07 PM, Graham
> Percival wrote:
>
> Indeed. Even after you used that atrocity of HTML: blinking text!
> Here's an improved chart.ly - someone may submit a better one before
> go-live, but this is definitely better than "we need words!"
It would
Le samedi 15 août 2009 à 07:50 -0600, Carl Sorensen a écrit :
> I think that John Mandereau is working on the 2000 lines of python we would
> need to parse texinfo. We may be close to this in the next couple of
> months!
Well, I bet I can make the parser less than 1000 lines, including
comments,
28 matches
Mail list logo
