unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sébastien Vauban" <zthjwsqqafhv@spammotel.com>
To: <re.2YV9XX9BLMAAX@spammotel.com>, cyd@stupidchicken.com
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Color-theme problems in Emacs 22+ (Ubuntu, Windows)
Date: Thu, 01 Feb 2007 09:42:06 +0100	[thread overview]
Message-ID: <87wt32clr5.fsf_-_@mundaneum.mygooglest.com> (raw)
In-Reply-To: <87veingqz1.fsf@stupidchicken.com> (Chong Yidong's message of "Wed\, 31 Jan 2007 10\:23\:30 -0500")

Hi Chong,

> The problematic customization is in your .emacs file:
>
> ;; warning font lock (tabs, trailing spaces)
> (defvar font-lock-keywords nil)
> (add-hook 'font-lock-mode-hook
>           '(lambda ()
>              (setq font-lock-keywords
>                    (append font-lock-keywords
>                            '(("\t+"
>                               (0 'my-font-lock-tab-face t))
>                              ("[ \t]+$"
>                               (0 'my-font-lock-trailing-space-face t)))))))
>
> When you munge font-lock-keywords manually, unpredicatable
> things can occur.  In this case, it seems like font-lock-mode
> is taking over highlighting in buffers that normally specify
> face properties manually, causing the normal text highlighting
> to disappear.

Thank you *very much* for that quick and right answer.

Now, I'm relieved as I finally can jump to Emacs 22+, in Ubuntu
and in Windows as well (sorry, forced to use it at work, while
still refusing to use Outlook!).

Weirdly enough, under Emacs22/Ubuntu, my groups are dark green,
and under Emacs23/Windows, with the same config files, they are
purple, as you saw them. Not important, though, as I have
color-highlighting working, and so I know where are the empty
groups and the other ones.

I'm sorry to have disturbed you with a problem that appears to
be within my .emacs file, but see the weird thing: everything
worked perfectly in Emacs 21 (Ubuntu + Window$), and never in
Emacs 22+ (on both platforms)... That's the kind of interaction
that's difficult to spot.


> The proper way to do what you want is to use the function
> `font-lock-add-keywords'.  See also hi-lock.el, which may do
> what you want.

Thanks for the hint on how to do it properly...

Case is closed.

Please receive a grateful hello from Brussels!

Thank you very much,
  Seb

-- 
Sébastien Vauban

      reply	other threads:[~2007-02-01  8:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-21  6:49 Color-theme problems in Emacs 22+ (Ubuntu, Windows) Richard Stallman
2007-01-22 18:06 ` Chong Yidong
2007-01-25  8:49   ` Sébastien Vauban
2007-01-30 12:21   ` Sébastien Vauban
2007-01-30 17:21     ` Chong Yidong
2007-01-31  8:27       ` Sébastien Vauban
     [not found]       ` <1170232136.ZTHJWSQQAFHV@spammotel.com>
2007-01-31 15:23         ` Chong Yidong
2007-02-01  8:42           ` Sébastien Vauban [this message]

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=87wt32clr5.fsf_-_@mundaneum.mygooglest.com \
    --to=zthjwsqqafhv@spammotel.com \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=re.2YV9XX9BLMAAX@spammotel.com \
    --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 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).