Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Sergio Durigan Junior <sergiodj@riseup.net>
Cc: ding@gnus.org
Subject: Re: Possible bugs (gnus-demon and switching modes when composing messages)
Date: Sun, 14 Oct 2012 12:28:37 +0200	[thread overview]
Message-ID: <87hapxpctm.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87ehl1wo79.fsf@riseup.net> (Sergio Durigan Junior's message of "Sun, 14 Oct 2012 03:40:58 -0300")

Sergio Durigan Junior <sergiodj@riseup.net> writes:

> Anyway, maybe you can clarify one more question of mine, which is
> related to this behavior.  When I tell Gnus to open a newsgroup (e.g.,
> gmane.emacs.gnus.general), it downloads everything from the
> news-server!  I'm talking about more than 20 MB of data every time I
> open the group.  I have already set (gnus-large-newsgroup) to a
> sensible value (200 messages), but it still downloads everything from
> the server.  Is there any good way to make it download only the last
> 200 messages?

Did you set `gnus-fetch-old-headers'?  But even if you did, it should
only load all headers only once.  Or did you also set
`gnus-nov-is-evil'?

>> I'd use the gcc-self group parameter.  Then an appropriate Gcc header
>> will be created already when starting to write the mail, and that
>> header tells Gnus where to file the sent mail.
>>
>> ,----
>> | (setq gnus-parameters
>> |       `((,(rx "nnimap+A:")
>> | 	   (gcc-self . "nnimap+A:Sent"))
>> | 	  (,(rx "nnimap+B:")
>> | 	   (gcc-self . "nnimap+B:INBOX.Sent Items"))))
>> `----
>>
>> BTW, except for mailing lists I use gcc-self set to t which puts the
>> sent message in the group I've started writing it so that I can read my
>> mail as if they were newsgroups.  That's really convenient.
>
> Hm, I didn't know about the `gcc-self' parameter.  What's the
> difference between it and `gnus-message-archive-group'?

You can also have (gcc-self . t) to use the current group als gcc
target.

> Because that's what I do when I enter a group prefixed with "A" (in my
> example above):
>
>   (setq gnus-message-archive-group "nnimap+local:A/Sent")
>
> Shouldn't it work in the same way as the `gcc-self' parameter?

The `gcc-self' approach inserts a

  Gcc: nnimap+A:some/group

header which determines where to store the mail when sending off.  That
will work also when you change major modes while writing your mail.

Bye,
Tassilo



  reply	other threads:[~2012-10-14 10:28 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 [this message]
2012-11-15  5:52       ` Sergio Durigan Junior
2012-11-15  9:20         ` Matt Ford
2012-11-21  4:06           ` Sergio Durigan Junior
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=87hapxpctm.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --cc=ding@gnus.org \
    --cc=sergiodj@riseup.net \
    /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).