Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
mu-discuss
Home
+ new post
About this group
Join this group
Message from discussion mu4e: cancelled drafts not removed
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dirk-Jan C. Binnema  
View profile  
 More options Apr 5 2012, 6:33 pm
From: Dirk-Jan C. Binnema <d...@djcbsoftware.nl>
Date: Fri, 06 Apr 2012 01:33:36 +0300
Local: Thurs, Apr 5 2012 6:33 pm
Subject: Re: mu4e: cancelled drafts not removed
Print | View thread | Show original | Report this message | Find messages by this author
Hi James,

On Fri 06 Apr 2012 12:44:40 AM EEST, James Ladan wrote:

> Hi Dirk,

> On Sat, Mar 31, 2012 at 07:41, Dirk-Jan C. Binnema <d...@djcbsoftware.nl> wrote:
> > Ah; I implemented something similar in mu4e now (pushed to git); the
> > "--text follows this line--" is a buffer-only thing now that should
> > never appear in the written file. It seems to work well for me, please
> > let me know if you find any problems.

> Finally updated and tested. Works well, thanks.

Ah, that's good to hear.

> Now some new issues (because drafts are a big pain in the neck with
> their edge cases, etc.):

> 1. If one saves a draft and an update runs in the background, the file
> will likely be renamed. When the email is sent, the sent email is
> correctly moved to the sent folder, but the earlier saved copy will be
> left behind in the drafts folder.

> 2. Flags get out of whack for unseen drafts
>    - If I postpone a draft, let a sync run, and then try to edit, I'm
> told that "Editing is only allowed for draft messages."

Drafts get the maildir 'D' flag (,D in their filename) to signify
their draftness. However, I don't think the 'D' is widely used, so
possibly the synchronization loses it. mu4e insists on that flag to
prevent users from editing existing, non-draft messages.

>    - If I postpone a draft, edit it, postpone it again, and then let a
> sync run, I am able to open the draft for editing again later. (Good.)
>    - If I postpone a draft, view it, then let a sync run, I am still
> able to open the draft for editing again later. (Good.)

> Looks like the draft needs to be flagged as having been seen. Either a
> limitation in offlineimap or the IMAP server my company uses.

Hmm, not sure what's happening... but now (git), drafts are marked as
'S' (seen). Which makes sense, I suppose, since when you save the draft,
you must have seen it. Does that fix the problem?

> In the working cases for #2, editing and sending the postponed draft
> from a different computer (or webmail interface) works. Nice!

> >  - new messages are now considered unmodified until the user actual
> >   does something with it. Thus, if you accidentally start a new
> >   message, you can kill the buffer without emacs bothering you

> Works well. :)

Sounds great! Thanks for testing!

--
Dirk-Jan C. Binnema                  Helsinki, Finland
e:d...@djcbsoftware.nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google