4:38 p.m.
I read about a shell variable called HISTIGNORE that is supposed to prevent duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE="&"
It's not working. I still have duplicate commands galore. Why isn't is working?
4:51 p.m.
On Sat, Apr 28, 2012 at 4:38 PM, Peter Gueckel <pgueckel(a)gmail.com> wrote:
I read about a shell variable called HISTIGNORE that is supposed to
prevent duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE="&"
It's not working. I still have duplicate commands galore. Why isn't is working?
That prevents consecutive duplicates only I think.
John
4:54 p.m.
On 28 April 2012 22:38, Peter Gueckel <pgueckel(a)gmail.com> wrote:
I read about a shell variable called HISTIGNORE that is supposed to
prevent duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE="&"
It's not working. I still have duplicate commands galore. Why isn't is
working?
HISTIGNORE only deals with consecutive duplicates, IIRC.
What you want is:
export HISTCONTROL=erasedups
you might also want to add ":ignorespace" to the end of that. That will
cause any command prefixed by a space to be ignored as well - very useful
for those long commands that you will only ever run once!
Regards,
--
Andy
*The only person to have all his work done by Friday was Robinson Crusoe*
5:15 p.m.
Andy Blanchard wrote:
HISTIGNORE only deals with consecutive duplicates, IIRC.
What you want is:
export HISTCONTROL=erasedups
you might also want to add ":ignorespace" to the end of that. That will
cause any command prefixed by a space to be ignored as well - very useful
for those long commands that you will only ever run once!
Thanks. I will change it.
6:32 p.m.
On 04/29/2012 06:15 AM, Peter Gueckel wrote:
Andy Blanchard wrote:
> HISTIGNORE only deals with consecutive duplicates, IIRC.
>
> What you want is:
>
> export HISTCONTROL=erasedups
>
> you might also want to add ":ignorespace" to the end of that. That will
> cause any command prefixed by a space to be ignored as well - very useful
> for those long commands that you will only ever run once!
Thanks. I will change it.
http://www.thegeekstuff.com/2008/08/15-examples-to-master-linux-command-l...
Seems to have some nice examples of the various environment variables.
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
6:44 p.m.
Andy Blanchard wrote:
What you want is:
export HISTCONTROL=erasedups
It looked promising, but it doesn't work. I logged out and back in twice, then even
completely turned off the computer and back on again, but when I examine the
.bash_history file, it is riddled with duplicate commands.
7:01 p.m.
On 04/29/2012 07:44 AM, Peter Gueckel wrote:
Andy Blanchard wrote:
> What you want is:
>
> export HISTCONTROL=erasedups
It looked promising, but it doesn't work. I logged out and back in twice, then even
completely turned off the computer and back on again, but when I examine the
.bash_history file, it is riddled with duplicate commands.
I didn't do that much testing.....being summoned for breakfast. But, it seemed to
work fine for me.
I did 5 cat /etc/hosts followed by 5 ls /tmp and then repeated the cycled. Logged
out and Logged in and did a cat .bash_history.
The last few lines were....
vi .bash_profile
ls /etc
history
ls
cat .bash_history
cat /etc/hosts
ls /tmp
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
7:08 p.m.
On 29 April 2012 00:44, Peter Gueckel <pgueckel(a)gmail.com> wrote:
It looked promising, but it doesn't work. I logged out and back
in twice,
then even
completely turned off the computer and back on again, but when I examine
the
.bash_history file, it is riddled with duplicate commands.
It works, but not retrospectively. If you try running one of the
duplicated commands, it will strip out all of the duplicate entries then.
You'll also need to run "history -w" to update the history file, otherwise
it won't get updated until you exit the shell.
--
Andy
*The only person to have all his work done by Friday was Robinson Crusoe*
7:15 p.m.
On 04/28/2012 09:38 PM, Peter Gueckel wrote:
I read about a shell variable called HISTIGNORE that is supposed to
prevent
duplicate> commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE="&"
It's not working.
-=-
what made you think it would?, ie, from where do you find above variable
and it's use?
I still have duplicate commands galore.
-=-
not surprised.
Why isn't is working?
-=-
wrong command.
try;
HISTCONTROL="ignoredupes"
export HISTCONTROL
wfm ;)
--
peace out.
tc.hago,
g
.
*please reply "plain text" only. "html text" are deleted*
****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
The installation instructions stated to install Windows 2000 or better.
So I installed Linux.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****
7:29 p.m.
On 04/28/2012 04:44 PM, Peter Gueckel wrote:
Andy Blanchard wrote:
> What you want is:
>
> export HISTCONTROL=erasedups
It looked promising, but it doesn't work. I logged out and back in twice, then even
completely turned off the computer and back on again, but when I examine the
.bash_history file, it is riddled with duplicate commands.
http://linux.101hacks.com/command-line-history/histcontrol-erasedups/
http://linux.101hacks.com/command-line-history/histcontrol-ignoredups/
7:43 p.m.
On 04/28/2012 04:44 PM, Peter Gueckel wrote:
It looked promising, but it doesn't work. I logged out and back
in twice, then even
completely turned off the computer and back on again, but when I examine the
.bash_history file, it is riddled with duplicate commands.
It might only prevent new dups, not eliminate any already in .bash_history.
8:14 p.m.
Ed Greshko wrote:
On 04/29/2012 07:44 AM, Peter Gueckel wrote:
> Andy Blanchard wrote:
>
>> What you want is:
>>
>> export HISTCONTROL=erasedups
> It looked promising, but it doesn't work. I logged out and back in twice,
> then even completely turned off the computer and back on again, but when
> I examine the .bash_history file, it is riddled with duplicate commands.
>
I didn't do that much testing.....being summoned for breakfast. But, it
seemed to work fine for me.
I did 5 cat /etc/hosts followed by 5 ls /tmp and then repeated the cycled.
Logged out and Logged in and did a cat .bash_history.
The last few lines were....
vi .bash_profile
ls /etc
history
ls
cat .bash_history
cat /etc/hosts
ls /tmp
I'm thinking you have to start with an empty file. As was said in a former
post, it
doesn't work retroactively.
8:17 p.m.
On 04/29/2012 09:14 AM, Peter Gueckel wrote:
I'm thinking you have to start with an empty file. As was said in
a former post, it
doesn't work retroactively.
I wouldn't have expected it to work retroactively. Everyone knows "You can't
rewrite
history". :-) :-)
--
Never be afraid to laugh at yourself, after all, you could be missing out on the joke
of the century. -- Dame Edna Everage
8:21 p.m.
Andy Blanchard wrote:
It works, but not retrospectively. If you try running one of the
duplicated commands, it will strip out all of the duplicate entries then.
You'll also need to run "history -w" to update the history file, otherwise
it won't get updated until you exit the shell.
Thanks. It's not critical :-) I could just flush the contents of the history file, or
wait for duplicates to be stripped out over time. I was just fooling around. I do have
it set up with the correct variable, now, like you showed: HISTCONTROL=erasedups.
8:43 p.m.
Ed Greshko wrote:
On 04/29/2012 09:14 AM, Peter Gueckel wrote:
> I'm thinking you have to start with an empty file. As was said in a
> former post, it doesn't work retroactively.
I wouldn't have expected it to work retroactively. Everyone knows "You
can't rewrite
history". :-) :-)
It does in Linux:
history -c
history -w
;-)
8:52 p.m.
On 04/29/2012 12:15 AM, g wrote:
<>
HISTCONTROL="ignoredupes"
export HISTCONTROL
wfm ;)
after some post post thinking, i recalled that i did try "ignoreboth",
but with out results and dropped to "ignoredupes" only.
in addition, here is info from gnu .org:
from the gnu 'bash reference manual';
http://www.gnu.org/software/bash/manual/html_node/
you will find;
http://www.gnu.org/software/bash/manual/html_node/Bash-Variables.html
containing;
++++
HISTCONTROL
A colon-separated list of values controlling how commands are saved
on the history list. If the list of values includes ‘ignorespace’,
lines which begin with a space character are not saved in the history
list. A value of ‘ignoredups’ causes lines which match the previous
history entry to not be saved. A value of ‘ignoreboth’ is shorthand
for ‘ignorespace’ and ‘ignoredups’. A value of ‘erasedups’ causes
all previous lines matching the current line to be removed from the
history list before that line is saved. Any value not in the above
list is ignored. If HISTCONTROL is unset, or does not include a
valid value, all lines read by the shell parser are saved on the
history list, subject to the value of HISTIGNORE. The second and
subsequent lines of a multi-line compound command are not tested,
and are added to the history regardless of the value of HISTCONTROL.
++++
HISTIGNORE
A colon-separated list of patterns used to decide which command lines
should be saved on the history list. Each pattern is anchored at the
beginning of the line and must match the complete line (no implicit ‘*’
is appended). Each pattern is tested against the line after the checks
specified by HISTCONTROL are applied. In addition to the normal shell
pattern matching characters, ‘&’ matches the previous history line. ‘&’
may be escaped using a backslash; the backslash is removed before
attempting a match. The second and subsequent lines of a multi-line
compound command are not tested, and are added to the history regardless
of the value of HISTIGNORE.
HISTIGNORE subsumes the function of HISTCONTROL. A pattern of ‘&’ is
identical to ignoredups, and a pattern of ‘[ ]*’ is identical to
ignorespace. Combining these two patterns, separating them with a colon,
provides the functionality of ignoreboth.
++++
--
peace out.
tc.hago,
g
.
*please reply "plain text" only. "html text" are deleted*
****
in a free world without fences, who needs gates.
**
help microsoft stamp out piracy - give linux to a friend today.
**
to mess up a linux box, you need to work at it.
to mess up an ms windows box, you just need to *look* at it.
**
The installation instructions stated to install Windows 2000 or better.
So I installed Linux.
**
learn linux:
'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html
'The Linux Documentation Project' http://www.tldp.org/
'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html
'HowtoForge' http://howtoforge.com/
****
9:45 a.m.
On Sat, Apr 28, 2012 at 03:38:41PM -0600, Peter Gueckel wrote:
I read about a shell variable called HISTIGNORE that is supposed to
prevent duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE="&"
It's not working. I still have duplicate commands galore. Why isn't is working?
I have:
HISTIGNORE='ls:cp:mv:rmdir:mkdir:less:most:joe:cd' && export HISTIGNORE
in my .bashrc. Works afaict.
Terry
10:54 a.m.
Hi,
On Mon, Apr 30, 2012 at 16:45, <ny6p01(a)gmail.com> wrote:
I have:
HISTIGNORE='ls:cp:mv:rmdir:mkdir:less:most:joe:cd' && export HISTIGNORE
in my .bashrc. Works afaict.
I think someone else pointed this out earlier in the thread, HISTIGNORE
is the wrong variable for what the OP wants to achieve. The correct
option is HISTCONTROL.
Whereas HISTIGNORE uses pattern matching to not record commands in the
history list, HISTCONTROL controls which commands are saved in the
history list based on its value. In the OP's case the appropriate value
should be either of `ignoredups' or `erasedups'.
If someone is interested in the nitty gritties, look at `man bash`,
"Shell Variables".
Hope this is clear.
--
Suvayu
Open source is the future. It sets us free.
4372
days inactive
4374
days old
17 comments
9 participants
participants (9)
-
Andy Blanchard -
Ed Greshko -
Edward M -
g -
inode0 -
Joe Zeff -
Lee -
Peter G. -
Suvayu Ali