[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: pretest time?
From: |
Patrice Dumas |
Subject: |
Re: pretest time? |
Date: |
Sat, 15 Sep 2012 19:45:38 +0200 |
User-agent: |
Mutt/1.5.20 (2009-12-10) |
On Sat, Sep 15, 2012 at 04:15:50PM +0000, Karl Berry wrote:
> I seem to have worked my way back through the various issues I had
> saved to deal with before the pretest. Is there anything left that (any
> of) you know of?
>
> Doesn't seem crucial to deal with the nine not-yet-documented
> configuration variables (INPUT_ENCODING_NAME, etc.) before the pretest.
I attach a patch for that.
> I want to use @code for many more node names, and read through the
> manual once, but that doesn't have to be done first either.
I still have to excerpt the API information and put it in a draft or
something.
There is a question that may be worth looking at before the pretest:
- Strange sentence in @node key:
As a convention in GNU manuals, @code{@@key} should not be used in
index entries.
--
Pat
texinfo.txi-missing_cust_var.diff
Description: Text document
- pretest time?, Karl Berry, 2012/09/15
- Re: pretest time?,
Patrice Dumas <=