> You will need to source the file that contains the functions:
>
> source /etc/bash_completions
>
> The installation you did most likely added something like this to your
> ~/.bashrc:
>
> # enable programmable completion features (you don't need to enable
> # this, if it's already enabled in /etc/
On Fri, 21 May 2010, Peng Yu wrote:
> On Fri, May 21, 2010 at 11:19 AM, Marc Herbert wrote:
> > Le 21/05/2010 16:25, Peng Yu a ?crit :
> >> When I type something after 'which', something means a command.
> >> However, bash doesn't do command completion for the argument after
> >> 'which'. Is ther
On Fri, May 21, 2010 at 12:07 PM, Eric Blake wrote:
> On 05/21/2010 10:41 AM, Peng Yu wrote:
>>> 'help complete' is the easiest way to see the short details; other than
>>> that, look for complete under 'SHELL BUILTIN COMMANDS' in the man page.
>>
>> I see the following error. What is wrong with m
Greg Wooledge wrote:
On Fri, May 21, 2010 at 01:32:26AM -0700, Linda Walsh wrote:
Does something need to happen for case to be ignored in wildcards, on this
file
system?
Have you tried shopt -s nocaseglob yet?
That would do a wild card match for all file systems -- not just the ones that
Chet Ramey wrote:
On 5/21/10 1:00 PM, Roman Rakus wrote:
There are patches 6 and 7 available for bash-4.1.
I don't see any announce, are they official? I just want to be sure
:)
I usually put patches on the ftp sites around a week before I announce
them on bug-bash, to give myself time to fix
On 05/21/2010 07:22 PM, Chet Ramey wrote:
On 5/21/10 1:00 PM, Roman Rakus wrote:
There are patches 6 and 7 available for bash-4.1.
I don't see any announce, are they official? I just want to be sure :)
I usually put patches on the ftp sites around a week before I announce
them on bug-
On 05/21/2010 10:37 AM, Peng Yu wrote:
> On Fri, May 21, 2010 at 11:19 AM, Marc Herbert wrote:
>> Le 21/05/2010 16:25, Peng Yu a écrit :
>>> When I type something after 'which', something means a command.
>>> However, bash doesn't do command completion for the argument after
>>> 'which'. Is there
On 5/21/10 1:00 PM, Roman Rakus wrote:
> There are patches 6 and 7 available for bash-4.1.
> I don't see any announce, are they official? I just want to be sure :)
I usually put patches on the ftp sites around a week before I announce
them on bug-bash, to give myself time to fix any distribution p
On Fri, May 21, 2010 at 11:37:59AM -0500, Peng Yu wrote:
> Since pwd is a shell command, when /bin/pwd is actually used? In
> shells that don't have built-in pwd?
The primary reason it exists as a separate program is for strict
conformance to POSIX and other standards, which require the presence o
On 05/21/2010 10:41 AM, Peng Yu wrote:
>> 'help complete' is the easiest way to see the short details; other than
>> that, look for complete under 'SHELL BUILTIN COMMANDS' in the man page.
>
> I see the following error. What is wrong with my bash?
Nothing is wrong with bash. Bash is telling you
There are patches 6 and 7 available for bash-4.1.
I don't see any announce, are they official? I just want to be sure :)
RR
On Fri, May 21, 2010 at 11:06 AM, Eric Blake wrote:
> On 05/21/2010 09:50 AM, Peng Yu wrote:
>> complete -c works. I'm not familar with bash-completion package. How
>> to customize search path for each command.
>
> By using appropriate complete invocations for each command, and lots of
> shell fun
On Fri, May 21, 2010 at 11:19 AM, Marc Herbert wrote:
> Le 21/05/2010 16:25, Peng Yu a écrit :
>> When I type something after 'which', something means a command.
>> However, bash doesn't do command completion for the argument after
>> 'which'. Is there a way to configure bash behave depending on t
Le 21/05/2010 16:25, Peng Yu a écrit :
> When I type something after 'which', something means a command.
> However, bash doesn't do command completion for the argument after
> 'which'. Is there a way to configure bash behave depending on the
> context (in this case, do autocomplete after 'which')?
On 05/21/2010 09:50 AM, Peng Yu wrote:
> complete -c works. I'm not familar with bash-completion package. How
> to customize search path for each command.
By using appropriate complete invocations for each command, and lots of
shell functions.
>
> For exmaple, I want search in $PYTHONPATH after
On 5/21/10 11:25 AM, Peng Yu wrote:
> When I type something after 'which', something means a command.
> However, bash doesn't do command completion for the argument after
> 'which'. Is there a way to configure bash behave depending on the
> context (in this case, do autocomplete after 'which')?
Yo
On Fri, May 21, 2010 at 10:39 AM, Chet Ramey wrote:
> On 5/21/10 11:25 AM, Peng Yu wrote:
>> When I type something after 'which', something means a command.
>> However, bash doesn't do command completion for the argument after
>> 'which'. Is there a way to configure bash behave depending on the
>>
On 05/21/2010 09:25 AM, Peng Yu wrote:
> When I type something after 'which', something means a command.
> However, bash doesn't do command completion for the argument after
> 'which'. Is there a way to configure bash behave depending on the
> context (in this case, do autocomplete after 'which')?
When I type something after 'which', something means a command.
However, bash doesn't do command completion for the argument after
'which'. Is there a way to configure bash behave depending on the
context (in this case, do autocomplete after 'which')?
--
Regards,
Peng
Greg Wooledge wrote:
On Fri, May 21, 2010 at 01:32:26AM -0700, Linda Walsh wrote:
Does something need to happen for case to be ignored in wildcards,
on this file
system?
Have you tried shopt -s nocaseglob yet?
That would switch if of for all file systems, woulödn't it? Not what the OP
was lo
On Fri, May 21, 2010 at 01:32:26AM -0700, Linda Walsh wrote:
> Does something need to happen for case to be ignored in wildcards, on this
> file
> system?
Have you tried shopt -s nocaseglob yet?
Le 21/05/2010 09:32, Linda Walsh a écrit :
> I'm not sure if this is bash specific...I'd wager not, but I'm not sure where
> to
> put it.
I guess it is not.
> I created an xfs file system with the naming version=ci, (case-ignore) flag.
>
> This causes it to match filenames with case ignored.
>
I'm not sure if this is bash specific...I'd wager not, but I'm not sure where to
put it.
I created an xfs file system with the naming version=ci, (case-ignore) flag.
This causes it to match filenames with case ignored.
So an exact match of a file name matches with the case begin ignored,
i.e. '
23 matches
Mail list logo
