unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: ndame <laszlomail@protonmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: What is special about the minibuffer in regard to font locking?
Date: Sun, 23 Jan 2022 17:17:09 +0000	[thread overview]
Message-ID: <Z35VQjeAIYP0PI_Qzki3Z8rcLmRh_ipkqaVb2Xy6BnvyQ25DmZXU-9YK3bZ5dU5U-pYZu0mbC4Hu2g_QD2Kg1IqwjlQIUsm7wuspia-b15w=@protonmail.com> (raw)
In-Reply-To: <shKywr26F5jxSpp3Pf7g5Nx6qEzfJwV0CB8D3x355mfi6UmEL3wVuvjKhrrfjkkWHMat33IMnodtk0BYp2Znn1Dh01c_7CRAxVLmYqRjdtc=@protonmail.com>

> I don't think there's anything fundamental here.
> Probably just code like:

Thanks, I thought it was something more complicated.

And lo! If you go to eval-expression, paste this code
into the prompt:

(progn (setq font-lock-mode t) (emacs-lisp-mode))

and eval it right there in context (C-x C-e) then
the pasted code is font locked.

So syntax highlight works, but it breaks something
else, because then you can't get out of the
minibuffer with C-g for some reason. Probably
because of the mode change?

But you can do an M-x top-level to get out and
then the  minibuffer works again with C-g, because
it's reset to minibuffer-inactive-mode.



  parent reply	other threads:[~2022-01-23 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23  8:25 What is special about the minibuffer in regard to font locking? ndame via Users list for the GNU Emacs text editor
2022-01-23 16:30 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-23 17:17 ` ndame [this message]
2022-01-23 17:56   ` ndame

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='Z35VQjeAIYP0PI_Qzki3Z8rcLmRh_ipkqaVb2Xy6BnvyQ25DmZXU-9YK3bZ5dU5U-pYZu0mbC4Hu2g_QD2Kg1IqwjlQIUsm7wuspia-b15w=@protonmail.com' \
    --to=laszlomail@protonmail.com \
    --cc=help-gnu-emacs@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. 
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).