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 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
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
Carl D. Sorensen a écrit :
When you run makelsr.py, do you get a message about new snippets that have
been added, so you know snippet names to search the documentation for?
After you have run makelsr.py and cheked for unsafe snippets with the
recommended commands, just look for "new file" in
On 4/18/09 9:55 PM, "Graham Percival" wrote:
> On Sat, Apr 18, 2009 at 09:16:47PM -0600, Carl D. Sorensen wrote:
>>
>>> I don't mind what you do, so long as it doesn't break compilation. :)
>>
>> OK, so how about this for proposal 3 for something to go into the CG:
>
> Here's my proposal: s
On Sun, Apr 19, 2009 at 12:30:56PM +0200, Valentin Villenave wrote:
> 2009/4/19 Graham Percival :
>
> > Historically, we sent the snippet to the LSR editor to deal with.
> > Since we *still* don't have a dedicated LSR editor who has nothing
> > better to do than play with web-2.0 things... i.e. th
2009/4/19 Graham Percival :
> Historically, we sent the snippet to the LSR editor to deal with.
> Since we *still* don't have a dedicated LSR editor who has nothing
> better to do than play with web-2.0 things... i.e. the people who
> /are/ LSR editors are sufficiently skilled that they can be eve
On Sat, Apr 18, 2009 at 09:16:47PM -0600, Carl D. Sorensen wrote:
>
> > I don't mind what you do, so long as it doesn't break compilation. :)
>
> OK, so how about this for proposal 3 for something to go into the CG:
Here's my proposal: since this will change in 6 weeks and it isn't
urgent, we le
On Sat, Apr 18, 2009 at 11:55:31PM +0100, Neil Puttock wrote:
> Another option (though still not ideal since it suffers from the same
> formatting issues as pasting snippets verbatim from input/new ->
> input/lsr) is to use the same name for the regtest as the new snippet,
> then the docs will auto
On 4/18/09 5:45 PM, "Neil Puttock" wrote:
> 2009/4/19 Carl D. Sorensen :
>
>
>> What are the formatting issues when copying snippets into input/lsr? The
>> only thing I've run into is getting the whole header output if you don't put
>> "% begin verbatim" after the header.
>
> I was thinki
2009/4/19 Carl D. Sorensen :
> Perhaps, but I think it's a good idea to actually test how the snippet shows
> up in the docs, because there's documentation, not just LilyPond, in the
> snippet. Is there another way to do this that's easier than making the
> slight change to the snippet and copyin
On 4/18/09 4:55 PM, "Neil Puttock" wrote:
> 2009/4/18 Carl D. Sorensen :
>> [Snip original proposal on LSR snippets]
>
> It still needs ignoring like input/new snippets until an LSR update's been
> done.
>
>> [Snip original proposal on input/new snippets]
>
> I think this is the simplest op
2009/4/18 Carl D. Sorensen :
>
> I think something like the following needs to go in the CG under
> Documentation Work somewhere -- Probably after TWEAKS in section 3.4.
>
> "If a new snippet created for documentation purposes will compile in
> the current LSR version, the snippet should be added t
I think something like the following needs to go in the CG under
Documentation Work somewhere -- Probably after TWEAKS in section 3.4.
"If a new snippet created for documentation purposes will compile in
the current LSR version, the snippet should be added to the LSR, and a
reference to the snipp
18 matches
Mail list logo
