Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Prune duplicate command history entries
Date: Wed, 03 Jun 2015 08:20:00 -0000	[thread overview]
Message-ID: <20150603082036.GR17330@embecosm.com> (raw)
In-Reply-To: <1433301766-20101-1-git-send-email-patrick@parcs.ath.cx>

* Patrick Palka <patrick@parcs.ath.cx> [2015-06-02 23:22:46 -0400]:

> This patch implements pruning of duplicate command-history entries using
> a modest amount of lookbehind.  The motivation for this patch is to
> reduce the prevalence of basic commands such as "up" and "down" in the
> history file.

Dropping commands such as up / down could be pretty annoying if you
wanted to figure out where you were in the past. Dropping things like
bt from the history would be less annoying.

I wonder if we should classify commands into navigation or
state-changing commands and diagnostic commands.
I'd be happier see repeated diagnostic commands disappear, and less so
for commands that change inferior state, or navigate me around the
stack.

> The maximum lookbehind is fixed to 50 (an arbitrary number) so that the
> operation will be guaranteed to not take too long.

I think at the very least you should make this threshold
configurable.  I'd then argue for off by default due to the loss of
state changing commands being too annoying (for me).

You should probably have some tests too, we already test C-p in
readline.exp, so it should be possible to test that this feature
works.

Thanks,
Andrew


  reply	other threads:[~2015-06-03  8:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:22 Patrick Palka
2015-06-03  8:20 ` Andrew Burgess [this message]
2015-06-03 14:16   ` Patrick Palka
2015-06-03 17:42     ` Andrew Burgess
2015-06-03 17:10   ` Joel Brobecker

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=20150603082036.GR17330@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --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