* Emphasis delimiters show when `W W c'.

[gnus] / todo

diff --git a/todo b/todo
index 9657c7e..be0bfb8 100644 (file)
--- a/todo
+++ b/todo
@@ -1,6 +1,36 @@
 ;; Also know as the "wish list".  Some are done. For the others, no
 ;; promise when to be implemented.
 
+* 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 +48,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?).
 
@@ -649,6 +683,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.
 
@@ -1016,6 +1052,8 @@ exceeding lisp nesting on huge groups.
 
  which should correspond to `B nntp RET sunsite.auc.dk' in *Group*.
 
+ [done]
+
 *    Take a look at w3-menu.el in the Emacs-W3 distribution - this
  works out really well.  Each menu is 'named' by a symbol that
  would be on a gnus-*-menus (where * would be whatever, but at
@@ -1231,6 +1269,8 @@ exceeding lisp nesting on huge groups.
 
 *  (nnoo-set SERVER VARIABLE VALUE)
 
+   [done]
+
 *  nn*-spool-methods
 
 *  interrupitng agent fetching of articles should save articles.
@@ -1352,6 +1392,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
@@ -1393,6 +1435,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
@@ -1400,6 +1444,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.