From: gdt@work.lexort.com
To: ding@gnus.org
Subject: 2 oddities in current cvs
Date: Mon, 12 Mar 2007 15:18:17 -0400 [thread overview]
Message-ID: <smuslca2ruu.fsf@linuxpal.mit.edu> (raw)
I cvs updated this morning and am having two oddities; both have been
present for several weeks.
My system is NetBSD/i386 along the netbsd-3 branch (3.1, more or
less), with (fsf) emacs 21.4. mail is postfix and dovecot, and seems
to otherwise work fine.
1) When starting a new message, either with ^X m or f from an article,
I get
gnus-message-citation-mode: Symbol's function definition is void: font-lock-set-defaults
Then, things seem normal. I thought I had font-lock mode on by
default but on searching can't find any evidence of that, and visiting
a file doesn't enable it.
Something changed recently, and that matches my memory of trouble
starting:
revision 7.31
date: 2007/02/13 12:45:35; author: yamaoka; state: Exp; lines: +31 -66
(gnus-test-font-lock-add-keywords, gnus-message-add-citation-keywords)
(gnus-message-remove-citation-keywords): Remove.
(gnus-message-citation-mode): Instead of modifying font-lock-keywords directly,
make the variables in font-lock-defaults buffer-local, add
gnus-message-citation-keywords to them and then update the value of
font-lock-keywords.
2) Sometimes I get new mail, and gnus doesn't see it. Mail shows up
in IMAP's INBOX, and mail watching programs, tbird, etc. all see
it. I'm in the *Group* buffer, and type g, and gnus reports no
mail. If I select inbox, and exit it, and then type g, the new
mail is shown to be present. Sometimes this works fine, though.
Is anyone else seeing this? It feels like even odds for gnus vs
dovecot.
next reply other threads:[~2007-03-12 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 19:18 gdt [this message]
2007-03-13 2:56 ` Katsumi Yamaoka
2007-03-13 7:28 ` Simon Josefsson
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=smuslca2ruu.fsf@linuxpal.mit.edu \
--to=gdt@work.lexort.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).