Re: Possible bugs (gnus-demon and switching modes when composing messages)

[Tassilo Horn <tsdh@gnu.org>]

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

> 1) I usually set-up (gnus-demon-add-handler 'gnus-demon-scan-news 2
> nil), to instruct Gnus to automatically fetch new messages from (my
> local) IMAP server every 2 minutes.  However, this causes some
> annoying effects.  For example, when I compose a message and tell Gnus
> to send it (C-c C-c), if during the process of sending the message
> Gnus starts to check for new messages on the IMAP server, somehow
> things get stuck and the message is not sent.  I often have to cancel
> the process with C-g, and hit C-c C-c again.
>
> It is also worth mentioning that if I am opening a large group (e.g.,
> more than 2k messages) and Gnus starts to check for new messages, the
> same thing happens.  The solution is also the same: C-g, and tell Gnus
> to open the group again.
>
> Is this a known bug, and is there a workaround for it?

Not really a bug but at least a known limitation.  I'd simply use a
slightly longer interval and more importantly an idle time, e.g.,
something like

  (gnus-demon-add-handler 'gnus-demon-scan-news 15 5)

works very good for me.

> 2) I use more than one account on Gnus, so I have made dovecot put
> prefixes on the e-mail groups.  For example, for account "A" I have
> "A/Sent", "A/Trash", etc, and the same applies for other accounts.
> Depending on the group that I am opening, I tell Gnus to set some
> parameters based on the group's prefix.  So if I open a group from
> account "A", Gnus will know that when I send an e-mail to that group (or
> reply to a message there) it will store my sent message inside "A/Sent".
>
> Well, with that said, the problem is: whenever I change modes when
> composing a message, Gnus gets lost and doesn't store the sent message
> in the right group (in fact, I still don't know where/if it actually
> stores the message).  Rationale: when composing a message that has a
> patch attached, I often change to `change-log-mode' in order to write
> the patch's ChangeLog, and then change back to `message-mode' in order
> to finish writing the message (and send it).
>
> Does anyone see this as well?  Or does anyone have a better workflow
> to suggest?

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.

Bye,
Tassilo