Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15345 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2019-09-01 14:44 -0400 |
| Last post | 2019-09-01 14:44 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Idea: *.p<TAB> completion Chet Ramey <chet.ramey@case.edu> - 2019-09-01 14:44 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2019-09-01 14:44 -0400 |
| Subject | Re: Idea: *.p<TAB> completion |
| Message-ID | <mailman.284.1567363453.2075.bug-bash@gnu.org> |
On 9/1/19 2:29 PM, Dennis Clarke wrote: > On 9/1/19 11:10 AM, 積丹尼 Dan Jacobson wrote: >> $ ls *.pdf >> a.pdf b.pdf >> $ diff *.p<TAB> >> >> At this point <TAB> should complete "*.pdf". >> >> Or maybe as a bonus it could complete "a.pdf b.pdf" via a different key. >> > > So long as all these extensions and ideas get turned off by the env var > POSIXLY_CORRECT then the shell can make coffee for you. Why would the shell do that? POSIX doesn't have anything to say about emacs mode editing or word completion, so why would POSIXLY_CORRECT have any effect here? -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web