Hello in the Gregorian 2015 to all the beings who read this,
i've just fixed yet another segmentation violation and pushed the
fix to [master]: changing to an empty (new-year rotated) mailbox
as in "Fi+sent" with the settings
set folder-hook-+sent=fh-sent
define fh-sent {
localopts yes
set autosort=date showlast
}
will no longer crash on [master] (the particular bug existed since
the introduction of threaded display in nail(1) "[11.2] released
8/15/04". And [master] can also use the "~t" tilde escape without
entering an endless loop.
That comes to already three crashes [fixes: 309dea0, effb676 and
4064771] and one infinite loop [a105121] since 2014-09-16!
dict.cc gives: creepy, gross, scary, lousy and that list doesn't
even seem to be sorted (grumpy).
I want to announce that S-nail v14.8 will spring into existence in
late February or early March. It won't cover the promised list
and thread selection fixes. It is very likely that it won't cover
RFC 2231 nor further improvements on multibyte-handling (multibyte
/ mbrtowc() / stateful encoding support, as also in TODO).
I would however like to add shell-like ([ xy ]) && and || lists to
the if..endif statements and maybe i can fix the :colon modifier
selections. Because:
There will be no v14.9. On [crawl] i have already removed IMAP
support because, as i see it, these little-by-little steps will
never be sufficient to fix S-nail for real. I'm now actively
working on this codebase for about unbelievable 27 months, way
more than 20 months of which rather exclusively. I have to say
that in not that much more time i've implemented a C++ library
that is about three times of the size and has an incomparable
better level of quality from scratch. Whereas now i have the
feeling that with S-nail i just don't move:
$ find . -type f -name '*.c*' -o -name '*.h' -o -name '*.pl'|wc -l
423
$ wc -lwc `find . -type f -name '*.c*' -o -name '*.h' -o -name '*.pl'`
165052 583714 4249725 total
(S-nail is 49 and "51645 188138 1427448 total", respectively, on
[next] and 45, "45604 166985 1261781 total" on [crawl].)
Therefore: v14.8 will be the last major/minor release of the "old"
codebase. It has reached a pretty stable state and is backward
and forward compatible on the source code as well as on the
configuration level (like, e.g., the new *ssl-protocol* that
allows users to directly address the SSL library). More on that
in the announcement mail, then. As necessary an unimaginable
number of subminor/update releases will keep it going.
After v14.8 i personally will, on [crawl], use the scythe and go
down to the bottom --- and either come back with a new major/minor
release that i can truly stand and want to continue to work with
for the upcoming years, turning it into something really nice
(what i hope), or i'll perish in ugliness. :-) I think that can
only end up as something like a complete reimplementation and will
take rather two than one year. Maybe christmas 2016. That would
be nice.
Keep on going -- into the -right- left direction -- and
Ciao from Germany!
P.S.: on [next] one may use *ssl-verify*=ignore again, but don't
do that. :)
--steffen
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
S-nail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s-nail-users
