zsh-users
 help / color / mirror / code / Atom feed
From: Ligesh <myself@ligesh.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Separating <tab> and <C-i>
Date: Mon, 26 Jun 2006 12:54:42 +0530	[thread overview]
Message-ID: <20060626072442.GA11200@lxlabs.com> (raw)
In-Reply-To: <060625141715.ZM8662@torch.brasslantern.com>

On Sun, Jun 25, 2006 at 02:17:15PM -0700, Bart Schaefer wrote:
> On Jun 26,  1:47am, Ligesh wrote:
> } 
> }  I know historically <tab> was treated as <c-i> by terminal drivers
> 
> It has nothing to do with terminal drivers.  The definition of TAB in
> the ASCII character set is code point decimal 9, which corresponds to
> ctrl-I in the same way that backspace (8) is ctrl-H and newline (10)
> is ctrl-J.

 Yeah, I forgot. But does that mean zsh is actually processing the ascii value of the key pressed? So zsh has no means to know whether it was <tab> or <c-i>?

> 
> } but is there a way to map these keys to different actions?
> 
> Now *this* does have to do with terminal drivers, because you may be
> able to use the terminal driver to remap the character value(s) sent
> when you press a given key combination.  But that point pressing the
> keys "Ctrl" and "I" will no longer be sending a true ctrl-I character,
> and other applications may get confused.

 I have xmodmap, but that will play havoc with my entire system, and I will have reconfigure screen, vim, elinks and I don't know what else. But I guess that's the only way out. I will have to make the terminal driver send a different keystroke for <c-j> and <c-i>, the two keys I want changed from their ascii meaning.

 Thanks



  reply	other threads:[~2006-06-26  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 20:17 Ligesh
2006-06-25 21:17 ` Bart Schaefer
2006-06-26  7:24   ` Ligesh [this message]
     [not found]   ` <20060625223530.GA7971@lxlabs.com>
2006-06-27  2:46     ` Bart Schaefer
2006-06-27  8:34       ` Ligesh

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=20060626072442.GA11200@lxlabs.com \
    --to=myself@ligesh.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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).