From: Dan Nicolaescu <dann@ics.uci.edu>
To: Tom Tromey <tromey@redhat.com>
Cc: 1505@emacsbugs.donarmstrong.com
Subject: bug#1505: duplicate entries in compile-history
Date: Sat, 6 Dec 2008 09:50:17 -0800 (PST) [thread overview]
Message-ID: <200812061750.mB6HoGaL010867@mothra.ics.uci.edu> (raw)
In-Reply-To: <m3k5adwfxi.fsf@fleche.redhat.com> (Tom Tromey's message of "Sat, 06 Dec 2008 07:12:41 -0700")
Tom Tromey <tromey@redhat.com> writes:
> I ran into the following situation yesterday:
>
> I ran one compile command in the morning. Then, for the rest of the
> day, I ran a couple of different compile command, alternating them
> many times. Near the end of the day, I wanted to re-run the first
> command, but it had been removed from history.
>
> It would be nice if there were a way to eliminate duplicates from
> compile-history, so that older commands were not completely dropped.
> For instance, a command could still be put at the front of the list;
> but all duplicates of it elsewhere in the list could be removed at the
> same time.
C-h v history-delete-duplicate RET
history-delete-duplicates is a variable defined in `C source code'.
Its value is t
Documentation:
*Non-nil means to delete duplicates in history.
If set to t when adding a new history element, all previous identical
elements are deleted from the history list.
(inspired by tcsh's histdup)
This works on all histories, not only compile-history.
next prev parent reply other threads:[~2008-12-06 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 14:12 bug#1505: duplicate entries in compile-history Tom Tromey
2008-12-06 17:50 ` Dan Nicolaescu [this message]
2008-12-06 20:22 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2008-12-06 15:14 richardeng
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=200812061750.mB6HoGaL010867@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=1505@emacsbugs.donarmstrong.com \
--cc=tromey@redhat.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 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).