From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
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: Tue, 18 Dec 2018 18:55:05 +0000 [thread overview]
Message-ID: <20181218185505.GC8949__4256.77561802349$1545160448$gmane$org@ACM> (raw)
In-Reply-To: <83tvjad5x7.fsf@gnu.org>
Hello, Eli.
On Tue, Dec 18, 2018 at 20:51:48 +0200, Eli Zaretskii wrote:
> > Date: 18 Dec 2018 17:47:16 -0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: 33784@debbugs.gnu.org
> > Incidentally, the temporary buffer created by with-temp-buffer never has
> > font-lock-mode enabled, and font-lock-mode is spiked so that it cannot
> > be enabled in such a buffer. I don't know why. Attempting to enable it
> > fails silently, which is probably another bug.
> It's not a bug, since the temporary buffer starts in Fundamental mode.
If fails silently even after M-: c++-mode in that buffer.
The current strategy is silently to ignore (font-lock-mode) when the
buffer name begins with a space. It feels to me like an easy to
implement, but suboptimal, workaround to a real problem, whatever that
real problem might be.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-12-18 18:55 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 [this message]
[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
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='20181218185505.GC8949__4256.77561802349$1545160448$gmane$org@ACM' \
--to=acm@muc.de \
--cc=33784@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).