public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Patrick Palka <patrick@parcs.ath.cx>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Prune duplicate command history entries
Date: Wed, 03 Jun 2015 17:42:00 -0000	[thread overview]
Message-ID: <20150603174236.GS17330@embecosm.com> (raw)
In-Reply-To: <CA+C-WL9pVi_e9Uz2=6KRaWWaePYXDdAwSrPc3qbGwrfQs0z6QQ@mail.gmail.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

  reply	other threads:[~2015-06-03 17:42 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
2015-06-03 14:16   ` Patrick Palka
2015-06-03 17:42     ` Andrew Burgess [this message]
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=20150603174236.GS17330@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).