From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Dan Nicolaescu <dann@ics.uci.edu>, emacs-devel@gnu.org
Subject: Re: avoid duplicates in history
Date: Fri, 04 Jun 2004 12:20:12 +0900 [thread overview]
Message-ID: <buou0xsf1qr.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <87llj4gguw.fsf@mail.jurta.org> (Juri Linkov's message of "Fri, 04 Jun 2004 06:08:23 +0300")
Juri Linkov <juri@jurta.org> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>> Feedback would be appreciated.
>
> I think this is a useful feature.
>
>> Is the history-erasedups name ok?
>
> There are similar variables `comint-input-ignoredups' and
> `eshell-hist-ignoredups', so it could be rather named as
> `history-ignoredups'.
>
> OTOH, by functionality it is very like `delete-dups' so the name
> `history-deletedups' is no worse.
Yes it is, it runs two words together for no reason. Just use
`history-delete-duplicates'.
-Miles
--
Occam's razor split hairs so well, I bought the whole argument!
next prev parent reply other threads:[~2004-06-04 3:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 17:00 avoid duplicates in history Dan Nicolaescu
2004-06-04 3:08 ` Juri Linkov
2004-06-04 3:20 ` Miles Bader [this message]
2004-06-04 16:29 ` Dan Nicolaescu
2004-06-04 19:32 ` Juri Linkov
2004-06-04 21:27 ` Dan Nicolaescu
2004-06-04 22:09 ` Juri Linkov
2004-06-05 22:50 ` Richard Stallman
2004-06-07 8:53 ` Stefan Monnier
2004-09-02 0:37 ` removing duplicate from history by default [was Re: avoid duplicates in history] Dan Nicolaescu
2004-09-02 19:02 ` Richard Stallman
2004-09-03 23:05 ` removing duplicate from history by default Juri Linkov
2004-09-05 17:58 ` Dan Nicolaescu
2004-09-07 3:43 ` Richard Stallman
2004-06-05 13:48 ` avoid duplicates in history Richard Stallman
2004-06-26 20:45 ` Juri Linkov
2004-06-28 2:23 ` 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
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=buou0xsf1qr.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=miles@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).