Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Griswold <dgriswol@rochester.rr.com>
To: ding@gnus.org
Cc: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: buffers no longer fontified
Date: Sun, 06 Sep 2009 16:30:05 -0400	[thread overview]
Message-ID: <87d463ddf6.fsf@cantor.home> (raw)
In-Reply-To: <87tyzfzy3o.fsf@thinkpad.tsdh.de>

Tassilo Horn <tassilo@member.fsf.org> writes:

> Dan Griswold <dgriswol@rochester.rr.com> writes:
>
> Hi Dan!
>
>> Never mind, all. I figured it out. Turns out it was a problem with a
>> deprecated org-mode module I was still loading.
>
> Could you please tell me all details you can remember?

Sure. On Friday evening (EDT), after doing a git pull from the org
repository and re-making the packages, I found that Gnus wasn't showing
any fontification in the group or summary buffers. Now, I thought for
quite a while that this was a problem in Gnus. But then I observed that
bold faces were no longer being set by sudoku.el. (Yeah, I know.) I
realized then that the problem was not a Gnus issue at all.

Eventually I tracked the problem down to the inclusion of `org-mouse' in
the variable `org-modules'. When I removed that value from the list,
then all the fontification problems disappeared.

Because the functionality of org-mouse seemed to be handled just fine in
Emacs 23, then I thought that maybe this module is deprecated for this
Emacs version, and I just hadn't gotten the message. It turns out that
is not true. Trying it just now, I find that only following links works
without org-mouse.

Well, it might be nice to have the org-mouse features. So, in looking at
the source for org-mouse, I see that (like most packages) it encourages
(require 'org-mouse). I try it, without bothering to include org-mouse
in org-modules. And everything works just fine.

So, it appears that my "oh, never mind" now is indeed some sort of
bug. Apparently, as of Friday, activating org-mouse by having it listed
in org-modules will cause fontification problems with some other
packages. But having my own (require 'org-mouse) in my startup files is
just fine. (I find that strange, but there you go.)

That's about the limit of my ability to specify this bug (or quasi
bug?), at least without further guidance. I hope this has been of some
help.

Cheers,

Dan

-- 
 _______________________________
/\                              \
\_| Dan Griswold                |
  | dgriswol@rochester.rr.com   |
  |   __________________________|_
   \_/____________________________/



      reply	other threads:[~2009-09-06 20:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-05 12:53 Dan Griswold
2009-09-05 18:57 ` Dan Griswold
2009-09-06 19:12   ` Tassilo Horn
2009-09-06 20:30     ` Dan Griswold [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d463ddf6.fsf@cantor.home \
    --to=dgriswol@rochester.rr.com \
    --cc=carsten.dominik@gmail.com \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).