From: dkcombs@panix.com (David Combs)
To: help-gnu-emacs@gnu.org
Subject: Re: M-x custom: *PLEASE*, someone, have it build an INDEX (as in *info*)
Date: Sat, 30 Jan 2010 00:48:25 +0000 (UTC) [thread overview]
Message-ID: <hjvvkp$675$3@reader1.panix.com> (raw)
In-Reply-To: mailman.1677.1263871922.18930.help-gnu-emacs@gnu.org
In article <mailman.1677.1263871922.18930.help-gnu-emacs@gnu.org>,
Kevin Rodgers <kevin.d.rodgers@gmail.com> wrote:
>David Combs wrote:
>> Unlike most everyone else, I find "custom" basically UNUSABLE.
>>
>> (Actually, I'd much prefer a super-LONG edit-options -- at least
>> I could run M-x occur on it, see where things were.
>>
>> This custom thing -- I have no idea where things are, how far
>> down I have to go.
>>
>> Maybe if someone could code it to draw one HUGE tree (lying on its
>> side, of course), but the current scheme doesn't work for me.
>>
>> So, an INDEX would help -- each one being a LINK to the thing
>> it's about. Custom would make the index each time it started up.
>
>Why not `M-x apropos-variable' to generate the *Apropos* buffer as a
>virtual index? Then click on one of the links to display the *Help*
>buffer for any variable, which has a link to customize the variable.
>
>--
>Kevin Rodgers
>Denver, Colorado, USA
>
>
>
You mean with a regexp like "."? To get EVERYTHING?
(everything that emacs knows about, anyway, at that time
I guess that custom works the same way -- if a .el file
hasn't yet been read in, emacs won't know any of its
variables?
Or is that just plain wrong. Isn't there something that
is predefined, and if referenced, it's then read in?
Or is that just for defuns? Or not even emacs-lisp?)
David
next prev parent reply other threads:[~2010-01-30 0:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 10:37 M-x custom: *PLEASE*, someone, have it build an INDEX (as in *info*) David Combs
2010-01-19 3:31 ` Kevin Rodgers
2010-01-19 4:55 ` Drew Adams
2010-01-20 23:01 ` Ilya Zakharevich
2010-01-30 0:51 ` David Combs
[not found] ` <mailman.1677.1263871922.18930.help-gnu-emacs@gnu.org>
2010-01-30 0:48 ` David Combs [this message]
2010-01-30 3:05 ` Tim X
2010-01-30 7:26 ` Kevin Rodgers
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='hjvvkp$675$3@reader1.panix.com' \
--to=dkcombs@panix.com \
--cc=help-gnu-emacs@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.
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).