unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathias Dahl <brakjoller@gmail.com>
Subject: Re: foreground menu bug
Date: Tue, 21 Jun 2005 10:09:09 +0200	[thread overview]
Message-ID: <u64w85dy2.fsf@gmail.com> (raw)
In-Reply-To: E1Dilfb-0003IW-9E@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

>     I tested this the other day too and was confuzzled (confused +
>     puzzled). After a while I realized that it had to do woth
>     font-lock-mode overriding my coloring.
>
> Perhaps those menu items should be disabled when Font Lock is enabled.
> That way, people will see they're not supposed to work.
>
> However, doing that in a simple way would have the wrong results for
> Enriched mode buffers when Global Font Lock mode has been enabled.  So
> the criterion "when font lock mode is enabled" is not exactly the
> right criterion.  Perhaps it should be "in major modes that specify
> something nontrivial for Font Lock to do", or "in such major modes
> when Font Lock is enabled."

Or, it could just warn the user that the highlighting will not be
visible since font lock is enabled?

  parent reply	other threads:[~2005-06-21  8:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15  5:16 foreground menu bug Werner LEMBERG
2005-06-15 13:28 ` Mathias Dahl
2005-06-16  4:07   ` Richard Stallman
2005-06-20  9:08     ` Lute Kamstra
2005-06-21  8:09     ` Mathias Dahl [this message]
2005-06-26  4:46       ` Richard M. Stallman
2005-06-26 10:30         ` Lute Kamstra
2005-06-26 22:42           ` Richard M. Stallman
2005-06-27  8:22         ` Mathias Dahl
2005-06-28  4:16           ` Richard M. Stallman
2005-06-28  8:18             ` Mathias Dahl
2005-06-16 11:51   ` Lute Kamstra
2005-06-17  4:38     ` Richard Stallman
2005-06-17 11:19       ` Lute Kamstra
2005-06-20  8:38 ` Lute Kamstra
2005-06-27 13:14   ` Werner LEMBERG

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=u64w85dy2.fsf@gmail.com \
    --to=brakjoller@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).