Hello,
There is a small bug in the default completion system due to a
disagreement between a few functions in what is considered a command
delimiter. I have tested this on the current devel HEAD in the git repo
(d00a2d6).
Define a default completion:
_completion_loader() {
complete -
Hi,
Sarnath K - ERS, HCLTech wrote:
> I see this problem in the latest Bash 4.2 as well. Say, I invoke
> "rbash" or "bash -r". This leaves me in a restrictive shell.
> However, this restrictive shell allows me to run "bash" or any other
> shell (without execing - just simply run) which leaves me
Sarnath K - ERS, HCLTech wrote:
> Apart from this, BASH Documentation says "When a command that is
> found to be a shell script is executed (see COMMAND EXECUTION
> above), rbash turns off any restrictions in the shell spawned to
> execute the script.".
>
> Does this mean that a guy with restric
On 1/11/12 6:12 AM, Jonathan Nieder wrote:
> Hi,
>
> Sarnath K - ERS, HCLTech wrote:
>
>> I see this problem in the latest Bash 4.2 as well. Say, I invoke
>> "rbash" or "bash -r". This leaves me in a restrictive shell.
>> However, this restrictive shell allows me to run "bash" or any other
>> she
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -DCONF$
uname output: Linux ubuntu 2.6.32-24-generic #39-Ub
Hello Jonathan,
Thanks for the quick hint.
What I understand is that you are suggesting me to collate all required
commands in a special directory and then use it in the PATH and remove
everything else from the PATH in ".bashrc".
I think that would really serve my purpose. Thanks!
As far as c
Clark J. Wang wrote:
On Fri, Jan 6, 2012 at 00:33, Peng Yu wrote:
But beware to clearly document these by giving working
EXAMPLE code which include these three commands (not just text
explanation without working code, by "working code" I mean code
snippet is discouraged, a complete completio
On 1/11/12 3:03 PM, Linda Walsh wrote:
> Like... compat40 mentions it changes behavior, about interrupting a command
> list, yet try to find out what that behavior is, or what compat40 would
> change it 'to'?
Thanks, I added that to the description. It means that bash versions
later than 4.0 in
