From: David Kastrup <dak@gnu.org>
Cc: xemacs-beta@xemacs.org
Subject: Re: Emacs setup assistants
Date: 19 May 2004 08:34:46 +0200 [thread overview]
Message-ID: <x5hducrkl5.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3d6514fre.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> One project that's been on my mind (well, far back of my mind) for a
> few years has been to implement something that would make it easy to
> set up complex stuff by guiding the user through the process.
>
> This differs from Customize by being a guided tour through the
> options, not just a big whopping menu of stuff to twiddle.
>
> For instance, when setting Gnus up for reading news, an assistant
> would look around the environment for sensible news server defaults,
> present these to the user, ask for corrections, and at the end check
> whether the information given is sensible (ie., that the news server
> exists). (That's a pretty trivial example; setting up spam handling
> or mail reading is much more complicated. :-)
>
> My original plan was to use something HTML-like, and use w3, but Per
> Abraahmsen suggested using something more TeXinfo like, and I thought
> that was a really groovy idea, so here's an example assistant
> specification.
>
> (It's a mock-up; no code has been written, and most assistants would
> have more pages than one.)
>
> -----------
> @title Configuring Gnus for reading news
> @node Server name and port
> @variable server :string (gnus-getenv-nntpserver)
> @variable port :number 119
> @validate
> (let ((stream
> (condition-case err
> (open-network-stream "nntpd" nil server port)
> (error (setq error err)))))
> (if (memq (process-status stream) '(open run))
> (progn
> (delete-process stream)
> t)
> nil)))
> @end validate
> @result gnus-select-method (list server port)
> @text
> To read Usenet news with Gnus, you first have to tell
> Gnus where the news server is.
>
> The server name is @variable{server}; port number @variable{port}.
> @end text
> -----------
>
> Rendering this is another issue.
>
> I'm posting this here (on the Emacs and XEmacs development lists) to
> let all y'all know what's up, and get the loud objections that I'm
> sure are imminent... :-)
Well, there currently is the possibility to say:
If you want to enable document parsing permanently, press @kbd{C-x
C-e} after the following expression:
@example
(progn (require 'tex)
(customize-save-variable 'TeX-master nil "Manual"))
@end example
> And also -- would actually extending the texinfo.el parser be a good
> idea, or should I just roll my own (which would call texinfo.el
> functions, of course)?
I don't see what you are getting at. Info files are not read by the
texinfo parser. Is the question whether you should write your own
info reader?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-05-19 6:34 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5hducrkl5.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=xemacs-beta@xemacs.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.