X-Git-Url: http://cgit.sxemacs.org/?a=blobdiff_plain;f=todo;h=e7ccdb96d0dbf0e34da3a7546aa52828a97e50ed;hb=24c835fcbdb32da252b654d4e122a7adec97acc6;hp=bc350435b7b9d4368f30036a3f6c7820a13506ad;hpb=1a22e1d98500ef32bf4b3717491b5df8d26b753b;p=gnus

diff --git a/todo b/todo
index bc350435b..e7ccdb96d 100644
--- a/todo
+++ b/todo
@@ -1,6 +1,40 @@
 ;; Also know as the "wish list".  Some are done. For the others, no
 ;; promise when to be implemented.
 
+* Understand mail-user-agent. Maybe gnus-mail-user-agent.
+  
+  [Done]
+
+* Emphasis delimiters show when `W W c'.
+
+  [Fixed]
+
+* Parsing of the common list confirmation requests so that Gnus can
+   prepare the response with a single command.  Including LISTSERV
+   periodic ping messages and the like.
+
+* Parsing of the various List-* headers to enable automatic commands
+   like "send help message," "send unsubscribe message," and the like.
+
+   [done, see gnus-ml.el]
+
+* Parsing of the subscription notice to stash away details like what
+   address you're subscribed to the list under (and automatically send
+   mail to the list using that address, when you send mail inside the list
+   group), what address to mail to unsubscribe, and the list info message
+   if available.  Hitting the "get FAQ" command inside a mailing list
+   group should display that stashed copy of the info message.
+
+* Some help in coming up with good split rules for mailing lists, as
+   automated as possible.  Splitting on To and Cc is almost always not
+   what I want, since it can misfile messages and since if I'm cc'd on
+   list mail I want to get both copies, one in my personal mailbox and one
+   in the list mailbox.  I know other people handle it other ways, but I
+   prefer it that way.  Accordingly, some way to semi-automatically
+   generate split rules based on Sender, Mailing-List, Return-Path,
+   X-Loop, and all of the other random headers that often work would be
+   very cool.
+
 * Support for zipped folders for all backends this makes sense for.
   Most likely using jka-compr. (It has been suggested that this do
   work but I think it should be verified for all backends.)
@@ -18,6 +52,10 @@
   should go for both Gnus' own folders and the folders Gnus reads from
   (e.g. /var/spool/mail/${USER}). All backends this makes sense for.
 
+  [John Wiegley's article <200011030445.VAA08277@localhost.dynodns.net>,
+   posted on gnu.emacs.gnus does this.
+   Also, gnus-article-encrypt `K E' encrypts the article body.]
+
 * The stuff on "Newest Features" in the manual should be implemented
   and the node updated (it maybe is?).
 
@@ -54,6 +92,8 @@
   unencrypted.  Hook into article acquisition the way jka-compr
   supposedly does, to auto-decrypt every message read.
 
+  [See Support for encrypted folders.]
+
 * Baby's First Mail In Gnus.  Some set of functions that the
   new-to-mail-in-Gnus user can invoke which will query the user
   appropriately for the basic information required to establish mail
@@ -649,6 +689,8 @@ exceeding lisp nesting on huge groups.
 
 *  a way to tick/mark as read Gcc'd articles.
 
+   [done, (setq gnus-inews-mark-gcc-as-read t)]
+
 *  a way to say that all groups within a specific topic comes from a
  particular server?  Hm.
 
@@ -1233,6 +1275,8 @@ exceeding lisp nesting on huge groups.
 
 *  (nnoo-set SERVER VARIABLE VALUE)
 
+   [done]
+
 *  nn*-spool-methods
 
 *  interrupitng agent fetching of articles should save articles.
@@ -1354,6 +1398,8 @@ exceeding lisp nesting on huge groups.
  Is the "+" character illegal in newsgroup names?  Is there any way
  in Gnus to work around this?  (gnus 5.6.45 - XEmacs 20.4)
 
+ [It works in 5.8.8.]
+
 *  When `#F', do:
 
       Subject: Answer to your mails 01.01.1999-01.05.1999
@@ -1395,6 +1441,8 @@ exceeding lisp nesting on huge groups.
  into [-] buttons.  (If I click on one of the [+] buttons, it does
  turn into a [-] button.)
 
+ [fixed]
+
 * Perhaps there should be a command to "attach" a buffer of comments
  to a message?  That is, `B WHATEVER', you're popped into a buffer,
  write something, end with `C-c C-c', and then the thing you've
@@ -1402,6 +1450,8 @@ exceeding lisp nesting on huge groups.
 
 * Handle external-body parts.
 
+  [done for some access types]
+
 * When renaming a group name, nnmail-split-history does not get the
  group name renamed.