From: Andreas Schwab <schwab@linux-m68k.org>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: How is font-locking different in minibuf?
Date: Tue, 02 Aug 2011 18:24:35 +0200 [thread overview]
Message-ID: <m2ty9zhjcs.fsf@igel.home> (raw)
In-Reply-To: <m1wreww3s9.fsf@gmail.com> (Leo's message of "Tue, 02 Aug 2011 17:39:34 +0800")
Leo <sdl.web@gmail.com> writes:
> You can see defun not fontified. This behaviour is different from normal
> buffer. Any idea why it behaves this way? Thanks.
If you want font-lock-mode you need to enable it. Invisible buffer
don't by default.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-08-02 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 9:39 How is font-locking different in minibuf? Leo
2011-08-02 16:24 ` Andreas Schwab [this message]
2011-08-02 17:07 ` Leo
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=m2ty9zhjcs.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@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).