From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: should search ring contain duplicates?
Date: Sun, 14 May 2006 16:46:27 -0700 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEBDDGAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1FfQ24-0002cT-K7@fencepost.gnu.org>
See the thread at
http://lists.gnu.org/archive/html/emacs-devel/2004-09/msg00038.html
Thx. The only argument I see in that thread for ever
allowing duplicates is the point RMS raised about a
command history.
Could you show me what I said, back then, about a command history? I
don't remember it, and it is not easy for me to look through a thread.
Clicking the link shows this:
There was one question left, if removing duplicates from history
should be turned on by default.
IMHO duplicates should be removed from history by default, most users
are more interested in the unique data present in history. If an exact
sequence of events is desired M-x list-command-history can do that.
[I reformated the last message from Stephan in that thread to make it
clear who said what]:
Dan> How about the default? Should this be turned on by default?
Juri> It seems reasonable to turn it on by default.
RMS> Absolutely not! It would be a great surprise, and it would mean
RMS> you could not look around at your error messages without changing
RMS> other buffers on the screen.
Stephan> Huh? I don't understand why removing duplicates from the history
Stephan> would ever have any such effect.
Stephan> Could you explain what use case you're thinking of ?
next prev parent reply other threads:[~2006-05-14 23:46 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 23:29 should search ring contain duplicates? Richard Stallman
2006-05-14 23:46 ` Drew Adams [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-03 0:54 Drew Adams
2006-05-03 7:27 ` Dan Nicolaescu
2006-05-03 8:26 ` Kim F. Storm
2006-05-03 12:48 ` Juri Linkov
2006-05-03 13:53 ` Kim F. Storm
2006-05-04 10:12 ` Kim F. Storm
2006-05-04 10:29 ` David Kastrup
2006-05-04 12:00 ` Stefan Monnier
2006-05-04 12:19 ` Kim F. Storm
2006-05-04 12:25 ` David Kastrup
2006-05-05 22:14 ` Richard Stallman
2006-05-05 23:55 ` Kim F. Storm
2006-05-06 8:00 ` Eli Zaretskii
2006-05-06 23:36 ` Richard Stallman
2006-05-07 20:41 ` Kim F. Storm
2006-05-04 16:05 ` Stuart D. Herring
2006-05-04 16:23 ` David Kastrup
2006-05-04 16:36 ` Stuart D. Herring
2006-05-04 21:55 ` Kim F. Storm
2006-05-09 20:47 ` Juri Linkov
2006-05-10 9:34 ` Kim F. Storm
2006-05-10 22:55 ` Juri Linkov
2006-05-11 10:08 ` Kim F. Storm
2006-05-14 23:29 ` Richard Stallman
2006-05-15 9:54 ` Kim F. Storm
2006-05-16 4:29 ` Richard Stallman
2006-05-16 11:07 ` Kim F. Storm
2006-05-03 14:18 ` Stefan Monnier
2006-05-03 14:25 ` Kim F. Storm
2006-05-03 14:40 ` Drew Adams
2006-05-03 15:54 ` Drew Adams
2006-05-03 20:27 ` Juri Linkov
2006-05-03 23:08 ` Drew Adams
2006-05-04 14:17 ` Richard Stallman
2006-05-04 15:07 ` Kim F. Storm
2006-05-04 22:44 ` Kim F. Storm
2006-05-05 19:05 ` Richard Stallman
2006-05-05 19:14 ` Drew Adams
2006-05-05 19:25 ` David Kastrup
2006-05-05 20:09 ` Drew Adams
2006-05-06 14:25 ` Richard Stallman
2006-05-05 23:22 ` Juri Linkov
2006-05-05 23:32 ` Kim F. Storm
2006-05-06 2:05 ` Drew Adams
2006-05-03 14:43 ` Dan Nicolaescu
2006-05-04 19:41 ` Richard Stallman
2006-05-03 20:42 ` Richard Stallman
2006-05-03 22:41 ` Dan Nicolaescu
2006-05-04 19:41 ` Richard Stallman
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=DNEMKBNJBGPAOPIJOOICKEBDDGAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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.