From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 33784@debbugs.gnu.org, linux.xhyang@gmail.com
Subject: bug#33784: 27.0.50; some case c-backward-token-2 takes cpu more and emacs hang
Date: Wed, 19 Dec 2018 17:22:00 +0200 [thread overview]
Message-ID: <83k1k5czjb.fsf@gnu.org> (raw)
In-Reply-To: <20181218210507.GD8949@ACM> (message from Alan Mackenzie on Tue, 18 Dec 2018 21:05:07 +0000)
> Date: Tue, 18 Dec 2018 21:05:07 +0000
> Cc: linux.xhyang@gmail.com, 33784@debbugs.gnu.org
> From: Alan Mackenzie <acm@muc.de>
>
> > The real problem is probably performance. But that's a guess; someone
> > will have to do the forensics to find out which change did that, and
> > then try to find related bug reports and/or discussions.
>
> Hah! The change, not to fontify buffers with names beginning with
> spaces, was made by Simon Marshall on 1995-12-09. The list archives only
> go back to 2000. :-(
Maybe we should simply remove that limitation. Most temporary buffers
are in Fundamental mode anyway, and a few that aren't should support
font-lock. If they are rarely or never displayed, we should be fine.
> Maybe the documentation for with-temp-buffer should be amended to
> recommend Lisp programmers not to use it for buffers holding user text.
I believe this is a limitation that is unjustifiably harsh.
next prev parent reply other threads:[~2018-12-19 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 4:09 bug#33784: 27.0.50; some case c-backward-token-2 takes cpu more and emacs hang xh yang
[not found] ` <mailman.5878.1545108246.1284.bug-gnu-emacs@gnu.org>
2018-12-18 17:47 ` Alan Mackenzie
[not found] ` <20181218174716.96822.qmail@mail.muc.de>
2018-12-18 18:51 ` Eli Zaretskii
2018-12-18 18:55 ` Alan Mackenzie
[not found] ` <20181218185505.GC8949@ACM>
2018-12-18 19:23 ` Eli Zaretskii
2018-12-18 21:05 ` Alan Mackenzie
2018-12-18 22:05 ` Glenn Morris
2018-12-19 19:20 ` Alan Mackenzie
2018-12-19 15:22 ` Eli Zaretskii [this message]
2018-12-20 7:18 ` bug#33784: xh yang
2018-12-20 12:53 ` bug#33784: Alan Mackenzie
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=83k1k5czjb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33784@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=linux.xhyang@gmail.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 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).