From: Drew Adams <drew.adams@oracle.com>
To: Tom <adatgyujto@gmail.com>, emacs-devel@gnu.org
Subject: RE: Default history-length should be higher
Date: Sat, 25 Jan 2014 00:45:17 -0800 (PST) [thread overview]
Message-ID: <c9177a25-a6f4-4d78-afa2-d5b8d2dec98d@default> (raw)
In-Reply-To: <loom.20140125T085248-431@post.gmane.org>
> > BTW, whether someone finds a history list of 1000 elements to be
> > long or reasonable might also have to do with how they access its
> > elements.
> >
> > If someone typically just cycles among elements using, say, `M-p',
> > instead of searching (using, say, `M-r') or completing, then 1000
> > would generally be far too long a list - as would even 100 probably.
> > (I tend to complete against the history list.)
>
> All users should know at least M-r, it's in the manual, so it
> should be no argument against a longer history list.
I didn't mention it as an argument against a longer history list
(of which I am in favor). My point was that what is long for one
person might be short for another person, depending on how they
typically access the history.
The mere fact that `M-r' is documented does not mean that user X
makes much use of it. Some people are cycling drones.
next prev parent reply other threads:[~2014-01-25 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 19:10 Default history-length should be higher Tom
2014-01-24 20:54 ` Stefan Monnier
2014-01-25 1:35 ` Drew Adams
2014-01-25 6:39 ` Tom
2014-01-25 7:42 ` Drew Adams
2014-01-25 7:56 ` Tom
2014-01-25 8:05 ` Tom
2014-01-25 8:45 ` Drew Adams [this message]
2014-01-26 5:00 ` Michael Welsh Duggan
2014-01-26 19:22 ` Bozhidar Batsov
2014-01-26 19:44 ` Eli Zaretskii
2014-01-26 20:19 ` Bozhidar Batsov
2014-01-26 20:34 ` Óscar Fuentes
2014-01-26 21:16 ` Drew Adams
2014-01-26 23:44 ` Trent W. Buck
2014-01-26 23:52 ` Stefan Monnier
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=c9177a25-a6f4-4d78-afa2-d5b8d2dec98d@default \
--to=drew.adams@oracle.com \
--cc=adatgyujto@gmail.com \
--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).