From: Micah Elliott <mde@micahelliott.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: bindkey problem
Date: Thu, 22 May 2014 09:15:43 -0700 [thread overview]
Message-ID: <CAELbujqCVnjSHK13QimnmrMkZuNBKNrX0GKqx00Cw7EU_Ad5PA@mail.gmail.com> (raw)
In-Reply-To: <75CA7BD7-0251-421F-BADB-5A138950CCC8@me.com>
> why would you want to disable [^s / ^q]?
Good question. They're of historic utility (I don't find their default
pause/resume useful), and mostly just cause confusion when
accidentally pressed. Furthermore, it's great to free up a couple more
convenient/comfortable sequences. Traditionally, tools like screen and
tmux use ^a and ^b as their hotkeys. But those have terrible
collisions with emacs/vi bindings. I bind ^q for my tmux "prefix" and
love it. It's also very similar to reaching for vim's ^w window
bindings. Highly recommended tmux binding.
--
twitter:@MicahElliott | email:mde@MicahElliott.com | http://membean.com
Remember your words with Membean!
On Thu, May 22, 2014 at 7:00 AM, Akihiko Hohji <akhst7@me.com> wrote:
> Just curiosity, why would you want to disable these two blndkey ?
>
> AKi
>
>
> On May 22, 2014, at 12:25 AM, Manfred Lotz <manfred.lotz@yahoo.de> wrote:
>
>> On Wed, 21 May 2014 18:51:57 -0700
>> Micah Elliott <mde@micahelliott.com> wrote:
>>
>>> You might also need to do this:
>>>
>>> stty stop ''
>>> stty start ''
>>> stty -ixon
>>> stty -ixoff
>>>
>>> (from https://coderwall.com/p/ltiqsq)
>>>
>>> But maybe that's what no_flow_control is effectively doing.
>>>
>>
>> Yes, probably as no_flow_control was sufficient to turn it off. No additional stty
>> commands required.
>>
>> --
>> Thanks, Manfred
>
next prev parent reply other threads:[~2014-05-22 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 19:48 Manfred Lotz
2014-05-21 20:28 ` Frank Terbeck
2014-05-22 1:51 ` Micah Elliott
2014-05-22 4:25 ` Manfred Lotz
2014-05-22 14:00 ` Akihiko Hohji
2014-05-22 16:15 ` Micah Elliott [this message]
2014-05-22 4:24 ` Manfred Lotz
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=CAELbujqCVnjSHK13QimnmrMkZuNBKNrX0GKqx00Cw7EU_Ad5PA@mail.gmail.com \
--to=mde@micahelliott.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).