From: nljlistbox2@gmail.com (N. Jackson)
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 23377@debbugs.gnu.org
Subject: bug#23377: 25.0.93; Completion is extremely slow for insert-char
Date: Sat, 30 Sep 2017 16:27:02 -0400 [thread overview]
Message-ID: <87poa80w6h.fsf@moondust.localdomain> (raw)
In-Reply-To: <87fub4dtr9.fsf@users.sourceforge.net> (Noam Postavsky's message of "Sat, 30 Sep 2017 12:40:58 -0400")
At 12:40 -0400 on Saturday 2017-09-30, Noam Postavsky wrote:
>
> nljlistbox2@gmail.com (N. Jackson) writes:
>
>> At 10:21 +0300 on Wednesday 2016-04-27, Eli Zaretskii wrote:
>>>
>>> So what's the consensus here: do we need an option for turning
>>> the character display off, or don't we?
>>
>> In my opinion FWIW (about 1.5 cents?), being able to see the
>> character beside the name is too nice to give up for Emacs
>> 25.1, but, at least until the feature is further refined and/or
>> performance is improved, there needs to be a way to toggle it
>> on and off.
>
> I think since Mark's patch from #28302 was applied the slowdown
> isn't as bad, but some people were reporting much bigger waits
> (depending on fonts I guess?) and I'm still seeing a noticable
> wait on the order of 1 or 2 seconds, so IMO having a toggle
> makes sense.
I just retried my original recipe
emacs -Q
C-x 8 RET
TAB
on the emacs-26 branch and indeed it is amazingly much faster --
about one second here.
It might be nice for those on older and slower hardware to have a
toggle, but it is no longer so obviously necessary.
N.
next prev parent reply other threads:[~2017-09-30 20:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 0:25 bug#23377: 25.0.93; Completion is extremely slow for insert-char N. Jackson
2016-04-26 1:04 ` Paul Eggert
2016-04-26 2:17 ` Stefan Monnier
2016-04-26 2:51 ` Drew Adams
2016-04-26 4:10 ` Paul Eggert
2016-04-26 5:43 ` Drew Adams
2016-04-26 6:21 ` Eli Zaretskii
2016-04-26 6:34 ` Eli Zaretskii
2016-04-26 13:27 ` N. Jackson
2016-04-26 20:41 ` Paul Eggert
2016-04-27 1:31 ` N. Jackson
2016-04-26 11:51 ` Stefan Monnier
2016-04-26 15:49 ` Paul Eggert
2016-04-26 16:04 ` Drew Adams
2016-04-26 16:59 ` Paul Eggert
2016-04-26 17:15 ` Eli Zaretskii
2016-04-26 18:52 ` N. Jackson
2016-04-26 19:10 ` Eli Zaretskii
2016-04-27 2:09 ` N. Jackson
[not found] ` <<83r3dsyynq.fsf@gnu.org>
2016-04-26 20:18 ` Drew Adams
2016-04-26 16:27 ` Eli Zaretskii
2016-04-26 23:58 ` John Wiegley
2016-04-27 0:26 ` Paul Eggert
2016-04-27 0:53 ` Lars Magne Ingebrigtsen
2016-04-27 1:19 ` John Wiegley
2016-04-27 7:24 ` Eli Zaretskii
2016-04-27 12:27 ` Stefan Monnier
2016-04-27 19:04 ` John Wiegley
2016-04-27 0:10 ` Stefan Monnier
2016-04-26 6:26 ` Eli Zaretskii
2016-04-27 1:54 ` N. Jackson
2016-04-27 7:21 ` Eli Zaretskii
2016-04-27 15:16 ` N. Jackson
2017-09-30 16:40 ` Noam Postavsky
2017-09-30 20:27 ` N. Jackson [this message]
2019-06-25 13:53 ` Lars Ingebrigtsen
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=87poa80w6h.fsf@moondust.localdomain \
--to=nljlistbox2@gmail.com \
--cc=23377@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.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.
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).