Hello list, you get an announcement mail from a bitterly unhappy Steffen -- that is three times a lady (what i can tell you)! So, *unfortunately*, i'm announcing S-nail(1) v14.4.3. This is a bug-bug-bugfix release of v14.0.
The release tarball can be downloaded (e.g., via 'curl -vv -L') from, and its checksums are: <http://downloads.sourceforge.net/project/s-nail/s-nail-14_4_3.tar.gz> <https://downloads.sourceforge.net/project/s-nail/s-nail-14_4_3.tar.gz> MD5 = ecd7679edab0c7ad86ee6eae911f6493 SHA1 = 39fdade9b622a6addc5e70a5d929b0bc5ef49d00 SHA256 = 04a16a0df1df60db3e043baf3332b34356fbf99546620afdfdf11a0bc0a18d4d Online manual: <http://sdaoden.users.sourceforge.net/code-nail.html> [Web site : <http://sdaoden.users.sourceforge.net/code.html#s-nail>] git(1) repo : <git.code.sf.net/p/s-nail/code> git(1) browse: <http://sourceforge.net/p/s-nail/code/> The NEWS entry for 14.4.3 can be found below. The complete changelog of commits in between s-nail-14.3.2 and s-nail-14.4.3 can be inspected by using the git(1) `log' command: All commits: $ git log --reverse --topo-order s-nail-14.3.2.. Only topic branch headers: $ git log --oneline --merges --reverse s-nail-14.3.2.. Only the commits of the topic branches: $ git log --oneline --parents --merges --reverse s-nail-14.3.2.. | > while read c1 c2 c3 c4 c5 c6; do > echo "Topic branch: $c6" > git log --no-merges --oneline ${c1} ^$c2 > echo > done (This works with `git version 1.8.4-rc0'; since those guys have simply reversed the output of `rev-parse' somewhen after 1.7.?, breaking my git-topic-creator.pl, i can't give any promise.) v14.4.3, 2013-10-02 ------------------- I convey special thanks to Karol Błażewicz and Gaetan Bisson. - The new build system didn't allow to overwrite CFLAGS= when used in conjunction with GNU make(1). To make a long story short, removing a `.POSIX:' directive from the makefile fixed the problem. Luckily. [e6b26526] - More INSTALL notes for UnixWare 7.1.4, which suffers from the same problem: here the fix is to use the -e option of make(1). - Karol Błażewicz reported a segmentation violation he got when using an Arch Linux S-nail test package, and Gaetan Bisson informed me about that. The problem was that we didn't assign the resulting default USER@HOST address (which gets used when *from* is not set) to the function return value that actually ets used, effectively resulting in a NULL dereference. (It was a bug i've introduced in december 2012 due to sloppiness.) [cfd60479] v14.4.2, 2013-09-21 ------------------- Many thanks to Paul Vojta. - On GNU/Linux there is no MAXPATHLEN constant defined by default, as this is a non-standard legacy constant. Mozilla ran into this some time ago, though a bit different [1]. It made it easier for S-nail. [1] <https://bugzilla.mozilla.org/show_bug.cgi?id=412610> We could include `sys/limits.h' to get at MAXPATHLEN, there it is defined to be PATH_MAX, but let's just include the standard `limits.h' and ensure MAXPATHLEN ends up >= PATH_MAX. With this condition being true even FORTIFYd sources won't bail with reported buffer overflows because realpath(3) expects a buffer of PATH_MAX bytes. [bee5e57c] (Paul Vojta) - With the builtin LINE_EDITOR, ensure proper interaction with GNU rlogind(8), which is alone in its quest to set the ISTRIP termios(4) flag. [61e00f2d] - Bugfix a codepath that would have prevented compilation when HAVE_ICONV is not set. While there, allow to unselect message attachments when using the `~@' tilde command interactively, which i mysteriously had forgotten when allowing selection of 'em. (oops?) [4f58ffea] - It's now easier for packagers to get at debug-enabled CFLAGS; simply use WANT_ASSERTS=1 (should not be enabled in shipouts, please). [d8663406] - Fixed a terrible bug that i've introduced in november 2012, that would have corrupted MBOX files when using the `resend' command. (The so-called "From_ line" would have been quoted to ">From_ line" instead of simply being stripped.) [19d449e2] - Fixed a SIGSEGV for the builtin LINE_EDITOR, that would have occurred if a history traversal (^B or ^F) would have been continued by a reverse history completion (^R). While there, avoid some multiple-beeps-in-a-row that yet occurred due to code reuse, and document that ^G etc. reset the multibyte state machine. [003d9f6f] Also, the expand-on-tab code could have excessed line input maximums, e.g., after `? /usr/bin/*<Tab>'. This was of course known, but i wanted to keep it because all tested (modern) terminals "mess up but won't break", and thus made it possible to use the data, even if it's visual representation was messed up. The real solution will be much, *much* more complicated, i.e., show possible *completions*, page-wise, etc., i.e., just like is known by tab *completion*. This will need far more time because it doesn't make sense to embed such complicated code into the current bed. Now i've chosen to simply don't display excess, but replace the content with a message that says that there was excess. It simply looks better. [0320c8ba] - I've changed the use of `[?]' as a replacement sequence for invalid / non-displayable characters to `?' (again). There are still code paths (from the original codebase) which use the real Unicode replacement character instead, so our display is still not unique. On the long term the codepath can anticipate in all levels wether use of Unicode is possible, so that, then, we will be unique again, using either only `?' or the Unicode replacement character. [faf6380] - I've anticipated in v15.0 and implemented *quote-fold* as a stream filter. It is now multibyte safe and takes into account the visual width of characters, i.e., ideographs etc. It is working almost as good as an algorithm can work that looks at data linewise, but is yet experimental and incomplete in that it will break lines even if only whitespace or a backslash escape follows. It is code that is only a few hours old, which is why it is not enabled by default. [ v14.4.1, 2013-09-14 ------------------- How terrible. - Fix some harmless stylos and typos in the manual and `conf.rc'. [1a6b880, 417b066] - Ensure *complete* proper cleanup on signal-caused configuration run aborts. [7a08bda] - Bugfix: reenable empty configuration variable overrides, as in $ make install SID= NAIL=mailx ... [171861d] - Bugfix: rename the `conf.rc' variables SHELL, LISTER and PAGER because they clash with the POSIX standard variables of the same names, which hurts now that the configuration is run through the shell itself. The configuration names are now XSHELL, XLISTER and XPAGER (ouch). [ef93c4e] - nail.rc: comment out some non-portable S-nail(1) specifics, for those who install this file as mailx.rc or so, somewhere. [3f14b01] - From now on S-nail will use simple version tags, as, e.g., `14.4.1', i.e., no more `s-nail-14.4.1'. [a75437d, 183d59c] (Jürgen Daubert) Also move UAGENT out of `version.h' [f7be5be] Uh! v14.4 must have originated in a bad dream; good it's vanished. v14.4, 2013-09-13 ----------------- Thanks to the entire vivid and virile S-nail(1) user community is proper, especially Stephen Isard, Gavin Troy, Martin Neitzel. Not to forget Ryan Kavanagh and Ayan George. Note this time the changes are in reverse order, i.e., oldest first. Topic Branches ^^^^^^^^^^^^^^ 15fbe09 ^bf9173f 'topic/varmac-unite' Simplification and unification of variable and macro handling 40f6f58 ^15fbe09 'topic/cledit1' Command line editor; new manual section `Line editor' ad28a32 ^40f6f58 'topic/termsize' Honour POSIX mailx(1) and respect $COLUMNS and $LINES on startup dc3cd49 ^a446fd8 'topic/qf' You don't wanna know b8738f7 ^0651fd0 'topic/spam1' Interaction with SpamAssassin; new manual section `Handling spam' 5419d6f ^b8738f7 'topic/make1' Reworked build system; please read `INSTALL' and `conf.rc' 9ab4d6b ^5419d6f 'topic/list1' Slightly tweaked message thread display, fix `:u :r' to mean it ChangeLog ^^^^^^^^^ - The default PAGER is now more(1). (But read on.) - The `echo' command is now compliant, and fully supports XSI. - The `group' and `ungroup' command aliases have been removed, they are `alias' and `unalias'. - We now have the capability of line editing and history. One may choose from not less than three different implementations: a builtin editor as well as possible linkage against BSD editline(3) and also a GNU readline(3) compatible layer. Please read the new manual section `Line editor'. Input is now compliant in that an interactive line may be continued after escaping the newline character with a backslash. [topic/cledit1] (all of them) The *prompt* variable may now contain shell escapes, just like the `echo' command. [0938d8a] As a special extension the new \? escape, when used within *prompt*, will expand to the exit status of the last command. [41076d2] - The POSIX standard environment variables $COLUMNS and $LINES are now honoured upon startup. [topic/termsize] - The `help' / `?' commands now support abbreviation, i.e., ``$ ? unc'' should now find `uncollapse'. [7b86195] - The `~' abbreviation that has been introduced as an alias for `call' is now a real command, not a magic shortcut. [9987289] - The new variable *quote-as-attachment* can be used to additionally embed the quoted message as a `message/rfc822' MIME attachment. [topic/qf] - The compose-mode command `~@' will now attach messages from the current mailbox if given a filename of the style `#NUMBER'. Please read the corresponding manual section `Tilde escapes', though. - The `WANT_JUNK' and `WANT_SCORE', as well as Gunnar Ritters junk mail management have been removed. Instead S-nail(1) can now support interaction with SpamAssassin, but sofar only via the spamc(1) / spamd(1) client / server pair of programs that ships as part of SpamAssassin. The new configuration directive `WANT_SPAM' controls wether this feature is desired. Please read the new manual section `Handling spam'. [topic/spam1] (Martin Neitzel) (S-nail(1) is now *definitely* floating-point free.) - The configuration and make system have been overhauled / reorganized. The configuration is now in `conf.rc', also contains directives like `PREFIX' etc, and is always read in. However, only those directives which are not yet set (via environment or command line overwrites) are incorporated into the set of configuration options. Therefore $ make WANT_IMAP=0 $ make WANT_IMAP=1 will now build S-nail(1) twice, because of the changed configuration. Note that `WANT_GSSAPI' is now by default disabled, which shrunk a freshly started s-nail image by more than 30 percent. We're not finished yet in that there is no dependency graph etc. Please do read `INSTALL' and `conf.rc'. [topic/make1] - Message selection has been slightly bugfixed in that `:u :r' really means `:u' AND `:r'. Compared to NetBSD Mail(1) it's still a shame. Threaded message display has been slightly changed in that within a thread identical Subject: lines are not repeated. It may not be perfect yet due to the general list / thread state. [topic/list1] - If, upon startup, the environment variable `NAIL_NO_SYSTEM_RC' is set, then the system wide initialization file isn't read, just as if the `-n' option had been given. [1b31535] - It is now possible to use CTRL-C during connection hangs. (But in general error recovery capabilities of the socket related infrastructure is non-existent, practically speaking.) [45a9f36] - *quote-fold* has been temporarily disabled, as it is not multibyte safe. No review for v14.4. And today is Friday, the 13th. Ouuuh! --steffen ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk _______________________________________________ nail-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nail-devel
