From: Simon Josefsson <jas@extundo.com>
Subject: Re: nnimap: editing articles
Date: Mon, 13 Feb 2006 21:06:19 +0100 [thread overview]
Message-ID: <jasaccvvxac.fsf@latte.josefsson.org> (raw)
In-Reply-To: <4nr7679i49.fsf@lifelogs.com> (Ted Zlatanov's message of "13 Feb 2006 14:24:54 -0500")
"Ted Zlatanov" <tzz@lifelogs.com> writes:
> On 11 Feb 2006, jas@extundo.com wrote:
>
>> Gnus' editing functionality assume that if you edit article X, it will
>> be called X after the editing too. I.e., it doesn't refresh group
>> information, and doesn't understand when the new article is called Y.
>> Perhaps that can be fixed, so that 'e' works. OTOH, perhaps using 'e'
>> will simply give wrong impressions. With IMAP, you don't actually
>> edit the article. Perhaps some command that will download an article,
>> put you into an editing buffer, and have a command, say, C-c C-c
>> "save" it by querying for a destination group (which could be any
>> group) and then save the new article to that group. This sounds
>> rather useful, actually. Perhaps this is already possible...
>
> I don't see a problem with using `e' for this. It's very reasonable,
> and will affect other IMAP clients a little bit by appearing to create
> a new message, but if we set the flags appropriately that won't be
> serious.
Yep, should work fine. The 'e' command has to be teached about how to
do this though.
> What do you think about the discussion between me and Reiner about
> custom flags for Gnus in general? Is that something that imap.el and
> nnimap.el can support easily? Are there any performance issues?
It shouldn't be difficult to add, imap.el can parse them and set them
fine. It already use client-specific flags for things like gnus-agent
and other Gnus-specific marks.
Since this would be a new user interface, some care could be made so
it would work well with IMAP. I think it looks like a neat project,
that doesn't require much modifications to existing code (always a
nice property). I'm not sure what the user interface would look like
though. Some ideas:
- Summary buffer markup to print user-specific flags.
- Perhaps it should be optional, i.e., you'll have
to press some key to make the flags visible.
- Limiting to certain "tags", searching the user flags?
- Useful to "tag" messages, i.e., project-name or similar.
- Command to add a tag to current or process-marked messages.
- Could autocomplete on existing names, or allow the user to enter a
new flag.
- Command to process mark all messages with a certain user-flag?
...
next prev parent reply other threads:[~2006-02-13 20:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 11:22 set labels in nnml or nnfolder groups Uwe Brauer
2006-02-06 13:22 ` Reiner Steib
2006-02-06 14:37 ` Uwe Brauer
2006-02-06 15:09 ` mozilla (was: set labels in nnml or nnfolder groups) Uwe Brauer
2006-02-06 19:06 ` mozilla Ted Zlatanov
2006-02-07 12:25 ` mozilla Uwe Brauer
2006-02-07 15:41 ` mozilla Ted Zlatanov
2006-02-07 17:54 ` mozilla Uwe Brauer
2006-02-07 19:11 ` nnimap: editing articles (was: mozilla) Reiner Steib
2006-02-08 20:11 ` nnimap: editing articles Ted Zlatanov
2006-02-09 15:23 ` Reiner Steib
2006-02-11 22:01 ` Simon Josefsson
2006-02-13 19:24 ` Ted Zlatanov
2006-02-13 20:06 ` Simon Josefsson [this message]
2006-02-13 22:22 ` Steven E. Harris
2006-02-07 12:27 ` mozilla Uwe Brauer
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=jasaccvvxac.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).