From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] uemacs doesn't clear ixon termios flag?
Date: Wed, 25 Apr 2012 20:55:49 +0000 (UTC) [thread overview]
Message-ID: <jn9ock$htn$1@dough.gmane.org> (raw)
In-Reply-To: jn91fg$mt2$1@dough.gmane.org
On 2012-04-25, Grant Edwards <grant.b.edwards@gmail.com> wrote:
> I've enabled the uemacs package. It builds fine, but it doesn't seem
> to work unless you manually clear the termios ixon flag before running
> it. If you don't do that, the Ctrl-S keystroke isn't seen by uemacs
> -- instead it's intercepted by the tty layer and stops terminal
> output until you hit Ctrl-Q.
This appears to be bug in uemacs that's been known about for several
years. The fix below is from the busybox mailing list 3 years ago
http://lists.busybox.net/pipermail/busybox/2009-February/068304.html:
Or you could install this one:
ftp://ftp.kernel.org/pub/software/editors/uemacs/em-4.0.15-lt.tar.bz2
but beware that this version also has a problem with ^S/^Q because
it doesn't clear IXON. You'll need the following patch before ^S/^Q
will work at all:
--- posix.c 2009/02/01 13:31:09 1.1
+++ posix.c 2009/02/01 13:32:12
@@ -51,6 +51,7 @@
/* raw CR/NL etc input handling, but keep ISTRIP if we're on a 7-bit line */
ntermios.c_iflag &= ~(IGNBRK | BRKINT | IGNPAR | PARMRK
| INPCK | INLCR | IGNCR | ICRNL);
+ ntermios.c_iflag &= ~IXON;
/* raw CR/NR etc output handling */
ntermios.c_oflag &= ~(OPOST | ONLCR | OLCUC | OCRNL | ONOCR | ONLRET);
If I submitted a patch and a modified uemacs.mk would it likely be
accepted?
--
Grant Edwards grant.b.edwards Yow! HELLO, everybody,
at I'm a HUMAN!!
gmail.com
next prev parent reply other threads:[~2012-04-25 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 14:24 [Buildroot] uemacs doesn't clear ixon termios flag? Grant Edwards
2012-04-25 20:55 ` Grant Edwards [this message]
2012-05-01 22:07 ` Peter Korsgaard
2012-05-01 23:51 ` Grant Edwards
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='jn9ock$htn$1@dough.gmane.org' \
--to=grant.b.edwards@gmail.com \
--cc=buildroot@busybox.net \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.