Zsh Mailing List Archive
Messages sorted by:
Re: up-arrow no longer works right
- X-seq: zsh-users 13945
- From: TjL <luomat@xxxxxxxxx>
- To: TjL <luomat@xxxxxxxxx>, Zsh Users List <zsh-users@xxxxxxxxxx>
- Subject: Re: up-arrow no longer works right
- Date: Fri, 20 Mar 2009 02:03:27 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=7KY6KV6t9yqO5lPdJ9gOb8A8lhumahIwnvlUCCin/uk=; b=f9LjeN8gK+U2NSENVNR+MY6YaiXka9QY4RyrJb8sTsYn0Ksvg1U6X9MYZuVO2nTbKG 8ihk8RF7E56/DU0CzgcDjtohn8EFtb8x+l3Xb5JfvDgGbtksNao/NCEg+ykLN7kiTE7c 0S1g2nqJ3dH7FJI6WpM7hIVUfvrkrkRXE5eKc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=fRL2J6d13iTHt31gFqRq/H9t6HE52gNW4ddrCYrd2fXF6o1nmJO0wU+AXchaNaS5M+ MxXiajAKD6eocuA2LHwkchVJzA0MhsxLhH3ebBAi1PZInWT8xiQkfyyJbsZfMHBLLSVA bEXxKIuY1t5KMjCekDyvvJuwSD2p03ZQSmZME=
- In-reply-to: <20090320024835.GA64103@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <d2ecb10b0903191838y68e1dfbbsa80289a52256eb2a@xxxxxxxxxxxxxx> <20090320024835.GA64103@xxxxxxxxxxxxxxxxxxxx>
On Thu, Mar 19, 2009 at 10:48 PM, Phil Pennock
> On 2009-03-19 at 21:38 -0400, TjL wrote:
>> The oddity is that sometimes (usually after exiting from ssh and/or
>> screen) zsh seems to "forget" that, and pressing the up-arrow will
>> just go back through my history line by line, ignoring what I have
>> already typed.
>> Usually at that point I just exit the shell and open a new one, but
>> I'd really like to be able to kick-start my existing session if
>> possible (especially when I've ssh'd somewhere).
>> Any ideas what might cause this and (more importantly) what I can do to fix it?
> Perhaps the cursor keys have been put into application mode and your
> terminal type isn't supporting them in that mode?
I don't know what that means :-/
> When things are working, if you run:
> print -n '\e[?1h'
> do they stop working?
> If you run "bindkey", you'll see two batches for the two sets of cursor
> keys; for me:
> "^[OA" up-line-or-history
> "^[OB" down-line-or-history
> "^[OC" forward-char
> "^[OD" backward-char
> "^[[A" up-line-or-history
> "^[[B" down-line-or-history
> "^[[C" forward-char
> "^[[D" backward-char
> If those two sets ^[O<foo> and ^[[<foo> differ then this might explain
> it. So, (1) bind both sets the same and (2) see if "stty sane" helps.
'stty sane' did not fix it
> And: print -n '\e[?1l'
that fixes it
Messages sorted by: