adding a lintian override for the mutt Exec path in the desktop file

[software/mutt-debian.git] / doc / TODO

diff --git a/doc/TODO b/doc/TODO
index 76b0c38cf703c7c37704541bc76cd26073344c17..75b9596b6ab3e57ca5e5e8411bd128cecc7ffe01 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -17,8 +17,7 @@ Style/Technical
 
     If the filename ends with a vertical bar (|)
 
 
     If the filename ends with a vertical bar (|)
 

-  We need to choose either style and use it. Probably we want to add
-  a short typography section explaining layout details.
+  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.)
 
 * Think about some way of templating to a) help improve consistency
   (i.e. some sort of macro to refer to key, options, functions, etc.)


@@ -31,12 +30,6 @@ Style/Technical
   perl already to build docs, think about/look for simple perl
   templating engine.
 
   perl already to build docs, think about/look for simple perl
   templating engine.
 

-* Maybe add a mutt.css to contrib to make it look better.
-
-* As for sending patches, maybe add a short text file for documentation
-  hackers with guidelines. (Though nobody really seems to provide input
-  on the manual)
-

 * 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.
 * 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.


@@ -44,12 +37,6 @@ Style/Technical
 Content
 -------
 
 Content
 -------
 

-* Especially the introduction needs to be reworked quite a bit,
-  the current reference-like way is unfriendly for new users. There
-  should be an introduction chapter explaining concepts (config, menus,
-  hooks, etc.) E.g. the intro for hooks should come _before_ their
-  syntactical definition, not after.
-

 * 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).
 * 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).