zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Vimode problem (key press dropping)
Date: Wed, 29 Jul 2015 10:49:53 -0700	[thread overview]
Message-ID: <150729104953.ZM10383@torch.brasslantern.com> (raw)
In-Reply-To: <12757.1438188328@thecus.kiddle.eu>

On Jul 29,  6:45pm, Oliver Kiddle wrote:
}
} We could alleviate this issue by binding a few more keys by default at
} startup. Insert, Delete, Home, End, Page Up/Dn and the function keys
} all have termcap entries. Is there really a good reason not to bind at
} least the first four of these. What was the historical reason for not
} doing so?

Different terminals send different sequences for the same keys.  Also
you have to worry about whether the terminal is in keypad transmit mode
or not.  And the "same" terminal can behave differently when it's on
the far end of an ssh connection vs. when it's in a local console or
locally-running emulator.

So none of this can be hardwired, and it's a mess to calculate based on
the terminfo definition.  Duplicating the effort that programs like vim
and emacs go through to make this work has always seemed like overkill
for what's supposed to be a simple editor with minimal screen management.

This is why zkbd exists.

} Also, anyone know why the sequences for the cursors need to be
} passed through tputs()?

Some attempt to handle the keypad-transmit issue, I suspect.  I don't
recall; I think Wayne did the most recent work here, but I may be wrong
about that too.

} I also wonder whether we should consider trying to do something for
} Ctrl/Alt Left and Right to make it easier for new users.

A fair number of the terminals I use don't differentiate those modifier
keys in any useful way except when combining with non-alphabetics (and in
some caes not even then for e.g. the meta key).  My feeling has always
been that it's not a good idea to promise things we can't deliver.


  reply	other threads:[~2015-07-29 17:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  5:17 alx741
2015-07-29  9:26 ` Oliver Kiddle
2015-07-29 12:35   ` Mikael Magnusson
2015-07-29 15:30     ` Bart Schaefer
2015-07-29 15:35       ` Mikael Magnusson
2015-07-29 15:51         ` Bart Schaefer
2015-07-29 16:31           ` Mikael Magnusson
2015-07-29 16:45         ` Oliver Kiddle
2015-07-29 17:49           ` Bart Schaefer [this message]
2015-07-29 17:53             ` Bart Schaefer
2015-07-29 18:32   ` alx741

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=150729104953.ZM10383@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).