From: Paul Eggert <eggert@cs.ucla.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: 22884@debbugs.gnu.org
Subject: bug#22884: 25.0.92; C/l mode editing takes waaaayy too long
Date: Fri, 13 May 2016 14:09:27 -0700 [thread overview]
Message-ID: <e7e5ce84-9333-0e95-4bec-77ce24ee9564@cs.ucla.edu> (raw)
In-Reply-To: <7zvb2hu21l.fsf@fencepost.gnu.org>
On 05/13/2016 01:37 PM, Glenn Morris wrote:
> What about other C code, besides the Emacs sources?
> What if anyone ever wants to edit an older version of the Emacs sources?
Older versions of Emacs have smaller config.h files, which makes the
problem significantly smaller. I just now visited a config.h file for
Emacs 23.4, and the same “type ‘/ /’” benchmark took about two seconds
on my six-year-old desktop (Fedora 23 x86-64, AMD Phenom II X4 910e).
Although two seconds is pretty annoying, it's considerably better than
the ten seconds I was seeing with emacs-25 before we worked around the
problem there.
Although Non-Emacs sources may have the problem, I imagine it's
reasonably rare.
> Your initial report said: "This sort of thing makes Emacs effectively
> unusable for editing [some C code]", which is, y'know, a pretty bad state.
Yes, it is indeed a bad state. However, the problematic situations are
rare and cause slowdowns rather than crashes, so the case for making it
a blocker is not as strong as it could be.
next prev parent reply other threads:[~2016-05-13 21:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 18:08 bug#22884: 25.0.92; C/l mode editing takes waaaayy too long Paul Eggert
2016-03-03 12:49 ` Alan Mackenzie
2016-03-03 17:54 ` Paul Eggert
2016-03-03 19:23 ` Alan Mackenzie
2016-03-03 20:38 ` Eli Zaretskii
2016-03-03 21:57 ` Paul Eggert
2016-03-03 22:59 ` Alan Mackenzie
2016-03-03 20:51 ` Eli Zaretskii
2016-03-03 23:44 ` Paul Eggert
2016-03-04 14:47 ` Alan Mackenzie
2016-03-04 20:32 ` Paul Eggert
2016-03-04 21:08 ` Alan Mackenzie
2016-03-13 10:03 ` Alan Mackenzie
2016-03-08 14:02 ` Alan Mackenzie
2016-03-09 8:25 ` Paul Eggert
2016-03-09 9:28 ` John Wiegley
2016-03-09 9:37 ` Paul Eggert
2016-03-09 21:30 ` John Wiegley
2016-03-09 10:56 ` Alan Mackenzie
2016-03-09 14:44 ` Drew Adams
2016-03-09 17:04 ` Alan Mackenzie
2016-03-09 17:14 ` Drew Adams
2016-03-03 20:40 ` Eli Zaretskii
2016-03-03 22:27 ` Alan Mackenzie
2016-03-03 23:18 ` Alan Mackenzie
2016-03-04 8:32 ` Eli Zaretskii
2016-03-04 9:37 ` Alan Mackenzie
2016-03-15 3:07 ` Stefan Monnier
2016-05-08 23:10 ` Dmitry Gutov
2016-05-13 19:35 ` Paul Eggert
2016-05-13 20:37 ` Glenn Morris
2016-05-13 21:09 ` Paul Eggert [this message]
2022-04-28 11:22 ` Lars Ingebrigtsen
2022-04-28 19:35 ` Paul Eggert
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=e7e5ce84-9333-0e95-4bec-77ce24ee9564@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=22884@debbugs.gnu.org \
--cc=rgm@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.
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.