[email protected] wrote in
<20220727133923.j07y9%[email protected]>:
|Steffen Nurpmeso <[email protected]> wrote:
|> [email protected] wrote in
|> <20220723203725.zwaiq%[email protected]>:
|>|I've build s-mailx in a container using the `crawl' branch and it worked.
|>
|> Oh! Well.. Not crawl, that is not working, only [next] you may
|> consider. crawl is broken (always -- it is a distributed horror
|> backup, as stated in README).
...
|Sorry Steffen, for my delayed reply.
Sure.
|Thanks for the explanation. I'll use the [next] branch when building \
|from source.
If you really want it the hard way, nice; it is very stable,
but beware of backward incompatibilities.
Note the function i posted will choose the shell variant for you,
because the version information is only updated by the release
script, it stands still at v14.9.24 until then. I in fact use
\if "$version-hexnum" -ge 0x0E00A000 || \
[ $version-hexnum -ge 0x0E009018 && "$features" =% ,+devel, ]
\call v14_10
\end
and always have the development option on, thus.
You may find it nice to be able to use the "local" command
modifier for things like the `mail' or `reply' commands, i in fact
now use
ca m \\local mail
ca r \\local reply
ca Lr \\local Lreply
where ca is "\commandalias ca '\'commandalias".
(Of course "local" still only covers variables and such, not
things like headerpick lists, alternates, or whatever.)
Ciao.
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
