From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: should we be able to edit imap messages?
Date: Sun, 04 May 2014 16:32:10 +0800 [thread overview]
Message-ID: <8738gqlzat.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <upzcfvkqt2r0.fsf@dod.no>
Steinar Bang <sb@dod.no> writes:
>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:
>
>> Thanks! That was the impression I was getting. I'll just leave this
>> alone then.
>
> Yes, but I think article editing actually works in nnimap. At least it
> has worked at some point in time, because I have done it to re-thread
> articles.
>
> However the way it works, is by creating a new article when saving, and
> then deleting the old article.
Yeah, but then when you sync the server thinks it has a new message, and
if you're using other clients elsewhere, they all get the "new" message,
and... it just ends up feeling wrong, I think
next prev parent reply other threads:[~2014-05-04 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 6:38 Eric Abrahamsen
2014-05-03 9:55 ` Steinar Bang
2014-05-04 2:24 ` Eric Abrahamsen
2014-05-04 7:35 ` Steinar Bang
2014-05-04 8:32 ` Eric Abrahamsen [this message]
2014-05-05 23:29 ` Dan Christensen
2014-09-24 21:26 ` Ted Zlatanov
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=8738gqlzat.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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).