[email protected] wrote in
<[email protected]>:
|Steffen Nurpmeso <[email protected]> wrote:
|
|> Steffen Nurpmeso wrote in
|> <20250402072227._JET9ENL@steffen%sdaoden.eu>:
|>|[email protected] wrote in
|>| <[email protected]>:
|> ...
|>||Lurking the manpage, I see I can have a bunch of things in it.
|>||I already added some basic stuff (such as record) but I am curoius \
|>||to see what experienced users have in there .mailrc (or is it .s-nail.rc\
|>|| \
|>||BTW?).
|> ...
|>|I will attach that file, but it will surely be a bit confusing for
|>|a beginner.[.]
|>
|> Seeing it fly by it is worse, .. it is horrible.
|> Sorry for that.
|
|That's the most cryptic configuration file I have ever read ! :)
|
|I will need quite some time to digestify it. Even quite a lot.
Sorry. It should be sorted by version top-down not down-top. The
macros which relate to version numbers at least, that is.
It is likely that you possibly want to look at the key binding stuff
(see `bind'), maybe `colour's (config says `col'), and the
`headerpick' stuff (config says `hp'). And the *fullnames*
variable, i always was in despair with BSD Mail until i realized
i need this. The manual section "A starter" can hopefully be
that. And three short things are maybe of help:
1. All BSD Mail / POSIX mailx can abbreviate commands.
Some shortforms are even standardized, the manual shows these
in parenthesis, for example the `copy' command can be shortened
to `c', but other than that first-match-wins.
If you type `list' (or `l') then the list of commands is
printed, in lookup order (ie not 100% alphabetically to satisfy
the standardized abbreviations).
2. S-nail adds `commandalias'es which are looked up first.
This works recursively, for example i have
commandalias ca '\commandalias'
ca m mail
ca mail '\local mail'
then when i type
? m
m -> mail -> '\local mail'
3. S-nail adds command modifiers. The insane amount of backslash
you see (if you look) preceding commands is such a modifier, it
avoids commandalias lookups.
(At the end of the line, as the last character, it allows to
continue the current line on the next line.)
The "local" you see above is also a command modifier, but it is
not available in v14.9.25. ;}
x. I can only recommend to have a big fat
set v15-compat=y
very early or first, as this bends some things towards the
feature. It will be the default in v14.10.
In v14.9.25 you can create a macro
define __xv {
# Before v15: need to enable sh(1)ell-style on _entire_ line!
localopts yes;wysh set verbose;ignerr eval "${@}";return ${?}
}
commandalias xv '\call __xv'
and then you can get at least a little bit of command contexts
if you say
xv ? set
then you "get more" than with plain `?'.
Also for example with `varshow' as in
var charset-8bit
vs
xv var charset-8bit
In v14.10 the above is
define xverbose {
\local se verbose; eval ignerr local pp "$@"; \return $?
}
which shows a tremendous improvement of the state machinery,
but looks very cryptical still.
|-- Xavier
I take Isle of Man by the word.
Ciao and many greetings!
--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)
