Hi Carl,
Carl D. Sorensen a écrit :
Some time ago I proposed adding a section to the documentation on the
lilypond parser grammar. I didn't know how to follow up on it then, but I
still think it's useful, even if it's not perfect. And I know a lot more
now.
I think it's useful too.
What w
It's what comes straight out of the parser; I'd welcome any patches to
yyout2grammar.py (which I've attached here). It's been long enough since I
wrote it that I'm not really up on the code any more, and it's serviceable
enough for me to use.
Carl
On 4/24/09 7:17 PM, "Peter Chubb" wrote:
>
Carl> Some time ago I proposed adding a section to the documentation
Carl> on the lilypond parser grammar. I didn't know how to follow up
Carl> on it then, but I still think it's useful, even if it's not
Carl> perfect. And I know a lot more now.
I'd second having this added somewhere.
Carl, a
Some time ago I proposed adding a section to the documentation on the
lilypond parser grammar. I didn't know how to follow up on it then, but I
still think it's useful, even if it's not perfect. And I know a lot more
now.
I have a text file that can be created automatically:
$ bison -v lily/par
Good news, I got the docs built!
(I was missing a TeX package.)
AH
On Mon, Apr 13, 2009 at 10:52 AM, Graham Percival
wrote:
> On Sat, Apr 11, 2009 at 05:29:09PM -0600, Carl D. Sorensen wrote:
>>
>> On 4/11/09 5:21 PM, "Andrew Hawryluk" wrote:
>>
>> > I am trying to build the docs, and I get "pd
Anthony W. Youngman a écrit :
Oh MAO No.!
text is okay, but if you mean GNU info, I absolutely HATE that. A
simple text or pdf that I can read top-to-bottom is fine, but please
DON'T foist on us a hypertext system that a lot of people don't have a
clue how to use.
RMS goes on about
In message <20090424150621.ga5...@nagi>, Graham Percival
writes
Can we build a text version, or at least an info version, of the
CG fairly early in the build process? if it can be done quickly,
could this even be part of the ./autogen.sh process (just like
INSTALL) ?
Oh MAO No.!
tex
Carl D. Sorensen a écrit :
On 4/24/09 9:06 AM, "Graham Percival" wrote:
Actually, we should junk all README files (including
input/new/README); developers should have a single place (the CG)
to look.
IMHO we should keep READMEs whichpoint to the right chapter of the CG.
This and the t
On Fri, Apr 24, 2009 at 10:13:25AM -0600, Carl D. Sorensen wrote:
>
> On 4/24/09 9:06 AM, "Graham Percival" wrote:
>
> > Can we build a text version, or at least an info version, of the
> > CG fairly early in the build process? if it can be done quickly,
> > could this even be part of the ./aut
On 4/24/09 9:06 AM, "Graham Percival" wrote:
> On Mon, Apr 20, 2009 at 06:03:43PM +0200, John Mandereau wrote:
>>> The handmade snippet copy in input/lsr will be overwritten by an
>>> automatically-generated copy when makelsr.py is executed by the snippet
>>> maintainer."
>>>
>> I think this
On Fri, Apr 24, 2009 at 01:26:08PM +0200, John Mandereau wrote:
> Graham Percival a écrit :
>> Hmm, that sounds like it's information about the pdf. How do you
>> feel about "doc-init" or "doc-base" or "doc-stage-one" ? I must
>> admit that none of those are ideal, though.
>>
> I vote for "doc
On Mon, Apr 20, 2009 at 05:48:23PM +0200, John Mandereau wrote:
> John Mandereau a écrit :
>> People should never be bored by manually editing snippets in input/new
>> to write them in input/lsr, as this can be handled automatically by
>> makelsr, but there are some formatting requirements for
On Mon, Apr 20, 2009 at 06:03:43PM +0200, John Mandereau wrote:
>> The handmade snippet copy in input/lsr will be overwritten by an
>> automatically-generated copy when makelsr.py is executed by the snippet
>> maintainer."
>>
> I think this is not necessary.
>
> Thanks for yout work Carl; maybe
Op vrijdag 24-04-2009 om 10:31 uur [tijdzone +0200], schreef John
Mandereau:
> > web -> doc
> ...and here's a patch for GUB3.
Thanks, please ping me when this is in lilypond master?
Jan.
--
Jan Nieuwenhuizen | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://w
Graham Percival a écrit :
On Fri, Apr 24, 2009 at 11:19:15AM +0200, John Mandereau wrote:
pdf-info
Hmm, that sounds like it's information about the pdf. How do you
feel about "doc-init" or "doc-base" or "doc-stage-one" ? I must
admit that none of those are ideal, though.
I vote fo
On Fri, Apr 24, 2009 at 11:19:15AM +0200, John Mandereau wrote:
> Graham Percival a écrit :
>> If you're renaming it anyway, why not give it a
>> more intuitive name?
>>
> It's the first stage of docs building, but for the developer or doc
> writer it just means building PDF and Info docs, s
John Mandereau a écrit :
Thanks for yout work Carl; maybe this could be completed with
information from input/new/README. Btw we may want to junk
input/lsr/README, as (or if) its contents is in the CG.
IMHO you should push this to Git soon, as all essential techical
issues are solved (besides
John Mandereau a écrit :
John Mandereau a écrit :
People should never be bored by manually editing snippets in
input/new to write them in input/lsr, as this can be handled
automatically by makelsr, but there are some formatting requirements
for stuff in input/new that are not necessary for reg
Graham Percival a écrit :
WTM is "web-1"?
Do "make help"... or read below.
If you're renaming it anyway, why not give it a
more intuitive name?
It's the first stage of docs building, but for the developer or doc
writer it just means building PDF and Info docs, so what about
pdf-info
?
On Fri, Apr 24, 2009 at 10:15:30AM +0200, John Mandereau wrote:
> I had the changes for this for weeks in my working tree; it mainly
> renames targets to use more standard names:
>
> web -> doc
> web-1 -> doc-1
WTM is "web-1"? If you're renaming it anyway, why not give it a
more intuitive name?
I haven't looked at your patch or the implementation, but suddenly
remembered about
http://lists.gnu.org/archive/html/lilypond-devel/2008-11/msg00405.html
which seems to indicate that a binary search was already done.
/Mats
Neil Puttock wrote:
Hi,
Please review this patch here:
http://co
John Mandereau a écrit :
it mainly renames targets to use more standard names:
web -> doc
web-1 -> doc-1
web-clean -> doc-clean
web-install -> install-doc
web-uninstall -> uninstall-doc
info-install -> install-info
...and here's a patch for GUB3.
John
diff --git a/gub/specs/lilypond-doc.py b/
Hi,
This is a follow-up of thread "Why is it _still_ so freaking hard to get
info with images?"
http://lists.gnu.org/archive/html/lilypond-devel/2009-03/msg00144.html
I had the changes for this for weeks in my working tree; it mainly
renames targets to use more standard names:
web -> doc
we
23 matches
Mail list logo
