2 Before you start making additions to (Heirloom mailx and) S-nail,
3 subscribe to the development mailing list at
4 <https://lists.sourceforge.net/lists/listinfo/nail-devel>
5 to coordinate your efforts with the maintainer and other people.
7 Backward-compatibility breakers
8 -------------------------------
10 - Is anybody actually using the NSS code? Does this still apply?
11 Check and verify -- or remove it!
12 [Note: due to lack of personal interest... Please complain.]
13 - Recipients specified on the command line should be added to those
14 specified in the message when the -t option is set.
15 - The -q option makes me sad as it doesn't use *indentprefix* for the
16 quoted file. So either there should be -Q which does so, or -q should be
17 changed. Also see ~R below.
18 [Note: i think i go for the latter. Please complain.]
19 - NetBSD mailx(1) removes all recipients in up Cc: and To: that are also
20 specified in Bcc. At least configurable.
21 [Note: i plan to make this default. Please complain.]
22 - At least optionally disallow silent discarding of invalid addresses,
23 i.e., cause sending to be aborted if not all recipient addresses pass the
25 And shouldn't it generally be marked as an error and reported when the
26 program exits? At least in non-interactive mode?? Yet there is no
27 indication that anything has happened at all!
28 [Note: i plan to report error in non-interactive mode. Please complain.]
29 - POSIX says that, when written to DEAD: "If the file exists, the message
30 shall be written to replace the contents of the file". This is mentioned
31 for ASYNCHRONOUS EVENTS, but it's the only description of what should be
32 done in which way to DEAD. savedeadletter() yet appends.
33 - Furthermore, *all* file operations yet append, even recipient target
34 files are appended. I don't know if this is really desirable behaviour,
35 but i have not thought about that for real. Maybe this should be at
41 - [v13:started] Reformat the manual.
42 roff style is fine, but lines should be ~70 characters, not only ~25.
45 - Make it possible to reply to/save/write/xy part X.Y[.Z] by allowing its
46 specification directly, as in, e.g., ':w 1.2'. (Martin Neitzel)
47 - I want to have a ~R tilde command that works like ~r except it performs
48 quoting of the input just as ~m does. Also see -q above.
49 - Offer the possibility to work with certificate fingerprints instead of
50 full certificates, in equal spirit to the current maintainers S-Postman
51 and Mercurial. S-nail(1) could simply offer something in equal spirit to
52 the formers --fingerprint, so that no other tool is necessary for
53 certificate management (for secure transport at least).
54 - Think about a name bypass hashmap cache, and whenever we have to skin or
55 nalloc() or whatever, look in there. Maybe even an additional link for
56 non GFULL(/GSKIN) and fully skinned struct name objects.
57 The amount of duplicated work in this codebase if frustrating, but the
58 real healing would make necessary a complete rewrite of the name handling!
59 Such a cache would work without touching the current code flow ... or
60 allow a smooth transition to a new one anyway.
61 - It would be nice if it would be possible to define a format string for
62 *quote*, like 'set quote="format=some formats"'.
63 - Deal with faulty message selection that may occur when selecting threads
64 via & (when at least mixed with other selectors).
65 - On the long run -- try to add command line editing.
66 - For those who use S-nail(1) only with a MTA it may be desirable to have
67 some "smopts" expansion mechanism in equal spirit to NetBSD mailx(1).
68 - While talking about NetBSD mailx(1), the author can imagine that being
69 able to use the optional -H:xy stuff is sometimes nice.
70 - Add the possibility to simply place whatever header in the editor (and
71 in the mail read in due to the -t command line option, and...).
72 - Check against RFC 5322.
73 Really recheck all the header parsing code.
74 - What about RFC 6531?
75 - Check against newest POSIX.
76 - Maybe add a bash(1)ish POSIXLY_CORRECT (or so) switch that can be used to
77 disallow extensions (e.g. specification of "full" addresses on command
79 - Maybe there should be an additional ZOMBIE directive that is served in
80 equal spirit to DEAD, but that could be a valid MBOX... ?
81 What i want is a *real* resend, best if possible from command line.
82 Meaning, also the possibility to postpone a message.
83 - mime.c:prefixwrite() tracks state internally instead of having a cookie
84 argument. That doesn't really make sense. Either it is capable to work
85 with multiple files concurrently and prefix-quotes them correctly in the
86 same fashion, or it doesn't track anything at all. It even tracked those
87 calls that do not write a prefix at all before, just to make this
88 mechanism work ... Or not? Well, if you track the last file and if there
89 was a newline last, and you switch files, then the last newline state is
90 lost, and you do write the prefix even if in the other file there was no
91 newline last. I'm confused now. Change this, please.
94 + Add C99-likeish typedefs for integers and use them everywhere.
95 + Don't use magic constants/values.
96 + Try to thin out the onion and reduce work that is done over and over
97 again. Maybe introduce objects to represent header[field/body] and
98 content and find a way to pass those all through that vegetable.
99 + The current codebase assumes that in multibyte encodings plains ASCII
100 characters can be tested "as-is". This assumption is wrong for some
101 encodings that use U+001B (escape) or another ASCII thing to introduce
102 shift states. The only real solution to this problem would be to
103 rewrite the entire codebase and use wide characters (IMO) everywhere.
104 + Document the functions in the interface declarators.
105 + [v13:started] Resort the functions and where they are implemented.
106 It's really terrible. Just think about outof(), savedeadletter(),
108 - The current maintainer doesn't like longjmp()s.
109 - The current maintainer doesn't like signals.
110 - The current maintainer would like to see that compilation with a C++
111 compiler is possible, though that would be a long way and be especially
112 problematic due to the (C ish) way enums are used. He never understood
113 why there is not "bitenum", btw.
114 - The current maintainer worked with all-tabs for almost one and a half
115 decade and turned over to all-spaces afterwards.
117 vim:set fenc=utf-8 syntax=txt ts=8 sts=2 sw=2 et tw=75: