This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Prune duplicate command history entries
- From: Andrew Burgess <andrew dot burgess at embecosm dot com>
- To: Patrick Palka <patrick at parcs dot ath dot cx>
- Cc: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Wed, 3 Jun 2015 18:42:36 +0100
- Subject: Re: [PATCH] Prune duplicate command history entries
- Authentication-results: sourceware.org; auth=none
- References: <1433301766-20101-1-git-send-email-patrick at parcs dot ath dot cx> <20150603082036 dot GR17330 at embecosm dot com> <CA+C-WL9pVi_e9Uz2=6KRaWWaePYXDdAwSrPc3qbGwrfQs0z6QQ at mail dot gmail dot com>
* Patrick Palka <patrick@parcs.ath.cx> [2015-06-03 10:15:47 -0400]:
> Hmm, but doesn't the empty-command shorthand already make it mostly
> impossible to figure out where you were in the past? If you run "up"
> twice by typing "up\n\n" then only one history entry for "up" gets
> added to the history file (with or without the patch).
I confess I hadn't spotted that. Looking back through the history to
figure out what I've been doing isn't a common operation (thankfully).
I guess so long as the feature was switchable then I have little
objection.
Thanks,
Andrew