[email protected] wrote:
|*** Steffen Nurpmeso <[email protected]> [Fri, 22 Jan 2016 13:51:20 +0100]:
|>If not, you cannot overwrite
|>a CONFIG=, if you say CONFIG=MAXIMAL you cannot do
|>WANT_READLINE=yes, for example. I've just tried and for me "$
|>make WANT_READLINE=yes all" works on FreeBSD 10.2, giving me
|>colour and readline support.
|
|Well, make configure says that it enables readline and coloured
|messages, but when actually running s-nail I do not see any of this.
|Well, possibly there can be some issue with my environment. I use
Not really, if "make config" says it enabled readline then it
should have enabled readline and the S-nail command line should be
driven by it? And colour support changed, the commit message
says, and the NEWS entry will be along these lines:
Completely rework colour: add `colour' and `mono' commands..
v15 and above will be more feature rich (shall they ever be
reached). The next major release will not happen before 2017.
This is two years. And since S-nail has become pretty stable and
works pretty well too i'm hoping that it'll attract some people in
these forthcoming years. Assuming this really happens it seems
best not to use that hacky variable-based colour approach, it was
nothing but a quick hack around new years eve 2013/2014 in order
to honour John Dodson and Ypnose with some coloured output, but to
take some time and implement something that will last.
Like that we can make the colour stuff truly upwards compatible
today and can also support at least font attributes on monochrome
displays
(..I think i'll furtherly diversify this by adding a `colour256'
command, since the termcap/terminfo initialization happens after
the user configuration files are read, and thus there is no
possibility to query the number of colours from within there.)
|patched 14.8.6 now and it is fine. Just wanted to check the next branch.
Of course! You can easily use [next], there are no issues known
(moving [customhdr] onto it was a bit too fast; a single fix
yesterday affected the `customhdr' command when feeding the header
field body as multiple arguments), except that
*mime-alternative-favour-rich* is too stupid to face real life
yet. But it contains backward-incompatible fixes and changes, and
without looking over the output of "$ git log --oneline
master..next" you likely won't have a good experience. I'm sorry
that i sometimes can't support the "upgrading doesn't change
behaviour". :( I hope this will be possible after v15, though.
--steffen
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
S-nail-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/s-nail-users
