From: Eli Zaretskii <eliz@gnu.org>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Add option to remove duplicate command history entries
Date: Thu, 04 Jun 2015 19:25:00 -0000 [thread overview]
Message-ID: <83sia7p97u.fsf@gnu.org> (raw)
In-Reply-To: <CA+C-WL8_HGSwiO5qWTw3rhYgCF0hwe5G2FzRk1xOwPaPJ6RGHw@mail.gmail.com>
> 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.
next prev parent reply other threads:[~2015-06-04 19:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 16:22 Patrick Palka
2015-06-04 16:47 ` Eli Zaretskii
2015-06-04 18:54 ` Patrick Palka
2015-06-04 19:25 ` Eli Zaretskii [this message]
2015-06-09 18:10 ` Pedro Alves
2015-06-09 18:41 ` Patrick Palka
2015-06-10 15:12 ` Pedro Alves
2015-06-19 23:33 ` Patrick Palka
2015-06-20 6:52 ` Eli Zaretskii
2015-06-26 13:35 ` Patrick Palka
2015-06-26 14:18 ` Pedro Alves
2015-06-26 14:30 ` Patrick Palka
2015-06-26 14:50 ` Pedro Alves
2015-06-26 15:12 ` Patrick Palka
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=83sia7p97u.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=patrick@parcs.ath.cx \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox