Hi.
To re-do previous command sequences from the history Bash provides
operate-and-get-next (bound to C-o). So to re-do a sequence A B C of commands
I need to navigate to A in the history and then enter
A C-o (=> B) C-o (=> C) RET
However, that requires the decision to re-do a sequence (and
Hi,
I have the following problem:
(Environment or regular) variable FOO contains the path of existing directory
"/foo". When I have a file "/foo/bar" in that directory and when I press TAB
in the following commandline ('|' denoting the cursor position)
$ cat $FOO/b|
bash expands the comman
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc'
-DLOCALEDIR='/sapmnt/oraicall/home/tools/bash
> -u Treat unset variables as an error when substituting.
>
> I think the behaviour is consistent with the documentation.
The question is rather when to consider a variable set or unset.
For me, an empty string (or empty commadline) is as set or as
unset as an empty array. But I don't get an "
Configuration Information [Automatically generated, do not change]:
Machine: sparc
OS: solaris2.9
Compiler: /sapmnt/global/tools/compiler/SS11/SUNWspro/bin/cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='sparc'
-DCONF_OSTYPE='solaris2.9' -DCONF_MACHTYPE='sparc-sun-solaris2.9'
-DCONF_VEN
Hi, bash folks,
for a larger shell-based project I wanted to have definit answers to questions
like
- are all redirections to log handle 3 done when the log handle is actually
open?
- are all calls to grep handled properly (either return value or output
ignored)?
- are all calls to exit valid?
