From: Sergio Durigan Junior <sergiodj@riseup.net>
To: ding@gnus.org
Subject: Possible bugs (gnus-demon and switching modes when composing messages)
Date: Sat, 06 Oct 2012 18:39:26 -0300 [thread overview]
Message-ID: <874nm7wa9d.fsf@riseup.net> (raw)
[Trying to send the message again since it apparently got bounced]
Hello,
Before opening new bugs, I decided to ask here to see if anyone has any
hints on what's happening with me.
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?
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?
Thanks a lot in advance,
--
Sergio
next reply other threads:[~2012-10-06 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 21:39 Sergio Durigan Junior [this message]
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
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=874nm7wa9d.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).