[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readabl

From: Linda Walsh
Subject: Re: bug? "type -P xxx" returns "xxx" that isn't executable...(or readable)
Date: Mon, 04 Aug 2014 23:35:06 -0700
User-agent: Thunderbird

Chet Ramey wrote:
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?)...

This just isn't true.  TAB is bound to `complete' when you disable posix
mode with `set +o posix'.  Since the only binding that gets changed when
enabling or disabling posix mode is the one for TAB, any other characters
you have bound to `complete' retain their bindings.

I dunno why, maybe it's a 4.2 thing?  But I hit tab and it
was still inserting and  backquote (my substitute complete)
did nothing....Now that I know about it I can avoid it, but
it does limit the ability to pick working features like
type -P only returning executables out of the posix set.

Why anyone would want the broken functionality I dunno... maybe that
can be added to some queue since it works in posix shouldn't
be too difficult to fix in non-posix.

 There are a
couple of ways to handle the issue you've raised, but it has not surfaced
as a problem before, so it doesn't have a high priority in the work queue
right now.
I would think that many or most problems posted here are new.
In this case, I was trying to ensure some other problem wasn't happening
(in the boot script -- wanted to make sure it wasn't running
in posix mode)...during testing found my completion key unmapped...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]