From: Alan Mackenzie <acm@muc.de>
Subject: Re: Visit random info files?
Date: Sat, 14 May 2005 12:56:53 +0000 [thread overview]
Message-ID: <lis46d.6g.ln@acm.acm> (raw)
In-Reply-To: mailman.4709.1115847214.2819.help-gnu-emacs@gnu.org
Ryan Bowman <ryanlbowman@yahoo.com> wrote on Wed, 11 May 2005 14:30:38
-0700 (PDT):
> Prefacing my question, I know nothing of info files, is it possible to
> write a function that visits a randomly chosen page from all available
> info files? If so, Would someone be willing to instruct me on how such
> a function could be composed (or is there one already)?
Maybe it's not quite what you're looking for, but C-u C-h i might do. It
loads the file you tell it as an info file.
> Ryan Bowman
--
Alan Mackenzie (Munich, Germany)
Email: aacm@muuc.dee; to decode, wherever there is a repeated letter
(like "aa"), remove half of them (leaving, say, "a").
next prev parent reply other threads:[~2005-05-14 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.4709.1115847214.2819.help-gnu-emacs@gnu.org>
2005-05-11 23:23 ` Visit random info files? Thien-Thi Nguyen
2005-05-14 12:56 ` Alan Mackenzie [this message]
2005-05-11 21:30 Ryan Bowman
2005-05-11 21:57 ` Joe Corneli
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=lis46d.6g.ln@acm.acm \
--to=acm@muc.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 read-only IMAP folder(s) and NNTP newsgroup(s).