From: S M <themolesbox@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Live Clock Causes Directory Flashing In URxvt & XTerm
Date: Thu, 12 Jun 2014 13:46:05 -1000 [thread overview]
Message-ID: <CAC=V-3LkjPsA6T62K8rCXhZwK1nUTnTP9E-htL9qhUAv17q62Q@mail.gmail.com> (raw)
In-Reply-To: <CAC=V-3L_WgUTrMD0tbjyknq-ab8MFm4WRrB4+QjGsBBWXVpHvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4331 bytes --]
I'm still a noob with all this and someone said to make my .zshrc section
like this now, I'm assuming is correct?
THANKS again! :)
# keys -----------------------------------------------------------------
#+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
typeset -A key
key[Home]=${terminfo[khome]}
key[End]=${terminfo[kend]}
key[Insert]=${terminfo[kich1]}
key[Delete]=${terminfo[kdch1]}
key[Up]=${terminfo[kcuu1]}
key[Down]=${terminfo[kcud1]}
key[Left]=${terminfo[kcub1]}
key[Right]=${terminfo[kcuf1]}
key[PageUp]=${terminfo[kpp]}
key[PageDown]=${terminfo[knp]}
# setup key accordingly
[[ -n "${key[Home]}" ]] && bindkey "${key[Home]}" beginning-of-line
[[ -n "${key[End]}" ]] && bindkey "${key[End]}" end-of-line
[[ -n "${key[Insert]}" ]] && bindkey "${key[Insert]}" overwrite-mode
[[ -n "${key[Delete]}" ]] && bindkey "${key[Delete]}" delete-char
[[ -n "${key[Up]}" ]] && bindkey "${key[Up]}" up-line-or-history
[[ -n "${key[Down]}" ]] && bindkey "${key[Down]}"
down-line-or-history
[[ -n "${key[Left]}" ]] && bindkey "${key[Left]}" backward-char
[[ -n "${key[Right]}" ]] && bindkey "${key[Right]}" forward-char
On Mon, Jun 9, 2014 at 4:05 PM, S M <themolesbox@gmail.com> wrote:
> Hi Frank & Bart,
>
> Thank you Bart, I've been able to get it better by making the time
> increase, but I'll try out the titlebar too.
>
> Frank I'm new to zsh and this is config from the distro livarp that is
> dead now that I copied from.
>
> At this point in time I'm still clueless with a lot of it.
>
> If it's not to much trouble can you please show me how you'd correct this
> keys section for any problems?
> I got a little of what you said before Frank, but don't quite fully
> understand?
>
>
> # keys -----------------------------------------------------------------
>
> typeset -A key
> key[Home]=${terminfo[khome]}
> key[End]=${terminfo[kend]}
> key[Insert]=${terminfo[kich1]}
> key[Delete]=${terminfo[kdch1]}
> key[Up]=${terminfo[kcuu1]}
> key[Down]=${terminfo[kcud1]}
> key[Left]=${terminfo[kcub1]}
> key[Right]=${terminfo[kcuf1]}
> key[PageUp]=${terminfo[kpp]}
> key[PageDown]=${terminfo[knp]}
> # setup key accordingly
>
> [[ -n "${key[Home]}" ]] && bindkey "${key[Home]}" beginning-of-line
> [[ -n "${key[End]}" ]] && bindkey "${key[End]}" end-of-line
> [[ -n "${key[Insert]}" ]] && bindkey "${key[Insert]}" overwrite-mode
> [[ -n "${key[Delete]}" ]] && bindkey "${key[Delete]}" delete-char
> [[ -n "${key[Up]}" ]] && bindkey "${key[Up]}"
> up-line-or-history
> [[ -n "${key[Down]}" ]] && bindkey "${key[Down]}"
> down-line-or-history
> [[ -n "${key[Left]}" ]] && bindkey "${key[Left]}" backward-char
> [[ -n "${key[Right]}" ]] && bindkey "${key[Right]}" forward-char
>
>
> Thank you both again...
>
> Cheers
>
>
> On Mon, Jun 9, 2014 at 6:02 AM, Bart Schaefer <schaefer@brasslantern.com>
> wrote:
>
>> On Jun 9, 2:50am, S M wrote:
>> }
>> } So as example, 'cd /etc/' then tap tab to see the directory, try this
>> in a
>> } directory with a small amount of directories, or open the term full
>> screen
>> } to see a huge directory, but play with it, and at that point the
>> terminal
>> } starts flashing.
>>
>> This is happening because the completion list gets erased and redrawn each
>> time there is a 'zle reset-prompt' call. This in turn happens because
>> zle doesn't know whether the prompt changed size (new number of lines,
>> etc.) since the last time it was repainted, and the completion listing
>> code is a pluggable module that doesn't know what else zle may have done,
>> so the only way they can collectively be sure to keep a clean display is
>> to do a full refresh.
>>
>> Consider putting the live clock in your terminal title bar instead of in
>> the prompt, or update it less than once per second as you've already
>> tried.
>>
>
>
prev parent reply other threads:[~2014-06-12 23:46 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
2014-06-09 16:02 ` Bart Schaefer
2014-06-10 2:05 ` S M
2014-06-12 23:46 ` S M [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='CAC=V-3LkjPsA6T62K8rCXhZwK1nUTnTP9E-htL9qhUAv17q62Q@mail.gmail.com' \
--to=themolesbox@gmail.com \
--cc=schaefer@brasslantern.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).