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 * Add Message-IDs or URLs refering to relevant discussions on lists and
9 * Use nicer icons, especially group, summary and message mode
11 Only basic and frequently used commands should have an icons.
12 Maybe use Gnome icons if we can (copyright assignment?). See
13 http://theotp1.physik.uni-ulm.de/~ste/comp/emacs/gnus/tool-bar/ for a
16 * nnweb doesn't work properly.
18 Due to changes in the HTML output of Google Groups and Gmane, stuff related
19 to web groups (gnus-group-make-web-group) doesn't work anymore.
21 Fetching an article by MID (cf. gnus-refer-article-method) over Google
24 * Merge `message-extra-wide-headers' and ` message-header-synonyms'?
26 * Maybe texi/emacs-mime.texi could be divided into user-visible stuff and
27 reference manual for the MIME library.
29 * texi/gnus-coding.texi should be fixed.
31 * gnus-topic-kill-region
32 From Colin Marquardt <colin.marquardt@usa.alcatel.com>
34 I noticed that when re-arranging topics, C-k yanks a topic just fine
35 (runs gnus-topic-kill-group).
37 However, my habit is to do marking and the yanking the region, so I
38 would run C-w on the marked topic. But C-w runs
39 gnus-group-kill-region and doesn't yank the topic (for groups it
42 So could we have a gnus-topic-kill-region, or a
43 gnus-group-kill-region which handles topics as well?
45 * Speed up sorting in summary buffer if there is a limit.
47 Suggested by Daniel Ortmann <ortmann@isl.net>.
49 * Investigate the memory usage of Gnus.
51 But it does seem strange that Gnus would use some 15meg for this. I
52 think that is worth investigating. I suspect that bugs or bad
53 design are causing waste; they could be in Gnus, or in Emacs. -- RMS
57 The result of Google group search return a thread. Is it a digest
62 Implement NOV caching with Gnus Agent.
64 * Allow specification of server in Newsgroups header
68 WIBNI I could put `Newsgroups: nntp+quimby:bla' into a message and
69 Gnus would know to post this message on my server `nntp:quimby' into
70 the group bla? I think this would be way cool.
72 But Gnus would have to rewrite the Newsgroups header before actually
75 Thanks for Micha Wiedenmann for this suggestion.
77 * Parsing of the common list confirmation requests so that Gnus can
78 prepare the response with a single command. Including LISTSERV
79 periodic ping messages and the like.
81 * Parsing of the subscription notice to stash away details like what
82 address you're subscribed to the list under (and automatically send
83 mail to the list using that address, when you send mail inside the list
84 group), what address to mail to unsubscribe, and the list info message
85 if available. Hitting the "get FAQ" command inside a mailing list
86 group should display that stashed copy of the info message.
88 * Some help in coming up with good split rules for mailing lists, as
89 automated as possible. Splitting on To and Cc is almost always not
90 what I want, since it can misfile messages and since if I'm cc'd on
91 list mail I want to get both copies, one in my personal mailbox and one
92 in the list mailbox. I know other people handle it other ways, but I
93 prefer it that way. Accordingly, some way to semi-automatically
94 generate split rules based on Sender, Mailing-List, Return-Path,
95 X-Loop, and all of the other random headers that often work would be
98 * Support for zipped folders for all backends this makes sense for.
99 Most likely using jka-compr. (It has been suggested that this do
100 work but I think it should be verified for all backends.)
102 * Agent (Can someone write some subtopics here? I don't use it myself
103 so I don't know what is lacking.)
105 * Support for encrypted folders. Even if the mail arrives unencrypted
106 Gnus should be able to encrypt the *folder* for added safety. This
107 should go for both Gnus' own folders and the folders Gnus reads from
108 (e.g. /var/spool/mail/${USER}). All backends this makes sense for.
110 [John Wiegley's article <200011030445.VAA08277@localhost.dynodns.net>,
111 posted on gnu.emacs.gnus does this.
112 Also, gnus-article-encrypt `K E' encrypts the article body.]
114 * Splitting .newsrc.eld so the history is in one file and the
115 configuration is in another. To help those that reads at two
116 locations (e.g. work and home) and want to have the same
119 * gnus-uu-decode should complain if one or more parts of a series post
120 (ie, "part N of X") is missing, and optionally tick what parts are
121 there for decoding in a later session.
123 * Additional article marking, and an ability to affect marks placed
124 during e.g. mail acquisition. I want to be able to notice the
125 subject "fast money" or "web traffic", automatically mark it with a
126 `$', and score it into oblivion. (But I fear that wanting to change
127 marks with mail-source-* and nnmail-* functions will represent a
128 philosophical conflict with the rest of Gnus' management of article
129 marks. mail-source-* and nnmail-* currently hack around with files
130 under ~/Mail and leave traces in ~/Mail/active, but don't affect
131 things stored in .newsrc.eld.)
133 * A much better interface to nnmail-split-methods. I don't know how
134 I'd like this done, but I know that the current method of manually
135 hacking regexps is pretty untenable for new users. My boss, who is
136 tenured faculty at CMU and CEO & CTO at JPRC, and whose research
137 work has involved Lisp for the last 25 years, is trying to implant
138 himself in a Gnus mail environment, and this is a big sticking point
141 * PGP-supported encryption of entire nnml & nnmh groups. There are
142 people with whom I exchange mail routinely who don't send w/PGP, but
143 I'd really rather that the content not be left lying around
144 unencrypted. Hook into article acquisition the way jka-compr
145 supposedly does, to auto-decrypt every message read.
147 [See Support for encrypted folders.]
149 * Baby's First Mail In Gnus. Some set of functions that the
150 new-to-mail-in-Gnus user can invoke which will query the user
151 appropriately for the basic information required to establish mail
152 handling, leaving the appropriate traces in .gnus. Perhaps a
153 customize buffer would be appropriate.
154 - Where does your mail come from?
155 - If some server, what is your POP/IMAP protocol identity?
156 - What is your identity when sending mail, as opposed to posting to
158 - Here are some basic concepts of mail groups (list a few:
159 personal mail, company-wide mail, mailing lists, garbage dumps,
160 receptacles for outbound copies of what one sends; which ones do
161 you want to instantiate, and what mail should land in each?
162 [/viz./ problem of nnmail-split-methods interface.]
164 [Probably `assistant.el' will provide this. But it's development is
167 * Full integration of nnir into Gnus. Generic hooks for adding new
168 external nnir sources. I use a couple experimental, in-house tools
169 (JPRC is a research lab, occupied with document analysis and machine
170 learning) and adding new search engines to nnir by hacking the main
171 nnir.el module is rather clunky.
173 * Manual ordering of articles in an nnml folder.
175 That is, keystrokes to move articles (or whole threads) up or down
176 in the *Summary* buffer relative to the other articles. The order
177 would be persistent (e.g., across gnus sessions).
179 With this ability, an nnml folder would make for a good to-do list.
181 * Since many uses Gnus to store to do lists I think it is time for an
182 nntodo. (I know Kai already written one, maybe use that for a start?)
184 * nnsql backend, which would allow messages or folders to be imported
185 in a local (My|Postgre|?)SQL RDBMS.
187 * "posting profiles" ideally accessible from a popup menu; allowing
188 choice between predefined profiles of
189 from,name,organization,etc. Example: I'm at home, but need to reply
190 to a work mail; i can hit 'R', then use this command to switch to my
191 'work' profile for purposes of this one reply. (This might already
192 be possible with current Gnus, but I don't think so.)
194 * Better handling of the mail retrieving / splitting feature:
195 - the variables <backend>-get-new-mail should not exist anymore. Mail
196 retrieving should be a separate matter.
197 - we should be able to split mails to groups AND backends at the same time.
198 - meanwhile, we should still be able to associate certain mail sources with
201 * A better interface to the agent download scoring rules, like the one
202 for the other scoring rules.
204 * Editing of messages in the agents cache.
206 * More article marks (like '!' or '?').
207 Maybe user defined marks that can be displayed as any choosen charakter,
208 so one could do things like limiting on, to do whatever one likes with
211 * A possibility to add notes to messages. If thouse could include links
212 to other (stored) messages this would be very practical.