zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: S M <themolesbox@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: Live Clock Causes Directory Flashing In URxvt & XTerm
Date: Mon, 09 Jun 2014 15:19:09 +0200	[thread overview]
Message-ID: <8761kadxv6.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <CAC=V-3LOe8RhuxmypJvg1-9+xCrm2og8Bodh2JQUeCsrt02GnQ@mail.gmail.com> (S. M.'s message of "Mon, 9 Jun 2014 02:50:06 -1000")

Hi,

I can't say much about the problem you're describing, but I've spotting
something in your setup, that I thought I might mention:

S. M. wrote:
[...]

You do this for keyboard setup:

> typeset -A key
> key[Home]=${terminfo[khome]}
[...]

> [[ -n "${key[Home]}"    ]]  && bindkey  "${key[Home]}"    beginning-of-line
[...]

That will only work reliably, if you also put the terminal you're using
into keyboard-transmit mode while the line editor (ZLE) is active. You
can do that like this:

#+BEGIN_SRC shell
if (( ${+terminfo[smkx]} )) && (( ${+terminfo[rmkx]} )); then

    # If these entries are not  available for a given terminal, then
    # that terminal  is in  keyboard-transmit mode by  default. That
    # means, everything  is well  without any additional  action. If
    # not, this can do the trick:

    function zle-line-init () {
        echoti smkx
    }

    function zle-line-finish () {
        echoti rmkx
    }

    zle -N zle-line-init
    zle -N zle-line-finish

fi
#+END_SRC


Regards, Frank

-- 
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
                                                  -- RFC 1925


  reply	other threads:[~2014-06-09 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 12:50 S M
2014-06-09 13:19 ` Frank Terbeck [this message]
2014-06-09 16:02 ` Bart Schaefer
2014-06-10  2:05   ` S M
2014-06-12 23:46     ` S M

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=8761kadxv6.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=themolesbox@gmail.com \
    --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).