This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add option to remove duplicate command history entries
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Patrick Palka <patrick at parcs dot ath dot cx>
- Cc: gdb-patches at sourceware dot org
- Date: Thu, 04 Jun 2015 22:25:09 +0300
- Subject: Re: [PATCH] Add option to remove duplicate command history entries
- Authentication-results: sourceware.org; auth=none
- References: <1433434918-30948-1-git-send-email-patrick at parcs dot ath dot cx> <83y4jzpgj6 dot fsf at gnu dot org> <CA+C-WL8_HGSwiO5qWTw3rhYgCF0hwe5G2FzRk1xOwPaPJ6RGHw at mail dot gmail dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Patrick Palka <patrick@parcs.ath.cx>
> Date: Thu, 4 Jun 2015 14:53:40 -0400
> Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
>
> >> +@cindex remove duplicate history
> >> +@kindex set history remove-duplicates
> >> +@item set history remove-duplicates
> >> +@itemx set history remove-duplicates on
> >> +Remove duplicate history entries added during the current session. Before a
> >
> > Given the description below, this summary is slightly misleading,
> > IMO. Why not simply
> >
> > Keep in history of CLI commands only one copy of each command.
>
> How about I rewrite this section into:
>
> Keep in the command history list only one copy of each command. If a new
> command being added to the history list is a duplicate of an older one, the
> older entry is removed from the list. Only history entries added during the
> current session are considered for removal. This option is off by default.
Perfect, thanks.