From: "René 'Necoro' Neumann" <lists@necoro.eu>
To: zsh-users@zsh.org
Subject: Re: shared history but recalling history in current terminal
Date: Wed, 27 Nov 2013 20:08:24 +0100 [thread overview]
Message-ID: <52964328.5040801@necoro.eu> (raw)
In-Reply-To: <131127000208.ZM18878@torch.brasslantern.com>
Am 27.11.2013 09:02, schrieb Bart Schaefer:
> On Nov 26, 10:31pm, Wayne Davison wrote:
>>
>> bindkey '^p' up-line-or-local-history
>>
>> up-line-or-local-history() {
>> zle set-local-history 1
>> zle up-line-or-history
>> zle set-local-history 0
>> }
>> zle -N up-line-or-local-history
>
> Another possibility is something like:
>
> zle-line-init() { zle set-local-history 1 }
> zle -N zle-line-init
>
> zle-keymap-select() {
> [[ $KEYMAP = isearch ]]
> zle set-local-history $?
> }
> zle -N zle-keymap-select
>
> Then incremental search is non-local history, everything else is local,
> and you don't have to re-create individual keybindings.
>
Unfortunately, this seems only to work when not doing a 'RETURN' without
command in a session, because then the other sessions are imported again:
S1>ls
S2>echo muh
S1>(UP) -> ls (ESC)
S1>(RETURN)
S1>(RETURN)
S1>(UP) -> echo muh
This seems to be not completely deterministic, in some cases it does not
happen.
I tried to debug the widgets you defined, but any 'echo' or 'zle -M' I
put in there was ignored.
- René
next prev parent reply other threads:[~2013-11-27 19:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 20:30 shawn wilson
2013-11-27 6:31 ` Wayne Davison
2013-11-27 8:02 ` Bart Schaefer
2013-11-27 13:49 ` shawn wilson
2013-11-27 15:11 ` Karoly Negyesi
2013-11-27 15:17 ` shawn wilson
2013-11-27 18:24 ` Bart Schaefer
2013-11-27 19:08 ` René 'Necoro' Neumann [this message]
2013-11-28 1:05 ` Bart Schaefer
2013-11-28 20:44 ` René 'Necoro' Neumann
2013-11-28 21:33 ` Bart Schaefer
2013-11-30 11:03 ` René 'Necoro' Neumann
2013-11-30 19:07 ` Bart Schaefer
2013-12-08 23:40 ` Jan Larres
2013-12-08 23:54 ` Jan Larres
2013-12-10 7:09 ` Bart Schaefer
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=52964328.5040801@necoro.eu \
--to=lists@necoro.eu \
--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).