all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Juri Linkov <juri@jurta.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [rms@gnu.org: Re: mouse cannot be used in *grep* buffer if font-lock is turned off]
Date: Tue, 19 Oct 2004 15:43:00 -0400	[thread overview]
Message-ID: <jwvsm8afqkq.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20041019210656.2de3ff4b@pfdabpc.inhouse.start.de> (Daniel Pfeiffer's message of "Tue, 19 Oct 2004 21:06:56 +0200")

> This sounds like a step further: font-lock without fonts, i.e. a property
> lock mode.  Actually I can't for the life of me imagine why anybody would
> not want font-locking, even vi can do it nowadays.  It adds so much
> legibility, I feel it should be on by default.  My oldish 500MHz P3 can
> handle it easily and I'm pretty sure I used without great penalty way back
> on my 100MHz box.

I tend to agree.  I think if the only reason not to turn on font-lock is
because the visual effects are annoying, then I suggest the following:

- always turn on the font-lock machinery.
- font-lock.el places face properties on the `font-lock-face' property.

M-x font-lock-mode does nothing more than

  (set (make-local-variable 'char-property-alias-alist)
       (cons '(face font-lock-face) char-property-alias-alist))


-- Stefan

  reply	other threads:[~2004-10-19 19:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19  6:13 [rms@gnu.org: Re: mouse cannot be used in *grep* buffer if font-lock is turned off] Richard Stallman
2004-10-19 19:06 ` Daniel Pfeiffer
2004-10-19 19:43   ` Stefan Monnier [this message]
2004-10-21  1:45     ` Richard Stallman
2004-10-19 20:59   ` David Kastrup
2004-10-19 21:59     ` Daniel Pfeiffer
2004-10-19 22:39       ` David Kastrup
2004-10-20  7:07         ` Daniel Pfeiffer
2004-10-21  1:46           ` Richard Stallman

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=jwvsm8afqkq.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=rms@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.
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.