|
From: | Linda Walsh |
Subject: | Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable) |
Date: | Mon, 04 Aug 2014 11:27:37 -0700 |
User-agent: | Thunderbird |
Chet Ramey wrote:
Then go back -- the TAB key is unmapped as a completion char, but your old completion key is not remapped. So you end up with no completion keys. There are probably lots of other "one-way-adjustments", but I haven't hit them all.I'm going to guess that this is the same problem I discussed in http://lists.gnu.org/archive/html/bug-bash/2014-06/msg00049.html but the description above pretty much makes a hash of it.
--- So because I am using the POSIX default for tab to self insert, if I switch in+out of posix mode, you wipe my default? Just because I happen to have the same default as posix is no reason to wipe it when leaving posix. I mean why doesn't bash store the value the user had before entering posix and restore it when leaving? The double problem is that tab is no longer bound to anything when you leave posix -- you don't get your original completion char back, and TAB isn't activated as a new completion character, so completion gets disabled. Surely that can't be desirable? (i.e. despite how bash got there -- understandable, shouldn't it be fixed?)...
[Prev in Thread] | Current Thread | [Next in Thread] |