Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org, patrick@parcs.ath.cx
Subject: Re: [PATCH] Add option to remove duplicate command history entries
Date: Sat, 20 Jun 2015 06:52:00 -0000	[thread overview]
Message-ID: <83egl6kh2u.fsf@gnu.org> (raw)
In-Reply-To: <1434756821-7423-1-git-send-email-patrick@parcs.ath.cx>

> From: Patrick Palka <patrick@parcs.ath.cx>
> Cc: Patrick Palka <patrick@parcs.ath.cx>
> Date: Fri, 19 Jun 2015 19:33:41 -0400
> 
> This patch implements the new option "history remove-duplicates", which
> controls the removal of duplicate history entries ("off" by default).
> 
> The motivation for this option is to be able to reduce the prevalence of
> basic commands such as "up" and "down" in the history file.  These
> common commands crowd out more unique commands in the history file (when
> the history file has a fixed size), and they make navigation of the
> history file via ^P, ^N and ^R more inconvenient.
> 
> The option takes an integer denoting the number of history entries to
> look back at for a history entry that is a duplicate of the latest one.
> "history remove-duplicates 1" is equivalent to bash's ignoredups option,
> and "history remove-duplicates unlimited" is equivalent to bash's
> erasedups option.
> 
> [ I decided to go with this integer approach instead of a tri-state enum
>   because it's slightly more flexible and seemingly more intuitive than
>   leave/erase/ignore.  ]
> 
> gdb/ChangeLog:
> 
> 	* NEWS: Mention the new option "history remove-duplicates".
> 	* top.c (history_remove_duplicates): New static variable.
> 	(show_history_remove_duplicates): New static function.
> 	(gdb_add_history): Conditionally remove duplicate history
> 	entries.
> 	(init_main): Add "history remove-duplicates" option.
> 
> gdb/doc/ChangeLog:
> 
> 	* gdb.texinfo (Command History): Document the new option
> 	"history remove-duplicates".
> 
> gdb/testsuite/ChangeLog:
> 
> 	* gdb.base/history-duplicates.exp: New test.

OK for the documentation parts.

Thanks.


  reply	other threads:[~2015-06-20  6:52 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
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 [this message]
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=83egl6kh2u.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