From: Thomas Dickey <dickey@radix.net>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] slang v.s. ncurses
Date: Mon, 5 Sep 2005 06:16:16 -0400 [thread overview]
Message-ID: <20050905101616.GA21255@saltmine.radix.net> (raw)
In-Reply-To: <AB061826FE6135FCBE559295@[10.0.0.1]>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
On Mon, Sep 05, 2005 at 07:47:17AM +0100, Tavis Ormandy wrote:
>
>
> --On Monday, September 05, 2005 14:41:45 +0900 Georgi Georgiev
> <chutz@gg3.net> wrote:
> > key sequence works fine with my slang-linked mutt, but it
> > does not with a ncurses-linked mutt. I am aware what Control-S is
> > supposed to do historically.
>
> stty stop undef
that's simple. I would have pointed out that ncurses can use a different
mode (start by "man raw"), but that mutt is using a particular mode presumably
for a good reason.
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
[-- Attachment #2: Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2005-09-05 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 5:41 [gentoo-dev] slang v.s. ncurses Georgi Georgiev
2005-09-05 6:47 ` Tavis Ormandy
2005-09-05 8:01 ` Georgi Georgiev
2005-09-05 10:16 ` Thomas Dickey [this message]
2005-09-05 11:51 ` Georgi Georgiev
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=20050905101616.GA21255@saltmine.radix.net \
--to=dickey@radix.net \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox