Hello,
I have the following lines on my login script, intended to make my history big
enough for me, and not to waste space by keeping several copies of the same
command again anda again:
HISTCONTROL='ignoreboth:erasedups'
HISTSIZE=4096
HISTFILESIZE=4096
To make sure it is working as that, I do
On Fri, Jun 13, 2008 at 06:52:48PM -0400, Chet Ramey wrote:
[...]
>> Also, it may be good to specify that, if the timeout is
>> reached, bash will consume the input but will not put
>> that consumed input into the variable:
>
> Actually, the bash-4.0 implementation will put the input
Chet Ramey wrote:
>> -
>> $ function name (echo)
>> bash: syntax error near unexpected token `echo'
>> -
> It's not. It's a shift/reduce conflict in the grammar. The default
> yacc/bison behavior is to choose the `function word () command'
Stephane Chazelas wrote:
However, I find that it does have an effect on Unix or
TCP sockets, on /dev/random and other terminals than
"the" terminal.
So maybe a better wording could be: "This option has no
effect on regular files"?
Thanks, I'll put in s
Jan Schampera wrote:
When you use the third form shown above and use the subshell-grouping
compound command '(...)' as function body, then it doesn't pass the parser:
-
$ function name (echo)
bash: syntax error near unexpected token `echo'
---
Eric Blake wrote:
I'm not sure whether this is a bug in POSIX or in bash, but I noticed the
following with bash-3.2.39.
$ bash -c 'foo=$(cat <
I agree with your analysis. The reworked command-substitution parsing in
bash-4.0 makes this a syntax error.
Finally, bash has a definite bug, wit
Roman Rakus wrote:
I have found one message for this:
http://lists.gnu.org/archive/html/bug-bash/2008-05/msg00074.html
And I have added some others patches. Oh, 1 patch for this 3 things :)
Please say if this patch will be applied.
Thanks for the updates.
Chet
--
``The lyf so short, the craft
Stephane Chazelas wrote:
On Tue, Jun 10, 2008 at 11:19:47AM -0400, Chet Ramey wrote:
[...]
So it is indeed a bug.
Yes, it is. I fixed it the last time this came up, in January.
[...]
Thanks,
It still seems to be there in 3.2.39 which seems to be the
latest version or ftp.gnu.org.
Yes, it
