Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16713
| From | Ilkka Virta <itvirta@iki.fi> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Expand first before asking the question "Display all xxx possibilities?" |
| Date | 2020-08-06 17:11 +0300 |
| Message-ID | <mailman.1009.1596723074.2739.bug-bash@gnu.org> (permalink) |
| References | (1 earlier) <f507d245-af9c-3c41-9c19-acff9735e703@case.edu> <rgf0sa$c3f$1@ciao.gmane.io> <fa0e51f8-6ee3-c80e-d6d0-9be9561667e5@iki.fi> <81399d97-eba6-17ca-fd2b-7fbb420c8314@case.edu> <b932b572-2c2e-7edd-09c6-70f0089890be@iki.fi> |
On 6.8. 15:59, Chet Ramey wrote: > On 8/6/20 8:13 AM, Ilkka Virta wrote: >> I think they meant the case where all the files matching the given >> beginning have a longer prefix in common. The shell expands that prefix to >> the command line after asking to show all possibilities. > > Only if you set the "show-all-if-ambiguous" readline variable explicitly > asking for this behavior. Readline's default behavior is to complete up to > the longest common prefix, then, on the next completion attempt, to note > that there weren't any additional changes to the buffer and ask if the user > wants to see the alternatives. Dan wants a change in the behavior that > variable enables. Right, sorry. I do have it set because otherwise there's a step where tab-completion only produces a beep, and doesn't do anything useful. I didn't realize causes partial completion to be skipped too. -- Ilkka Virta / itvirta@iki.fi
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Expand first before asking the question "Display all xxx possibilities?" Ilkka Virta <itvirta@iki.fi> - 2020-08-06 17:11 +0300
csiph-web