From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Syncing (gnus)New Features and GNUS-NEWS
Date: Tue, 06 Jan 2004 23:11:08 +0100 [thread overview]
Message-ID: <v9r7yczq0z.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3ekudzo4w.fsf@quimbies.gnus.org>
On Tue, Jan 06 2004, Lars Magne Ingebrigtsen wrote:
> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>> Shouldn't we declare one "master" and create the other automatically?
> [...]
>> Running »makeinfo --no-headers --paragraph-indent=0 --fill-column=83«
>> on `gnus-news.texi' already gives acceptable output
[...]
> Sounds like a good idea.
I've committed two news files gnus-news.texi and gnus-news.el. (See
<news:E1Adz6j-0001bU-00@quimby.gnus.org> for details.)
`gnus-news.texi' is the master file, which is included in `gnus.texi'.
I added a new node "No Gnus"; Please adjust the menu title (-> see
FIXME). texi/GNUS-NEWS can now be created using "make GNUS-NEWS" in
the texi/ subdirectory (after re-running configure).
What is missing: Instead of ./texi/GNUS-NEWS we should create it in
the parent directory. Probably it's best to do this using commit
script on quimby? Another script should disallow changes to
./GNUS-NEWS. (I'm not a CVS expert, but IIRC it's possible.)
I already have converted the current entries form GNUS-NEWS into
`gnus-news.texi' and the auto-generated output is nice, IMHO. If
anyone wants to improve `gnus-news.el', please do so. E.g. one could
use `texinfmt' (like in `infohack.el') instead of the external
"makeinfo".
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2004-01-06 22:11 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
2004-01-06 4:39 ` Lars Magne Ingebrigtsen
2004-01-06 22:11 ` Reiner Steib [this message]
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=v9r7yczq0z.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).