Gnus development mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@riseup.net>
To: ding@gnus.org
Subject: Re: Possible bugs (gnus-demon and switching modes when composing messages)
Date: Wed, 21 Nov 2012 02:06:52 -0200	[thread overview]
Message-ID: <87haojoazn.fsf@riseup.net> (raw)
In-Reply-To: <874nkr6x3e.fsf@rss01.mhs.man.ac.uk>

Hi Matt, thanks for the reply.

On Thursday, November 15 2012, Matt Ford wrote:

> I've got a note in my config file which seems to produce a similar bug
>
> ;; If we set the below to t then this seems to make news groups behave
> ;; badly (every message gets downloaded all the time) but we won't have
> ;; all articles available
> (setq gnus-agent-consider-all-articles nil)
> (setq gnus-agent-synchronize-flags t)
> (setq gnus-agent-mark-unread-after-downloaded nil)
> (setq gnus-agent-enable-expiration 'DISABLE)
>
> Perhaps you have set this also?

Hm, no, I don't have any of these settings in my .gnus file.  Actually,
I didn't quite understand if you are suggesting that I should have these
settings, or that I shouldn't :-).  According to your comment, if I set
`gnus-agent-consider-all-articles' to t, it will solve my problem, right?

Thanks in advance,

-- 
Sergio




  reply	other threads:[~2012-11-21  4:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-06 21:39 Sergio Durigan Junior
2012-10-07 18:39 ` Tassilo Horn
2012-10-14  6:40   ` Sergio Durigan Junior
2012-10-14 10:28     ` Tassilo Horn
2012-11-15  5:52       ` Sergio Durigan Junior
2012-11-15  9:20         ` Matt Ford
2012-11-21  4:06           ` Sergio Durigan Junior [this message]
2012-11-21 10:49             ` Matt Ford
2012-11-21 22:01               ` Sergio Durigan Junior
2012-11-22  5:43                 ` Sergio Durigan Junior
2012-11-22  7:12                   ` Eric Abrahamsen
2012-11-23  2:56                     ` Sergio Durigan Junior
2012-11-22 15:20                   ` Burton Samograd
2012-11-25  5:10                     ` Sergio Durigan Junior

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=87haojoazn.fsf@riseup.net \
    --to=sergiodj@riseup.net \
    --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).