>
> Faheem Mitha wrote:
>
>> $ cd --help
>> bash: cd: --: invalid option
>> cd: usage: cd [-L|-P] [dir]
>>
>> I'm don't even know how to get the usage output without
>> inducing an error.
>
> Does "help cd" do the trick?
>
No. ''help cd'' does the trick.
Regards,
Matias.
Chet Ramey wrote:
It was a mistake to allow such characters in function names (`unset' doesn't
work to unset them without forcing -f, for instance). We're stuck with them
for backwards compatibility, but I don't have to encourage their use.
---
Why doesn't bash create some sort of "deprecate
I was looking @ coprocess section in the manpage where it says that:
NAME must not be supplied if command is a simple command.
For the coproc:
FH1(stdout) is put in NAME[0]
FH0(stdin) is put in NAME[1]
PID is put in NAME_PID
Questions (Seems like these should be in manpage, in this s
> Machine Type: i686-pc-linux-gnu
>
> Bash Version: 4.2
> Patch Level: 8
> Release Status: release
>
> Description:
> man bash is currently lacking information on what is allowed for
> function
> names. It implies name with name () compound-command [redirection] and
> at the st
On 4/11/11 1:10 AM, Allan McRae wrote:
> I am seeing what appears to be some sort of UTF-8 conversion issue in
> bash-4.2. I do not see this in bash 4.1. I think the easiest way to
> describe this is:
>
>
>> bash41 --version
> GNU bash, version 4.1.9(2)-release (i686-pc-linux-gnu)
>
>> LC_ALL
Hi Faheem,
Faheem Mitha wrote:
> $ cd --help
> bash: cd: --: invalid option
> cd: usage: cd [-L|-P] [dir]
>
> I'm don't even know how to get the usage output without
> inducing an error.
Does "help cd" do the trick?
> I think a man page might also be a good idea. You may
> als
