From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs setup assistants
Date: Wed, 19 May 2004 09:45:38 -0400 [thread overview]
Message-ID: <E1BQRO6-0002QH-9m@fencepost.gnu.org> (raw)
In-Reply-To: <m3d6514fre.fsf@quimbies.gnus.org> (message from Lars Magne Ingebrigtsen on Tue, 18 May 2004 22:55:17 +0200)
@title Configuring Gnus for reading news
@node Server name and port
@variable server :string (gnus-getenv-nntpserver)
@variable port :number 119
@validate
(let ((stream
This would require changes in Texinfo, which would
make it very hard.
Can you design it to use existing Texinfo constructs? For instance,
just use @example instead of @validate. Use @defopt instead of
@variable.
You can design some convention for giving the extra info
that you need, so it will show up in the Info file or ASCII
output.
next prev parent reply other threads:[~2004-05-19 13:45 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 20:55 Emacs setup assistants Lars Magne Ingebrigtsen
2004-05-19 6:34 ` David Kastrup
2004-05-19 7:32 ` Lars Magne Ingebrigtsen
2004-05-19 10:31 ` David Kastrup
2004-05-19 15:29 ` Ted Zlatanov
2004-05-19 20:49 ` Thien-Thi Nguyen
2004-05-19 21:35 ` Lars Magne Ingebrigtsen
2004-05-20 13:17 ` Richard Stallman
2004-05-20 17:31 ` Ted Zlatanov
2004-05-21 14:12 ` Richard Stallman
2004-05-21 17:42 ` Ted Zlatanov
2004-05-21 19:09 ` Lars Magne Ingebrigtsen
2004-05-21 18:32 ` Eli Zaretskii
2004-05-22 21:44 ` Richard Stallman
2004-05-19 8:18 ` Per Abrahamsen
2004-05-19 9:59 ` Juri Linkov
2004-05-20 7:25 ` David Kastrup
2004-05-20 9:43 ` Eli Zaretskii
2004-05-20 10:57 ` David Kastrup
2004-05-20 13:44 ` Eli Zaretskii
2004-05-20 17:00 ` David Kastrup
2004-05-20 18:31 ` Eli Zaretskii
2004-05-20 19:05 ` Jon Ericson
2004-05-20 19:07 ` Ted Zlatanov
2004-05-21 18:12 ` Eli Zaretskii
2004-05-21 18:04 ` Ted Zlatanov
2004-05-22 11:09 ` Per Abrahamsen
2004-05-24 14:10 ` Ted Zlatanov
2004-05-24 19:46 ` David Kastrup
2004-05-25 18:16 ` Ted Zlatanov
2004-05-25 20:59 ` Juri Linkov
2004-05-25 22:57 ` A.J. Rossini
2004-05-25 23:19 ` Miles Bader
2004-05-26 7:11 ` David Kastrup
2004-05-26 14:04 ` Ted Zlatanov
2004-05-27 8:50 ` David Kastrup
2004-05-26 14:06 ` Ted Zlatanov
2004-05-26 22:14 ` Juri Linkov
2004-05-26 18:57 ` Per Abrahamsen
2004-05-26 10:42 ` Eli Zaretskii
2004-05-26 13:59 ` Ted Zlatanov
2004-05-27 23:54 ` Richard Stallman
2004-05-26 15:26 ` Stefan Monnier
2004-05-27 15:07 ` Ted Zlatanov
2004-05-27 16:59 ` René Kyllingstad
2004-05-27 16:59 ` René Kyllingstad
2004-05-22 13:28 ` Eli Zaretskii
2004-05-20 20:57 ` David Kastrup
2004-05-21 17:57 ` Eli Zaretskii
2004-05-22 11:01 ` Per Abrahamsen
2004-05-21 14:11 ` Richard Stallman
2004-05-29 1:26 ` David A. Cobb
2004-05-30 8:15 ` Per Abrahamsen
2004-05-20 10:00 ` Per Abrahamsen
2004-05-19 6:43 ` David Kastrup
2004-05-19 13:45 ` Richard Stallman [this message]
2004-05-19 15:04 ` David Kastrup
2004-05-19 20:07 ` Eli Zaretskii
2004-05-19 16:41 ` Ted Zlatanov
-- strict thread matches above, loose matches on Subject: below --
2004-05-26 11:48 Berndl, Klaus
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1BQRO6-0002QH-9m@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).