From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Syncing (gnus)New Features and GNUS-NEWS
Date: Mon, 05 Jan 2004 23:14:37 +0100 [thread overview]
Message-ID: <plop87y8sm3uwi.fsf@gnu-rox.org> (raw)
In-Reply-To: <v9n092leuv.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 05 Jan 2004 14:11:36 +0100")
[-- Attachment #1: Type: text/plain, Size: 1442 bytes --]
On 5 Jan 2004, Reiner Steib<4.uce.03.r.s@nurfuerspam.de> verbalized:
> Hi,
>
> currently we have two places were new (user-visible) features are
> described:
>
> 1. The node (info "(gnus)New Features") in `texi/gnus.texi'
>
> 2. GNUS-NEWS (plain test file in outline mode).
>
> Is the intention that both places should contain (essentially) the
> same information?
>
> I think we should (and must) keep GNUS-NEWS for several reasons (e.g.
> for later inclusion in Emacs' NEWS file and to allow users to see
> what's new without installing the info manual).
>
> Shouldn't we declare one "master" and create the other automatically?
> (What I usually do is write an entry for `gnus.texi', Copy&Paste the
> formated info-output to GNUS-NEWS and adjust it slightly (line breaks,
> etc). Creating the text version first and adding the markup later is
> very annoying, IMHO.)
>
> Maybe it would make sense to factor out the No Gnus node (i.e. the
> current version) to `gnus-news.texi', add "@include gnus-news.texi" in
> `gnus.texi' and convert `gnus-news.texi' to GNUS-NEWS automatically.
>
> Running »makeinfo --no-headers --paragraph-indent=0 --fill-column=83«
> on `gnus-news.texi' already gives acceptable output (see a quick test
> below). Of course some modifications have to be done (by sed or in
> lisp).
>
> Opinions?
I do agree with that.
zeDek
--
.o. | Hacker wonderland
..o |
ooo |
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2004-01-05 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 13:11 Reiner Steib
2004-01-05 15:19 ` Simon Josefsson
2004-01-05 20:29 ` Steinar Bang
2004-01-05 22:14 ` Xavier Maillard [this message]
2004-01-06 4:39 ` Lars Magne Ingebrigtsen
2004-01-06 22:11 ` Reiner Steib
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=plop87y8sm3uwi.fsf@gnu-rox.org \
--to=zedek@gnu-rox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).