unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 57727@debbugs.gnu.org
Subject: bug#57727: 29.0.50; Optimize tty display updates
Date: Tue, 13 Sep 2022 09:48:39 -0400	[thread overview]
Message-ID: <jwvbkrj5r36.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m2a673yg44.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Tue, 13 Sep 2022 07:53:47 +0200")

Gerd Möllmann [2022-09-13 07:53:47] wrote:
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> 1. Multi-tty make me feel it's natural to make the behavior terminal
>>> dependent.  At least I don't consider unreasonable for a user to expect
>>> being able to tailor the behavior depending on the terminal.
>>
>> I guess the reason why I think it's over-engineered is that I feel it's
>> not something which end-users will want to play with or configure
>> per-terminal: we should have a setting that works well everywhere.
>
> I really good default would indeed be a Good Thing.  But, on the other
> hand, I think it's not likely that we find something that works for
> everyone all the time.

Really?  AFAICT noone has complained about the existing behavior (the
change under discussion was prompted by looking at the code, no?), so
what we currently have seems to work quite well "for everyone all the time".

> As far as the OS default goes (1024 on my system), I don't think I agree
> completely.  A frame on a full-size terminal window has a width of
> ca. 380 columns, which is a bit much for a buffer of 1024.

I tend to agree that 1kB sounds a bit small (from a network perspective,
I'd expect >1.5kB, to fill a typical Ethernet frame) but whether it
matters or not really depends how the "per packet" vs "per byte"
overheads compare.


        Stefan






  parent reply	other threads:[~2022-09-13 13:48 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-11 10:03 bug#57727: 29.0.50; Optimize tty display updates Gerd Möllmann
2022-09-11 11:18 ` Lars Ingebrigtsen
2022-09-12  6:02   ` Gerd Möllmann
2022-09-12 11:21     ` Eli Zaretskii
2022-09-11 13:49 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-12  6:33   ` Gerd Möllmann
2022-09-12 11:29     ` Eli Zaretskii
2022-09-12 11:52       ` Gerd Möllmann
2022-09-12 13:15         ` Gerd Möllmann
2022-09-12 14:18     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-13  5:53       ` Gerd Möllmann
2022-09-13 11:33         ` Eli Zaretskii
2022-09-13 11:36           ` Lars Ingebrigtsen
2022-09-13 12:44             ` Gerd Möllmann
2022-09-13 13:48         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-09-13 13:53           ` Gerd Möllmann
2022-09-17 13:34 ` Gerd Möllmann
2022-09-17 21:09 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-18  5:34   ` Gerd Möllmann

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvbkrj5r36.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57727@debbugs.gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).