From: era eriksson <era+gmane@iki.fi>
To: bug-gnu-emacs@gnu.org
Subject: Re: Documentation for ido-mode is not very enlightening
Date: Mon, 25 Feb 2008 19:01:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20080225T185432-597@post.gmane.org> (raw)
In-Reply-To: 47C2CC51.8050802@gmx.at
martin rudalics <rudalics <at> gmx.at> writes:
> > Here's the documentation string for the function "ido-mode":
> >
> > ido-mode is a variable defined in `ido.el'.
>
> Hmmm... This is the doc-string for the _variable_ `ido-mode'.
> Please try C-h f RET ido-mode RET instead.
Right you are. That does not change the fundamental problem: if you don't know
what ido-mode is, it won't help you find out.
ido-mode is an interactive autoloaded Lisp function in `ido'.
(ido-mode &optional arg)
Toggle ido speed-ups on or off.
With arg, turn ido speed-up on if arg is positive, off otherwise.
Turning on ido-mode will remap (via a minor-mode keymap) the default
keybindings for the `find-file' and `switch-to-buffer' families of
commands to the ido versions of these functions.
However, if arg arg equals 'files, remap only commands for files, or
if it equals 'buffers, remap only commands for buffer switching.
This function also adds a hook to the minibuffer.
What's an "ido speed-up"? What are "ido versions" of the find-file functions?
If you are terminally curious, you might try it out, but you should not assume
your users have indefinite time and patience. For many users, the amount of
modes and features you could try out at one point or another is overwhelming,
and those with obscure or hard-to-find features are going to go undiscovered by
most users, and waste the time of many who try them out only to find the
features are not useful to them.
Even just the following very brief introduction from the beginning of the
"Comments" section in the ido.el source would help a lot:
Ido - interactive do - switches between buffers and opens files and
directories with a minimum of keystrokes.
Like I wrote in my original report, it would be even better if the entire
comments section of the source file could be turned into documentation. It's
fairly detailed and comprehensive.
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
next prev parent reply other threads:[~2008-02-25 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 19:04 Documentation for ido-mode is not very enlightening era
2008-02-25 14:10 ` martin rudalics
2008-02-25 19:01 ` era eriksson [this message]
2008-02-25 21:49 ` martin rudalics
2008-02-25 22:04 ` Jason Rumney
2008-02-26 19:23 ` era eriksson
2008-02-26 21:14 ` Stefan Monnier
2008-02-27 7:48 ` era eriksson
2008-02-27 16:17 ` Stefan Monnier
2008-02-27 16:30 ` Drew Adams
2008-02-27 21:01 ` Stefan Monnier
2008-02-27 21:34 ` Drew Adams
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=loom.20080225T185432-597@post.gmane.org \
--to=era+gmane@iki.fi \
--cc=bug-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.
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).