On Sat, 25 Jul 2009, Ken Irving wrote:
> On Fri, Jul 24, 2009 at 07:36:31PM -0700, michael rice wrote:
> > Is there a problem with naming a bash script file "script"? I'm using
> > Fedora 11.
> >
> > ...
> > [mich...@localhost ~]$ cat ./bin/script
> > #!/bin/bash
> > # Sample shell script
> > ec
You know how it shows us the choices when we hit TAB,
# rm /var/tmp/dan_home_bkp2009-07-26-02-
dan_home_bkp2009-07-26-02-18-36.bz2 dan_home_bkp2009-07-26-02-27-07.bz2
Well given that we are not going to bother to make the differing endings
bold, like in emacs, well, at least we can line them up v
Henning Garus wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: i686
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
> -DCONF_VENDOR='pc' -DLOCALEDI
On Fri, Jul 24, 2009 at 07:36:31PM -0700, michael rice wrote:
> Is there a problem with naming a bash script file "script"? I'm using Fedora
> 11.
>
> ...
> [mich...@localhost ~]$ cat ./bin/script
> #!/bin/bash
> # Sample shell script
> echo "The date today is `date`"
> echo Your shell is $SHELL
On Fri, 24 Jul 2009, michael rice wrote:
> Is there a problem with naming a bash script file "script"? I'm using Fedora
> 11.
Most systems already have a command called 'script'. It is not a
good idea to use the names of existing commands for your scripts.
--
Chris F.A. Johnson, webma
On Saturday 25 July 2009, michael rice wrote:
> Is there a problem with naming a bash script file "script"? I'm using
> Fedora 11.
"script" is most likely the name of a command installed on your system (on
mine, it's /usr/bin/script). Try "man script" and see.
So if you really want to call your s
Is there a problem with naming a bash script file "script"? I'm using Fedora 11.
Michael
[mich...@localhost ~]$ bash --version
GNU bash, version 4.0.23(1)-release (i386-redhat-linux-gnu)
[mich...@localhost ~]$ cat ./bin/temp
#!/bin/bash
# Sample shell script
echo "The date today is `date`"
ech
Can you reproduce this with bash-4.0 with all 24 patches applied? I
still have more testing to do, but I haven't been able to reproduce
it on my Mac OS X development machines.
Dunno what was wrong, but redownloading the patches solved the patching
issue.
Compiled with all the patches applied
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
On Saturday 25 July 2009, Linda Walsh wrote:
> AFAIK, I'm still screwed if I want to create more than one
> pipe for outputs -- either sending stderr to one pipe and stdout to
> another, OR a way of even doing what "tee" does, but built into the
> shell, so I could, using the building "tee", a f
10 matches
Mail list logo