unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Kamphausen <skampi@gmx.net>
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 13:28:34 +0200	[thread overview]
Message-ID: <87zl8e3s7x.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: mailman.7657.1254162498.2239.help-gnu-emacs@gnu.org

Hi David,

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".  However, if I go to one of my
archive groups (nnml:mail.2009-09 currently) and hit M-x the messages
sent earlier lead to that group having a count > 0, that is, those sent
messages are not marked as read.  So, this is just the same as hitting
'g' anywhere in the group buffer.


>> Rereading my older post and while searching the gnus-source code as well
>> as the internet for answers I found that the method is stripped from the
>> group name.  According to this thread from 2006
>> http://thread.gmane.org/gmane.emacs.gnus.general/62775/focus=62934
>> this may well be the problem.
>>
>> To me it seems like the call to (gnus-group-short-name group) leads to
>> my problem.  If I read the changelog correctly it was introduced in
>> revision 1.57, Fri Jan 9 03:01:51 2009 UTC:
>>
>> http://cvs.savannah.gnu.org/viewvc/emacs/lisp/gnus/gnus-msg.el?root=emacs&r1=1.56&r2=1.57
>
> 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
      ))

(eval-after-load "mail-source"
  '(setq mail-sources
         '(
           (imap
            :server "mailserver.example.com"
            :user "domain/username"
            :password "verysecret"
            )
           )))


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?


Kind Regards,
Stefan
-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.


  parent reply	other threads:[~2009-09-29 11:28 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 [this message]
2009-09-29 12:00         ` David Engster
     [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

  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=87zl8e3s7x.fsf@usenet.my.skamphausen.de \
    --to=skampi@gmx.net \
    --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.
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).