unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Defun Self Documentation
Date: Fri, 06 Nov 2020 17:48:25 +0200	[thread overview]
Message-ID: <83a6vu8p12.fsf@gnu.org> (raw)
In-Reply-To: <AM0PR05MB6531DA3357DF64478BFA1E55B4ED0@AM0PR05MB6531.eurprd05.prod.outlook.com> (message from Anders Munch on Fri, 6 Nov 2020 15:33:27 +0000)

> From: Anders Munch <ajm@flonidan.dk>
> Date: Fri, 6 Nov 2020 15:33:27 +0000
> 
> Eli Zaretskii wrote:
> > Thanks for explaining your reasoning, but let's not forget that setting that to zero has a downside: if one types fast, it will slow down redisplay by delaying the response to the typing.
> 
> There is less work to do because it happens 0.125 seconds later?

No, because with zero value it happens immediately, and the extra work
required to show the overlay will slow down Emacs.

The display of the overlays to show the matching parentheses works
with an idle timer, and that value is the amount of time Emacs should
be idle before the parentheses are highlighted.  If you time fast,
Emacs will never be idle for that much time, so the parentheses will
not be highlighted while typing.  If you set the value to zero, the
parentheses will be highlighted no matter how fast you type, so Emacs
becomes less responsive to your typing.

> > But of course, this is personal, which is why it is a user option.
> 
> Sure, but we were talking about the default, and the 0.1 seconds is an actual
> scientific result.

I'm not sure the 0.1 number is relevant to this feature.  We are not
talking about the reaction time, we are talking about the shortest
time that indicates the user stopped typing.



  reply	other threads:[~2020-11-06 15:48 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 15:33 Defun Self Documentation Anders Munch
2020-11-06 15:48 ` Eli Zaretskii [this message]
2020-11-06 16:07   ` Christopher Dimech
2020-11-09  4:08   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  4:26     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  4:39       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  5:24         ` Beyond Kind Communication Corwin Brust
2020-11-09 13:32         ` Defun Self Documentation Eric S Fraga
2020-11-11 15:34           ` Michael Heerdegen
2020-11-09 15:51         ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2020-11-06  9:10 Anders Munch
2020-11-06 11:58 ` Eli Zaretskii
2020-11-05 15:16 Christopher Dimech
2020-11-05 15:45 ` tomas
2020-11-05 15:55   ` Christopher Dimech
2020-11-05 16:00     ` tomas
2020-11-05 16:10       ` Christopher Dimech
2020-11-05 18:08       ` Jean Louis
2020-11-05 19:34         ` Christopher Dimech
2020-11-05 16:15     ` Drew Adams
2020-11-05 16:41     ` Stefan Monnier
2020-11-05 16:51       ` Arthur Miller
2020-11-05 16:59         ` Christopher Dimech
2020-11-05 17:28         ` Stefan Monnier
2020-11-05 17:29     ` Michael Heerdegen
2020-11-05 17:50       ` Christopher Dimech
2020-11-05 19:35         ` Michael Heerdegen
2020-11-05 19:22     ` Joost Kremers
2020-11-05 19:38       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-05 19:50         ` Eli Zaretskii
2020-11-05 21:02           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06  5:27             ` Eli Zaretskii
2020-11-06  7:07               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06  7:18                 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06  7:45                   ` Eli Zaretskii
2020-11-06  8:17                     ` tomas
2020-11-06  8:38                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06  8:45                         ` tomas
2020-11-09  3:22                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06  8:44                     ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-11-06 11:54                       ` Eli Zaretskii
2020-11-06 12:12                         ` Christopher Dimech
2020-11-06 17:36                         ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-11-06 18:03                           ` Christopher Dimech
2020-11-09  3:49                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 18:39                           ` Eli Zaretskii
2020-11-09  4:00                             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  3:48                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  3:45                         ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-09  3:29                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-06 17:02               ` Stefan Monnier
2020-11-06 18:35                 ` Eli Zaretskii
2020-11-06 18:50                   ` Stefan Monnier
2020-11-06 19:07                     ` Christopher Dimech
2020-11-06 19:23                       ` Stefan Monnier
2020-11-06 19:41                         ` Christopher Dimech
2020-11-05 16:07 ` Drew Adams
2020-11-05 18:41   ` Emanuel Berg via Users list for the GNU Emacs text editor

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=83a6vu8p12.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).