all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Zachary Napier <zachary.napier.44@gmail.com>
Cc: 37137@debbugs.gnu.org
Subject: bug#37137: Setting font-lock-case-fold-search to t causes hangs on certain types in c-mode
Date: Sun, 25 Aug 2019 14:12:49 -0400	[thread overview]
Message-ID: <jwv7e71qfpy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <CAOtOpxJ4FcAiujM=0oE326e8F-k9JPiMHwCvXCYEFFtR3ZxqQQ@mail.gmail.com> (Zachary Napier's message of "Wed, 21 Aug 2019 15:20:20 -0700")

> I have in my .emacs file only these two lines:
>
>     (custom-set-variables
>      '(font-lock-keywords-case-fold-search t))

How did you end up with that?
font-lock-keywords-case-fold-search is not a customize variable, so you
should not set it with custom-set-variables.

> Then if I visit an empty or nonexistent C file and just type "LONG"
> (in all caps or with at least one letter being capital), Emacs will
> hang after typing the final G but before the G appears on screen

Clearly not a desirable behavior, indeed, but the above var setting is
clearly a pilot error.  Of course

    (setq-default font-lock-keywords-case-fold-search t)

would give the same result, but I'd also argue that it'd be
a pilot error.


        Stefan






  parent reply	other threads:[~2019-08-25 18:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-21 22:20 bug#37137: Setting font-lock-case-fold-search to t causes hangs on certain types in c-mode Zachary Napier
     [not found] ` <mailman.18.1566429065.1922.bug-gnu-emacs@gnu.org>
2019-08-25 10:22   ` Alan Mackenzie
2019-08-25 18:12 ` Stefan Monnier [this message]
2019-09-01 21:28   ` Zachary Napier
2019-09-02 12:50     ` Stefan Monnier
2019-09-02 19:26       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv7e71qfpy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=37137@debbugs.gnu.org \
    --cc=zachary.napier.44@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 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.