Four hours, no replies yet.
So I decided to post a comment on:
http://forums.gentoo.org/viewtopic-p-6162718.html
Thanx if someone with more profound GNU bash programming understanding
finds a fix or an explanation and a workaround for this...
(I wasn't able to send this with bashbug)
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -
DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gn
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/sha
On 2/6/10 6:38 AM, Jon Seymour wrote:
> Is it to allow users who may have reason to type sensitive commands a
> trivial means to suppress such commands from their command history?
Yes. Not just sensitive commands, but any command for any reason.
--
``The lyf so short, the craft so long to ler
On Feb 6, 5:37 pm, djackn wrote:
> May I used the following in a bash script to pass variables to myIpExec?
>
> Result = myIpExec(${IPaddr1} ${IPaddr2} ${IPaddr3} ${IPaddr4})
>
> myIpExec is a c program that normally uses scanf to prompt the user
> for the IP addresses and returns 0 or 1.
> I
May I used the following in a bash script to pass variables to myIpExec?
Result = myIpExec(${IPaddr1} ${IPaddr2} ${IPaddr3} ${IPaddr4})
myIpExec is a c program that normally uses scanf to prompt the user
for the IP addresses and returns 0 or 1.
I plan to use the script to test the program
I too was unaware of the HISTCONTROL option, but now that I know what
it does, I am intrigued by the rationale for HISTCONTROL=ignorespace?
In other words, what motivated the inclusion of handling for this
option specifically?
Is it to allow users who may have reason to type sensitive commands a
t
Mike,
Thanks, I was unaware of HISTCONTROL.
Paul
On 6 February 2010 09:06, Jan Schampera wrote:
> Mike Frysinger schrieb:
>
>>> When using the bash shell in an xterm or rxvt terminals at least,
>>> commands executed which start with a space, eg " ls" are not added to
>>> the command line hist
Mike Frysinger schrieb:
>> When using the bash shell in an xterm or rxvt terminals at least,
>> commands executed which start with a space, eg " ls" are not added to
>> the command line history and so are not accessible by ctrl-p.
>
> this is by design
> -mike
This is controlled by the HISTCONTR
