1 ;; Also know as the "wish list". Some are done. For the others, no
2 ;; promise when to be implemented.
4 * Go through the todo list and remove items already done.
6 * Use a new custom type (`define-widget') for posting-style in `gnus-cus.el'
7 (G c) and for `gnus-posting-styles'. Maybe some allowed types are still
10 * Add proper doc strings to functions and variables explained in the manual
11 (info "(gnus)Gnus Utility Functions")
13 * Add Message-IDs or URLs refering to relevant discussions on lists and
16 * Use nicer icons, especially group, summary and message mode
18 Only basic and frequently used commands should have an icons.
19 Maybe use Gnome icons if we can (copyright assignment?). See
20 http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/gnus/tool-bar/ for a
23 * Maybe Gnus should support the LIST SUBSCRIPTIONS, see RFC 2980.
25 * Merge `message-extra-wide-headers' and ` message-header-synonyms'?
27 * Maybe texi/emacs-mime.texi could be divided into user-visible stuff and
28 reference manual for the MIME library.
30 Related: Bill Wohler's article on mh-e-user.
31 http://thread.gmane.org/29067.1138078896@olgas.newt.com
33 * Fix `change servers' command, see David Kastrup's message.
34 http://thread.gmane.org/x54qewqxz4.fsf@lola.goethe.zz
36 * texi/gnus-coding.texi should be fixed.
38 * gnus-topic-kill-region
39 From Colin Marquardt <colin.marquardt@usa.alcatel.com>
41 I noticed that when re-arranging topics, C-k yanks a topic just fine
42 (runs gnus-topic-kill-group).
44 However, my habit is to do marking and the yanking the region, so I
45 would run C-w on the marked topic. But C-w runs
46 gnus-group-kill-region and doesn't yank the topic (for groups it
49 So could we have a gnus-topic-kill-region, or a
50 gnus-group-kill-region which handles topics as well?
52 * Speed up sorting in summary buffer if there is a limit.
54 Suggested by Daniel Ortmann <ortmann@isl.net>.
56 * Investigate the memory usage of Gnus.
58 But it does seem strange that Gnus would use some 15meg for this. I
59 think that is worth investigating. I suspect that bugs or bad
60 design are causing waste; they could be in Gnus, or in Emacs. -- RMS
64 The result of Google group search return a thread. Is it a digest
69 Implement NOV caching with Gnus Agent.
71 * Allow specification of server in Newsgroups header
75 WIBNI I could put `Newsgroups: nntp+quimby:bla' into a message and
76 Gnus would know to post this message on my server `nntp:quimby' into
77 the group bla? I think this would be way cool.
79 But Gnus would have to rewrite the Newsgroups header before actually
82 Thanks for Micha Wiedenmann for this suggestion.
84 * Parsing of the common list confirmation requests so that Gnus can
85 prepare the response with a single command. Including LISTSERV
86 periodic ping messages and the like.
88 * Parsing of the subscription notice to stash away details like what
89 address you're subscribed to the list under (and automatically send
90 mail to the list using that address, when you send mail inside the list
91 group), what address to mail to unsubscribe, and the list info message
92 if available. Hitting the "get FAQ" command inside a mailing list
93 group should display that stashed copy of the info message.
95 * Some help in coming up with good split rules for mailing lists, as
96 automated as possible. Splitting on To and Cc is almost always not
97 what I want, since it can misfile messages and since if I'm cc'd on
98 list mail I want to get both copies, one in my personal mailbox and one
99 in the list mailbox. I know other people handle it other ways, but I
100 prefer it that way. Accordingly, some way to semi-automatically
101 generate split rules based on Sender, Mailing-List, Return-Path,
102 X-Loop, and all of the other random headers that often work would be
105 * Support for zipped folders for all backends this makes sense for.
106 Most likely using jka-compr. (It has been suggested that this do
107 work but I think it should be verified for all backends.)
109 * Agent (Can someone write some subtopics here? I don't use it myself
110 so I don't know what is lacking.)
112 * Support for encrypted folders. Even if the mail arrives unencrypted
113 Gnus should be able to encrypt the *folder* for added safety. This
114 should go for both Gnus' own folders and the folders Gnus reads from
115 (e.g. /var/spool/mail/${USER}). All backends this makes sense for.
117 [John Wiegley's article <200011030445.VAA08277@localhost.dynodns.net>,
118 posted on gnu.emacs.gnus does this.
119 Also, gnus-article-encrypt `K E' encrypts the article body.]
121 * Splitting .newsrc.eld so the history is in one file and the
122 configuration is in another. To help those that reads at two
123 locations (e.g. work and home) and want to have the same
126 * gnus-uu-decode should complain if one or more parts of a series post
127 (ie, "part N of X") is missing, and optionally tick what parts are
128 there for decoding in a later session.
130 * Additional article marking, and an ability to affect marks placed
131 during e.g. mail acquisition. I want to be able to notice the
132 subject "fast money" or "web traffic", automatically mark it with a
133 `$', and score it into oblivion. (But I fear that wanting to change
134 marks with mail-source-* and nnmail-* functions will represent a
135 philosophical conflict with the rest of Gnus' management of article
136 marks. mail-source-* and nnmail-* currently hack around with files
137 under ~/Mail and leave traces in ~/Mail/active, but don't affect
138 things stored in .newsrc.eld.)
140 * A much better interface to nnmail-split-methods. I don't know how
141 I'd like this done, but I know that the current method of manually
142 hacking regexps is pretty untenable for new users. My boss, who is
143 tenured faculty at CMU and CEO & CTO at JPRC, and whose research
144 work has involved Lisp for the last 25 years, is trying to implant
145 himself in a Gnus mail environment, and this is a big sticking point
148 * PGP-supported encryption of entire nnml & nnmh groups. There are
149 people with whom I exchange mail routinely who don't send w/PGP, but
150 I'd really rather that the content not be left lying around
151 unencrypted. Hook into article acquisition the way jka-compr
152 supposedly does, to auto-decrypt every message read.