Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: About insert-last-word and "command args | less"
- X-seq: zsh-users 10877
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: About insert-last-word and "command args | less"
- Date: Sat, 14 Oct 2006 21:04:51 -0700
- In-reply-to: <20061015005019.GJ28997@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20061014115617.GA28997@xxxxxxxxxxxxxxxxxxx> <061014142741.ZM22567@xxxxxxxxxxxxxxxxxxxxxx> <20061015005019.GJ28997@xxxxxxxxxxxxxxxxxxx>
On Oct 15, 2:50am, Vincent Lefevre wrote:
}
} Thanks, but this is buggy with setopt HIST_IGNORE_DUPS:
Hrm. It's not *just* HIST_IGNORE_DUPS, because it works fine as long
as you're not inserting the word in command position. In fact, it
works fine as long as $BUFFER is not empty when you begin using it.
This implies that the bug is in one of up-history or down-history.
smart-insert-last-word sets NUMERIC and assumes that thereafter a
call to .up-history followed by one to .down-history will return the
editor to the current line. This appears not to work when $BUFFER
starts out empty and there are duplicate history items to skip.
The simple workaround is to change
setopt extendedglob
to
setopt extendedglob nohistignoredups
in smart-insert-last-word, on the second line.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author