zsh-workers
 help / color / mirror / code / Atom feed
From: Jason Spiro <jasonspiro4@gmail.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>, ZyX <kp-pav@yandex.ru>,
	 "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: In Vi mode, show whether "insert" or "command" state is active
Date: Sun, 28 Dec 2014 22:43:29 -0500	[thread overview]
Message-ID: <CAN2X26kDy89OOCTTrLEf=Ptar+eSnES4+CryA43Hn3tZhuS2fw@mail.gmail.com> (raw)

On Fri, Dec 26, 2014 at 6:32 AM, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> I'm not sure the keymap name is the most useful indicator for the vi
> mode. local keymaps are not going to be indicated and keymaps like
> menuselect have a longer name. Subtler indicators like cursor
> shape/colour or something like the readline feature are perhaps more
> useful. In vim, I would never read the '-- INSERT --' indicator: it is
> a blob that appears in peripheral vision.

Hmmm.

In viins mode, you could show a bright-white '-- INSERT --' indicator
somewhere on screen.  (Last line, like Vim?  First line?)  In vicmd
mode, you could hide the indicator.  This way, you could take
advantage of users' peripheral vision to make them aware of which mode
they're in.

Or you could indicate the mode using cursor color, like Emacs Viper
does.  In insert mode, turn the cursor green.  In command mode, turn
the cursor back to its normal color.

Or you could do both.

ZyX wrote:
> in case of %z one should not assume only vicmd/viins: zle is not as limited as
> readline and theoretically allows any number of modes (have never seen them
> actually implemented though).

Other modes are so uncommonly used that you don't actually need to
bother identifying them.  (Optimize for the common case, not for
uncommon cases.)  But if you insist, you could change the '-- INSERT
--' indicator to '-- name_of_mode --' or something.


             reply	other threads:[~2014-12-29  3:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29  3:43 Jason Spiro [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-22  0:07 Fwd: " Jason Spiro
2014-12-22  1:57 ` Bart Schaefer
2014-12-22 18:25   ` Peter Stephenson
2014-12-22 18:44     ` Ray Andrews
2014-12-22 18:44   ` ZyX
2014-12-23  4:40     ` Bart Schaefer
2014-12-25  4:15     ` Jason Spiro
2014-12-25 20:34       ` ZyX
2014-12-25 23:18         ` Bart Schaefer
2014-12-26 11:32           ` Oliver Kiddle
2014-12-26 19:21             ` Bart Schaefer
2014-12-26 21:58               ` Christian Neukirchen
2014-12-27  0:31                 ` 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='CAN2X26kDy89OOCTTrLEf=Ptar+eSnES4+CryA43Hn3tZhuS2fw@mail.gmail.com' \
    --to=jasonspiro4@gmail.com \
    --cc=kp-pav@yandex.ru \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-workers@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).