all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: David Koppelman <koppel@ece.lsu.edu>, emacs-devel@gnu.org
Subject: hi-lock-mode doesn't work with emacs -Q.
Date: Thu, 7 Jun 2007 10:26:51 +0100	[thread overview]
Message-ID: <20070607092651.GA1710@muc.de> (raw)

Hi, Stefan!

Start emacs -Q.  (Emacs 22.1, of course).  Visit a new file with:

    C-x C-f foo.txt

.  Type this:

    This file is foo.txt.

.  Enable hi-lock-mode and make "foo" a highlightable pattern:

    M-x hi-lock-mode
    C-x w h foo<CR><CR>    ; accept the default hi-yellow face.

.  This highlights the "foo" yellow, as expected.  At the end of the
line, type:

    foo

.  This new "foo" doesn't get highlighted.  It should be.

#########################################################################

Partial diagnosis:
(i) The bug happens even when global-hi-lock-mode is enabled.
(ii) after-change-functions is nil.  It ought to be
  (jit-lock-after-change t).
(iii) font-lock-mode is t.

How can font-lock-mode be t, whilst at the same time there is no
after-change function?  Is this some optimisation in Font Lock mode
that only sets after-change-functions when font-lock-keywords is
non-nil?

hi-lock.el doesn't seem to be violating Font Lock's proper calling
conventions in any way.

Stefan, I think you're the best person to fix this.

-- 
Alan Mackenzie (Ittersbach, Germany).

             reply	other threads:[~2007-06-07  9:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07  9:26 Alan Mackenzie [this message]
2007-06-07 13:22 ` hi-lock-mode doesn't work with emacs -Q Stefan Monnier
2007-06-08 11:11   ` Alan Mackenzie
2007-06-11 20:25 ` Stefan Monnier
2007-06-15 23:04   ` Alan Mackenzie
2007-06-15 21:51     ` Stefan Monnier

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=20070607092651.GA1710@muc.de \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=koppel@ece.lsu.edu \
    --cc=monnier@iro.umontreal.ca \
    /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.