On Jul 18, 2014 2:04 PM, "Jan Kundrát" <[email protected]> wrote: > It doesn't work like that. The "tasks" or "jobs" you see in there are low-level scheduling blocks which got already assigned their slot on the wire/socket so to speak. They cannot be re-scheduled to perform their duties on top of another connection. > > There's currently no concept of these higher-level tasks ("I want to send this mail" or "move these messages into a folder I just created") yet.
I see. >> It seems all I can do is take Trojita >> offline... which I just tried, and it kills the message-send job *but the >> stuck sync request is still trying*. > > Yes, which is not necessarily a wrong thing. You can reconnect and everything should work (TM). Please file bugs if it fails. The mere indication of a sync job in the status bar is a harmless thing; it will die when the connection times out. If it happens again, I'll try it. However, if a sync job is dead but the status bar shows that it's still in progress, this is misleading to the user. All I knew is, if there's a stuck job appearing in the status bar, other IMAP requests will be stuck behind it. I set Trojita to offline status and the status bar didn't change. Based on the available information in the interface, it appeared that further IMAP attempts would fail. There is no indication in the interface that the behavior after re-opening the IMAP connection will be different from the behavior before. IMO going offline should immediately kill any network activities. This is a reasonable expectation from the user's point of view. hjh
