From: David Engster <deng@randomsample.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Gnus with Emacs 23: gnus-gcc-mark-as-read not working anymore
Date: Tue, 29 Sep 2009 14:00:37 +0200 [thread overview]
Message-ID: <m263b2rme2.fsf@arcor.de> (raw)
In-Reply-To: 87zl8e3s7x.fsf@usenet.my.skamphausen.de
Stefan Kamphausen <skampi@gmx.net> writes:
> David Engster <deng@randomsample.de> writes:
>> Stefan Kamphausen <skampi@gmx.net> writes:
>>> Stefan Kamphausen <skampi@gmx.net> writes:
>>>> in the meantime I dived into the code and found that my description was
>>>> not fully correct. Right after sending a message with GCC-headers those
>>>> messages seem to be marked read, because they don't show up immediately
>>>> after sending. Just when I hit 'g' (gnus-group-get-new-news) the new
>>>> message make the group appear bold and with a message count > 0 in the
>>>> group buffer.
>>
>> Does hitting M-g on the group fix this?
>
> I'm not sure what you mean by "fix".
I meant if it then corrects the number of unread messages to "0". This
could happen if you have 'gaps' in the article numbers, which can often
be resolved by doing a M-g on that group. But that doesn't seem to be
the case here.
>> This was introduced because of a problem with nnimap as primary mail
>> backend. See
>>
>> http://thread.gmane.org/gmane.emacs.gnus.general/67932
>>
>> Do you use nnml as your primary back end?
>
> Yes:
>
> (setq gnus-select-method '(nnml ""))
> (setq gnus-secondary-select-methods
> '(
> ;; Had lots of nnimap groups here earlier, but now all are commented
> ;; However, I might need them again in the future
> ))
[...]
> I think I could switch primary to nnil and secondary to nnml, but I am
> not sure.
>
> Is it dangerous to try this? Would it mess up some files, like
> ~/.news.eld? What would I need to backup before any experiments?
No, better don't do this. It should work with nnml as primary back end,
otherwise it's a bug. I don't use nnml, so I'm not sure why it doesn't
work for you. Maybe nnml and nnimap behave differently in this regard,
which would be unfortunate. I will have to create a test setup for this.
Regards,
David
next prev parent reply other threads:[~2009-09-29 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 8:06 Gnus with Emacs 23: gnus-gcc-mark-as-read not working anymore Stefan Kamphausen
2009-09-22 7:49 ` Stefan Kamphausen
2009-09-28 15:50 ` Stefan Kamphausen
2009-09-28 18:25 ` David Engster
[not found] ` <mailman.7657.1254162498.2239.help-gnu-emacs@gnu.org>
2009-09-29 11:28 ` Stefan Kamphausen
2009-09-29 12:00 ` David Engster [this message]
[not found] ` <mailman.7691.1254225675.2239.help-gnu-emacs@gnu.org>
2009-09-29 13:22 ` Stefan Kamphausen
2009-09-29 21:33 ` David Engster
[not found] ` <mailman.7717.1254260069.2239.help-gnu-emacs@gnu.org>
2009-10-02 14:53 ` Stefan Kamphausen
2009-10-05 15:14 ` David Engster
[not found] ` <mailman.8078.1254756146.2239.help-gnu-emacs@gnu.org>
2009-10-06 11:24 ` Stefan Kamphausen
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=m263b2rme2.fsf@arcor.de \
--to=deng@randomsample.de \
--cc=help-gnu-emacs@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.