From: Tobias Angele Date: Sun, 9 Apr 2017 14:39:15 +0000 (+0200) Subject: delete TODO files X-Git-Tag: neomutt-20170526~47^2~6 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0ff286c8bb9d53f04a61f8d6dfae614ec01223a6;p=neomutt delete TODO files see https://github.com/neomutt/neomutt/milestone/9 --- diff --git a/TODO b/TODO deleted file mode 100644 index a02b4caa9..000000000 --- a/TODO +++ /dev/null @@ -1,59 +0,0 @@ -Problems are listed in approximate order of priority. - -- When displaying MIME headers, rfc 2047 decoding is applied (which - should not happen), and rfc 2231 decoding is not applied (which - should happen). - -- Help formatting could be revamped a bit. - -- In the "attachment" menu, assume this: - - 1 [text/plain, 7bit, 1.1K] - 2 [message/rfc822, 7bit, 6.1K] A test message - 3 [text/plain, 7bit, 0.1K] |-> - 4 [message/rfc822, base64, 2.5K] |-> - 5 [message/rfc822, base64, 2.7K] `-> - - (please note the "message/rfc822" attachments encoded as - Base64; that's illegal, but Sun's Mailtool sends that - kind of messages); then go to, say, attachment "4", - delete it, and go to the main menu; you won't be able to - quit the mailbox (ok, 'x' works, but 'q' doesn't). - - The problem here lies in the fact that mutt uses mailbox - handling functions to access message/rfc822 type - attachments. We'd need to perform an additional - decoding step before using these functions to fix this - bug. - - Please note that mutt's just assuming RFC-compliant mail - here. Fixing this stuff may become a PITA. - - - - -- BODY struct should probably have a pointer to its - corresponding HEADER struct. this is needed for - mh/maildir mailboxes so the correct pathname can be - found. Or perhaps all we need is a .hdr member of the - STATE struct so that all of the MIME handlers can look - up the corresponding HEADERs if need be? - -- handle message/external-body in some fashion - -- handle message/partial reconstruction - -- make patterns generic (I have patches for this -tlr), and - introduce generic menu limiting, menu pattern searching, and the - like. - - Note: This still requires some thought, since we'd have to store - per-entry data in the menu structure. As an alternative, we could - extend the tag method to do something to more general flags. The - latter approach would make the implementation of proper - tag-prefix behaviour more simple: Functions should only be applied - when a message is tagged and visible. Additionally, we must not - access a menu's max field directly any more: Adding an entry to a - menu will require re-allocating and possibly updating the v2r - array. How do we handle "in-the-middle additions" properly? Do - they happen at all? diff --git a/doc/TODO b/doc/TODO deleted file mode 100644 index 75b9596b6..000000000 --- a/doc/TODO +++ /dev/null @@ -1,44 +0,0 @@ -Documentation TODO in no particular order grouped by style and content. - -It would be nice to get some of these done for 1.6. - -Style/Technical ---------------- - -* Re-check complete manual for consistency. The same things need to be - consistently marked up, e.g. an item either always as or - always (decide clearly which to use for what), make sure - all option refs are links, things are consistently quoted. - E.g. it has: - - If the filename begins with a tilde (``˜'') - - and - - If the filename ends with a vertical bar (|) - - We need to choose either style and use it. - -* Think about some way of templating to a) help improve consistency - (i.e. some sort of macro to refer to key, options, functions, etc.) - and b) reduce typing overhead. - - $pipe_split - - is neither fun to read nor to write. This would give us lots of - options to improve it (e.g. an automated index). We depend on - perl already to build docs, think about/look for simple perl - templating engine. - -* Find a way (XSLT?) to trim the TOC for the option reference; it's - ugly but we probably want to keep the TOC depth as-is for other - sections. - -Content -------- - -* Some sections maybe should be better grouped by topic, instead of - one section per task (e.g. hooks should be grouped under a section - 'hooks' in the config chapter). - -* Talk a lot more about character sets and encodings. diff --git a/imap/TODO b/imap/TODO deleted file mode 100644 index 44d0a0a3d..000000000 --- a/imap/TODO +++ /dev/null @@ -1,33 +0,0 @@ -IMAP enhancements, by priority: - -[ -- socket -- ] - -* Smarter connection code. Mutt should handle dropped connections/routing - problems gracefully. It should be able to transparently reconnect. This - is facilitated by the next item. - -* Interruptible socket calls, preferably without having to abort the - connection. For example large downloads could be chunked. - -[ -- browsing -- ] - -* We should maybe add a new imap_format string for IMAP browsing, without all - the stat variables but with tags like how many messages are in the folders, - how many subfolders, that weird \Marked tag, etc. - -[ -- speed -- ] - -* Partial index loading, using server-side threading and sorting - -* Partial message loading, including parsing BODYSTRUCTURE for the - view-attachments menu - -* Disconnected mode, probably based on an augmented header cache - -[ -- new mail detection -- ] - -* Possibly opening multiple connections for mailbox polling, now that - we have IDLE support. - -Brendan Cully -Updated: 20070409