From: Micah Elliott <mde@micahelliott.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: bindkey problem
Date: Wed, 21 May 2014 18:51:57 -0700 [thread overview]
Message-ID: <CAELbujruX=TaA0MkXdRuT4sSCCqKdp3QEqYRSWbHi5TEndJVpw@mail.gmail.com> (raw)
In-Reply-To: <87zjia3mhq.fsf@ft.bewatermyfriend.org>
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.
--
twitter:@MicahElliott | email:mde@MicahElliott.com | http://membean.com
Remember your words with Membean!
next prev parent reply other threads:[~2014-05-22 1:52 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 [this message]
2014-05-22 4:25 ` Manfred Lotz
2014-05-22 14:00 ` Akihiko Hohji
2014-05-22 16:15 ` Micah Elliott
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='CAELbujruX=TaA0MkXdRuT4sSCCqKdp3QEqYRSWbHi5TEndJVpw@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).