From: Eli Zaretskii <eliz@gnu.org>
To: dickey@his.com
Cc: 17497@debbugs.gnu.org
Subject: bug#17497: 24.4.50; TTY menu glitches
Date: Sun, 01 Jun 2014 21:45:07 +0300 [thread overview]
Message-ID: <834n04bhak.fsf@gnu.org> (raw)
In-Reply-To: <20140601171817.GB9362@aerie.jexium-island.net>
> Date: Sun, 01 Jun 2014 13:18:17 -0400
> From: Thomas Dickey <dickey@his.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, 17497@debbugs.gnu.org
>
> What ncurses does when it's getting behind is to drop updates - the
> typeahead feature:
>
> The curses library does ``line-breakout optimization'' by looking for
> typeahead periodically while updating the screen. If input is found,
> and it is coming from a tty, the current update is postponed until re-
> fresh or doupdate is called again. This allows faster response to com-
> mands typed in advance. Normally, the input FILE pointer passed to
> newterm, or stdin in the case that initscr was used, will be used to do
> this typeahead checking. The typeahead routine specifies that the file
> descriptor fd is to be used to check for typeahead instead. If fd is
> -1, then no typeahead checking is done.
So buffering output more aggressively could help, is that what you are
saying?
We currently fflush the stream every 900 bytes and also every 10
screen lines or so. Does that sound reasonable?
next prev parent reply other threads:[~2014-06-01 18:45 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83vbslbuqr.fsf@gnu.org>
[not found] ` <20140531200947.GA779@aerie.jexium-island.net>
[not found] ` <83lhtgbrd6.fsf@gnu.org>
[not found] ` <20140601152657.GA15078@aerie.jexium-island.net>
2014-06-01 16:25 ` bug#17497: 24.4.50; TTY menu glitches Eli Zaretskii
2014-06-01 17:12 ` Thomas Dickey
2014-06-01 17:18 ` Thomas Dickey
2014-06-01 18:45 ` Eli Zaretskii [this message]
2014-06-01 19:46 ` Thomas Dickey
2014-06-02 15:17 ` Eli Zaretskii
2014-06-02 16:14 ` Glenn Morris
2014-06-02 16:43 ` Eli Zaretskii
2014-06-02 16:46 ` Glenn Morris
2014-06-02 16:56 ` Eli Zaretskii
2014-06-02 17:05 ` Glenn Morris
2014-06-03 13:43 ` Stefan Monnier
2014-06-03 18:47 ` Thomas Dickey
2014-06-03 21:07 ` Eli Zaretskii
2014-06-03 22:21 ` Thomas Dickey
2014-06-04 6:54 ` Eli Zaretskii
2014-06-04 3:03 ` Stefan Monnier
2014-06-04 8:31 ` Thomas Dickey
2014-06-04 9:10 ` Thomas Dickey
2014-06-04 9:38 ` Eli Zaretskii
2014-06-04 10:16 ` Eli Zaretskii
2014-06-04 16:08 ` Glenn Morris
2014-06-04 16:15 ` Eli Zaretskii
2014-06-04 16:09 ` Glenn Morris
2014-06-04 16:23 ` Eli Zaretskii
2014-06-04 17:10 ` Eli Zaretskii
2014-06-04 13:06 ` Stefan Monnier
2014-06-04 20:26 ` Thomas Dickey
2014-06-05 0:47 ` Stefan Monnier
2014-06-05 8:21 ` Thomas Dickey
2014-06-05 8:29 ` Andreas Schwab
2014-06-05 15:02 ` Eli Zaretskii
2014-06-05 13:44 ` Stefan Monnier
2014-06-05 13:47 ` Stefan Monnier
2014-06-05 15:00 ` Eli Zaretskii
2014-06-01 18:39 ` Eli Zaretskii
2014-05-15 12:26 Dmitry Antipov
2014-05-15 17:37 ` Eli Zaretskii
2014-05-16 6:36 ` Glenn Morris
2014-05-16 6:38 ` Glenn Morris
2014-05-16 6:53 ` Glenn Morris
2014-05-16 8:48 ` Eli Zaretskii
2014-05-16 15:47 ` Glenn Morris
2014-05-16 20:21 ` Eli Zaretskii
2014-05-17 9:56 ` Eli Zaretskii
2014-05-22 2:49 ` Eli Zaretskii
2014-05-22 5:44 ` Glenn Morris
2014-05-22 7:51 ` Andreas Schwab
2014-05-22 15:58 ` Glenn Morris
2014-05-22 17:19 ` Andreas Schwab
2014-05-22 17:29 ` Glenn Morris
2014-05-22 17:53 ` Eli Zaretskii
2014-05-22 16:19 ` Eli Zaretskii
2014-05-22 16:26 ` Glenn Morris
2014-05-22 16:46 ` Eli Zaretskii
2014-05-30 9:22 ` Eli Zaretskii
2014-05-31 2:22 ` Glenn Morris
2014-05-31 8:20 ` Eli Zaretskii
2014-05-31 17:35 ` Glenn Morris
2014-06-01 15:11 ` Eli Zaretskii
2014-06-03 4:51 ` Glenn Morris
2014-06-03 7:03 ` Eli Zaretskii
2014-05-22 16:43 ` Eli Zaretskii
2014-05-22 16:54 ` Glenn Morris
2014-05-22 17:07 ` Eli Zaretskii
2014-05-16 9:42 ` Dmitry Antipov
2014-05-16 10:26 ` Eli Zaretskii
2014-05-16 10:46 ` Eli Zaretskii
2014-05-16 14:59 ` Dmitry Antipov
2014-05-16 15:26 ` Eli Zaretskii
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=834n04bhak.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=17497@debbugs.gnu.org \
--cc=dickey@his.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.