On Tue 30 Jan 2024 at 10:34:21 (+0700), Max Nikulin wrote: > On 30/01/2024 02:51, David Wright wrote: > > . Press HOME, > > . Type any letter that makes a "wrong" command name (eg aokular), > > . Press END, > > The escape "Esc /" workaround has been posted in this thread already.
Yes, I believe I posted it. But if you have a long path with many ambiguous branches along the way, using Esc / gets very tedious because you get no help with choosing what character to write next. Tab Tab doesn't do anything until you reach a directory with "candidates" in it (ie files with appropriate extensions). But even then, Tab Tab does the wrong thing. It only lists the candidates, not any directories that can continue the path further. However, using my "wrong" command method, Tab Tab lists are complete all the way down the path. You can then correct the command in order to prune the Tab Tab listing to include just the candidates (and in preparation for actually executing the command, of course). > It uses built-in readline path completion instead of BASH programmable > completion. It may be available as [Alt+/] (in xterm it requires > xterm*vt100.metaSendsEscape: true) > > [Ctrl+A] and [Ctrl+E] are alternatives for [Home] and [End]. > > For details see the BASH manual > > info '(bash) Commands For Completion' > > "complete-filename" function and other sections related to readline > and completion. > https://www.gnu.org/software/bash/manual/html_node/Commands-For-Completion.html#index-complete_002dfilename-_0028M_002d_002f_0029 To Greg: Thanks for explaining Michael's true motives. Cheers, David.
