On 2021-12-04 12:39:41+0000, Jason McIntyre <jmc@kerhand.co.uk> wrote:
> On Sat, Dec 04, 2021 at 12:19:34PM +0100, Richard Ulmer wrote:
> > Hi all,
> > I've been reading up on "advanced" less(1) features and came across the
> > lesskey(1) man page. In the COMMAND SECTION of the page I read this:
> >
> > > The action is the name of the less action, from the list below.
> >
> > However I cannot see this list of available actions. The only thing
> > similar I can find is the list of default commands with their actions.
> > From this I can deduce some available actions, but I'm not sure if those
> > are all the available actions. Maybe there are some actions that are not
> > bound by default. I'm also missing a description of what the actions do
> > (I don't know all the default less(1) commands off the cuff).
> >
> > Is the action list missing from the lesskey(1) man page, or am I
> > misunderstanding something?
> hi.
>
> the actions do indeed match those in the command list. whether there are
> any undocumented ones, i don;t know. i suppose you'd have to go poking
> in the source. the actions will roughly match those described in the
> less(1) COMMANDS section. so for example in less(1):
> [....]
>
> however we still import less. i'd want to make sure that's not stepping
> on anyone's toes to make local changes.
Pls forgive if I'm missing the important points, but in a way, maybe it is
implied by man lesskey that the actions are
connected with the command list shown. On ~ line 56-57 (under COMMAND
SECTION) it says "The string is the command key(s) which invoke the
action", which is easy to miss. Then there follows a list of commands,
and one can search the man pages (with /) for everything that mentions "command",
type "h" within less, etc. I find I have to do kind of thing that often to get a
better idea of things, if one idea is mentioned in one part (or man
page) then I need to go read other parts (or pages) that discuss the
same thing; I even made a couple of scripts or aliases that quicken the
process for me.
No comments:
Post a Comment