From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: Excluding command from history list
Date: Sat, 24 Jan 2015 15:21:00 +0000 [thread overview]
Message-ID: <20150124152100.GA20359@tarsus.local2> (raw)
In-Reply-To: <150123204755.ZM2095@torch.brasslantern.com>
Bart Schaefer wrote on Fri, Jan 23, 2015 at 20:47:55 -0800:
> On Jan 23, 12:32pm, Ramkumar Ramachandra wrote:
> }
> } I want to exclude
> } *dcommit* from the history list; excluding it from the history file is
> } pretty simple:
> }
> } zshaddhistory () {
> } [[ $1 != *dcommit* ]]
> } }
> }
> } ... but I haven't figured out how to do it for the history list
>
> That *does* exclude it from the history list.
>
> What it doesn't do (and what nothing does) is exclude it from being
> kept in what might be termed the "previous command buffer". You
> can ALWAYS go back exactly one command, even when HISTSIZE=0, but
> with the zshaddhistory hook above, that command will be discarded
> as soon as there is another new one to replace it.
You could partially workaround that feature by wrapping the
history-recalling commands with "don't recall dcommit" variants. For
example:
% bindkey -L | grep up
bindkey "^[[A" up-line-or-history
% f() {
local b="$BUFFER"
zle .up-line-or-history
[[ $BUFFER == *dcommit* ]] && BUFFER=": : :"
}
% zle -N f f
% bindkey '^[[A' f
That doesn't stop you from using '!' in an input line, e.g., '!?dcommit'
would still recall the 'git svn dcommit' command.
Daniel
prev parent reply other threads:[~2015-01-24 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 17:32 Ramkumar Ramachandra
2015-01-24 4:47 ` Bart Schaefer
2015-01-24 15:21 ` Daniel Shahaf [this message]
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=20150124152100.GA20359@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).