zsh-users
 help / color / mirror / code / Atom feed
From: Steve Dondley <s@dondley.com>
To: Zsh users <zsh-users@zsh.org>
Subject: Re: How do I disable the mode for using j-k keys to scroll through history?
Date: Tue, 15 Mar 2022 20:21:56 -0400	[thread overview]
Message-ID: <1a9eb11345a54293cd18ba084cb23e16@dondley.com> (raw)
In-Reply-To: <3b61b4343181cb58d9ff6f71905666d9@dondley.com>

On 2022-03-15 06:38 PM, Steve Dondley wrote:
> I've been using zsh with oh-my-zsh for several months now with vi
> commands. Frequently, the command line seems to "lock up" and become
> unresponsive to input. I chalked it up to some kind of bug, hit
> ctrl-c, and moved on.
> 
> I finally just figured out that I had somehow entered some special
> mode that activates the "j" and "k" keys to pull up prev/next
> commands. Through trial and error, I discovered the <esc> key triggers
> this mode and the "s" key gets out of it.
> 
> Haven't figured out how to disable this feature. Google has turned up
> nothing useful after 10 min. of searching. Any ideas?

Heh, so it just dawned on me the big cause for all my mental confusion 
was that I considered "insert" mode to be "normal" mode on the command 
line. And then whenever I hit the <esc> key to do "normal" mode 
operations, I actually thought of that as some special "vim" mode and I 
never gave it much thought. I never stopped to realize I was always in 
vim "insert mode" the whole time I was typing into the command line and 
then going to "normal" mode when I hit escape.

And I have my caps lock keys doubles as a control key and escape key and 
I also double tap the caps lock/control key for a hot key. So if i 
mistyped, it would throw me into normal mode without me realizing it.

Anyway, after months of wondering what the hell was going on, mystery 
solved.

Thanks for the hand helping me figure this out.



      parent reply	other threads:[~2022-03-16  0:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-15 22:38 Steve Dondley
2022-03-15 22:46 ` Bart Schaefer
2022-03-15 22:55   ` Steve Dondley
2022-03-15 22:57     ` Steve Dondley
2022-03-15 23:24       ` Steve Dondley
2022-03-15 23:25       ` Bart Schaefer
2022-03-15 23:27       ` Lawrence Velázquez
2022-03-15 23:57         ` Steve Dondley
2022-03-15 23:59           ` Bart Schaefer
2022-03-15 23:24     ` Lawrence Velázquez
2022-03-15 23:47   ` Steve Dondley
2022-03-16  0:21 ` Steve Dondley [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=1a9eb11345a54293cd18ba084cb23e16@dondley.com \
    --to=s@dondley.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).