[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: glob-expand-word and vi-command mode
From: |
Mike Jonkmans |
Subject: |
Re: glob-expand-word and vi-command mode |
Date: |
Sat, 3 Feb 2024 23:13:17 +0100 |
On Sat, Feb 03, 2024 at 03:43:45PM -0500, Chet Ramey wrote:
> On 2/2/24 9:39 AM, Mike Jonkmans wrote:
> > From the manual, glob-expand-word:
>
> glob-expand-word doesn't work that great in vi command mode, mostly for
> the reasons you suspect. What made you use it over the standard vi mode
> binding for `*' (vi-complete)? That behaves like POSIX says it's supposed
> to in vi command mode.
I made some mappings on all *-expand-* variations for the discussion
on shell-expand-case.
The '*' mapping seams more appropiate.
But the vi-command mode puts the cursor on the last character,
instead of one past it (as it is in vi-insert-mode).
That has the effect that '*' does not work easily.
If you type, in vi-insert-mode:
l s space <switch-to-command-mode> *
files starting with 'ls' will be completed.
Expected all files to be inserted.
Not sure if that is fixable.
--
Regards, Mike Jonkmans
Re: glob-expand-word and vi-command mode, Chet Ramey, 2024/02/03
- Re: glob-expand-word and vi-command mode,
Mike Jonkmans <=