From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/61970 Path: news.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap: editing articles Date: Mon, 13 Feb 2006 21:06:19 +0100 Message-ID: References: <877j88zq93.fsf@mat.ucm.es> <87psm0ttfl.fsf_-_@mat.ucm.es> <4nlkwomhm8.fsf@lifelogs.com> <87mzh3nyno.fsf@mat.ucm.es> <4n4q3bfa6y.fsf@lifelogs.com> <87hd7b5a2c.fsf@mat.ucm.es> <4nr7679i49.fsf@lifelogs.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139861395 21281 80.91.229.2 (13 Feb 2006 20:09:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 13 Feb 2006 20:09:55 +0000 (UTC) Original-X-From: ding-owner+m10497@lists.math.uh.edu Mon Feb 13 21:09:55 2006 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F8k11-0003PJ-Ap for ding-account@gmane.org; Mon, 13 Feb 2006 21:09:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu ident=lists) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1F8k0u-0000cP-00; Mon, 13 Feb 2006 14:09:36 -0600 Original-Received: from nas02.math.uh.edu ([129.7.128.40]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1F8jxx-0000cH-00 for ding@lists.math.uh.edu; Mon, 13 Feb 2006 14:06:33 -0600 Original-Received: from quimby.gnus.org ([80.91.224.244]) by nas02.math.uh.edu with esmtp (Exim 4.52) id 1F8jxs-0000wR-C6 for ding@lists.math.uh.edu; Mon, 13 Feb 2006 14:06:33 -0600 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1F8jxq-0000GX-00 for ; Mon, 13 Feb 2006 21:06:26 +0100 Original-Received: from latte.josefsson.org (jas@yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.13.4/8.13.4/Debian-3) with ESMTP id k1DK6NsF029992 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 13 Feb 2006 21:06:24 +0100 Original-To: ding@gnus.org OpenPGP: id=B565716F; url=http://josefsson.org/key.txt X-Hashcash: 1:21:060213:ding@gnus.org::85p7TWT4kdsAtcK6:2iJ1 In-Reply-To: <4nr7679i49.fsf@lifelogs.com> (Ted Zlatanov's message of "13 Feb 2006 14:24:54 -0500") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on yxa-iv X-Virus-Scanned: ClamAV version 0.84, clamav-milter version 0.84e on yxa.extundo.com X-Virus-Status: Clean X-Spam-Score: -2.5 (--) Precedence: bulk Original-Sender: ding-owner@lists.math.uh.edu Xref: news.gmane.org gmane.emacs.gnus.general:61970 Archived-At: "Ted Zlatanov" 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? ...