From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: shared history but recalling history in current terminal
Date: Sat, 30 Nov 2013 11:07:07 -0800 [thread overview]
Message-ID: <131130110707.ZM27442@torch.brasslantern.com> (raw)
In-Reply-To: =?iso-8859-1?Q?=3C5299C600=2E8040508=40necoro=2Eeu=3E?= =?iso-8859-1?Q?Comments=3A_In_reply_to_Ren=E9_'Necoro'_Neumann_=3Clists?= =?iso-8859-1?Q?=40necoro=2Eeu=3E?= =?iso-8859-1?Q?________=22Re=3A_shared_history_but_recalling_history_in_c?= =?iso-8859-1?Q?urrent_terminal=22_=28Nov_30=2C_12=3A03pm=29?=
On Nov 30, 12:03pm, René 'Necoro' Neumann wrote:
}
} Perhaps one could add a zle-isearch-init widget? Strikes me odd, that
} there isn't one.
Yes, one could ... one could also turn the isearch actions into real
widgets and truly select the isearch keymap ... but which "one"?
The whole family of automatically-invoked widgets is a (relatively)
recent thing, and they were added in a very ad-hoc way (hence we have
"zle-line-finish" but "zle-isearch-exit").
I'm sure there are various side-effects that haven't been thought out;
e.g., if you start playing with up/down history or modifying $BUFFER
from inside zle-isearch-update, all sorts of oddness probably results.
next prev parent reply other threads:[~2013-11-30 19:07 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
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 [this message]
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=131130110707.ZM27442@torch.brasslantern.com \
--to=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).