On 2013-09-29, Sharon Kimble boudic...@talktalk.net wrote:
I'm having a problem with bash history. Basically, I do a lot of stuff
in tmux windows, and then when I open up another terminal window, but
not in tmux, it does not have the same history as in the tmux windows.
How can I get it so
On Sun, 29 Sep 2013 15:23:25 + (UTC)
Curt cu...@free.fr wrote:
On 2013-09-29, Sharon Kimble boudic...@talktalk.net wrote:
I'm having a problem with bash history. Basically, I do a lot of
stuff in tmux windows, and then when I open up another terminal
window, but not in tmux, it does
On Sun, 14 Nov 2010 19:44:38 -0300, Kjetil brinchmann Halvorsen wrote:
Hola!
Hola :-)
So I'm trying to use Ctrl-R to do reverse search in the history. Thia is
what happens; I try to search for white:
kje...@kjetil:~$ history | tail
(...)
(reverse-i-search)`wh': aptitude why patch
On Sun, 14 Nov 2010 19:51:18 -0700, Bob wrote in message
20101115025118.ga1...@hysteria.proulx.com:
Arnt Karlsen wrote:
Bob wrote in message:
Kjetil brinchmann Halvorsen wrote:
(reverse-i-search)`wh': aptitude why patch
--- After typing wh (without the quotes), it does not accept
On Mon, 15 Nov 2010 18:11:30 +0100, Arnt wrote in message
20101115181130.42248...@a45.fmb.no:
On Sun, 14 Nov 2010 19:51:18 -0700, Bob wrote in message
20101115025118.ga1...@hysteria.proulx.com:
Arnt Karlsen wrote:
Bob wrote in message:
Kjetil brinchmann Halvorsen wrote:
Arnt Karlsen wrote:
Bob wrote in message
Arnt Karlsen wrote:
..from grep --help |less: ;o)
-i, --ignore-case ignore case distinctions
That is a grep option. It doesn't apply to bash's history search.
..correct, that's _why_ we use such grep pipes instead. ;o)
Uhm...
On Mon, 15 Nov 2010 11:33:57 -0700, Bob wrote in message
20101115183357.ga18...@hysteria.proulx.com:
Arnt Karlsen wrote:
Bob wrote in message
Arnt Karlsen wrote:
..from grep --help |less: ;o)
-i, --ignore-case ignore case distinctions
That is a grep option. It
Kjetil brinchmann Halvorsen wrote:
So I'm trying to use Ctrl-R to do reverse search in the history.
Thia is what happens; I try to search for white:
Here you say white in lower case letters.
kje...@kjetil:~$ history | tail
284 Sunday 2010-11-14 [19:37:03 -0300] history 10
285 Sunday
On Sun, 14 Nov 2010 16:00:50 -0700, Bob wrote in message
20101114230050.ga7...@hysteria.proulx.com:
Kjetil brinchmann Halvorsen wrote:
So I'm trying to use Ctrl-R to do reverse search in the history.
Thia is what happens; I try to search for white:
Here you say white in lower case
Arnt Karlsen wrote:
Bob wrote in message:
Kjetil brinchmann Halvorsen wrote:
(reverse-i-search)`wh': aptitude why patch
--- After typing wh (without the quotes), it does not accept more
letters!
What you are missing is that the search is case sensitive. The Wh
in White is *not*
2008/6/30 ciracusa [EMAIL PROTECTED]:
Buenas Lista.
Donde se especifica cada cuanto tiempo se limpia el bash_history de un
usuario?
En la variable de entorno $HISTSIZE, por defecto son 500 comandos que registra.
Una vez borrado queda almacenado en algun historico?
Hasta donde se no.
--
On Thu, 2008-01-17 at 06:16 +0530, Raj Kiran Grandhi wrote:
Vincent Lefevre wrote:
On 2008-01-17 05:37:34 +0530, Raj Kiran Grandhi wrote:
set -o histappend
appends the history file instead of overwriting it.
$ set -o histappend
bash: set: histappend: invalid option name
Sorry
On 2008-01-17 15:18:23 +, Magnus Therning wrote:
On 1/17/08, Vincent Lefevre [EMAIL PROTECTED] wrote:
man zshoptions
Look at all the options in the History section...
Of course that was /exactly/ what I was hoping to /not/ have to do :-)
Luckily there aren't more than 18 options
On 2008-01-17 06:16:51 +0530, Raj Kiran Grandhi wrote:
Vincent Lefevre wrote:
But even if it can append commands, would bash do that *immediately*?
It seems that bash can save the history only when it exits.
By immediately, do you mean writing to the history file after every
command?
Yes
Vincent Lefevre wrote:
On 2008-01-16 18:38:08 -0500, Vikki Roemer wrote:
On Jan 16, 2008 6:25 PM, Adam Hardy [EMAIL PROTECTED] wrote:
I use alot of console windows in X as well as having shells and
ssh shells open sometimes for the same user. I notice that bash
doesn't save every command
On 1/17/08, Vincent Lefevre [EMAIL PROTECTED] wrote:
On 2008-01-17 09:54:42 +, Magnus Therning wrote:
I'm a ZSH user, so do you have any pointers on how to do that?
man zshoptions
Look at all the options in the History section...
Of course that was /exactly/ what I was hoping to
On 2008-01-17 09:54:42 +, Magnus Therning wrote:
I'm a ZSH user, so do you have any pointers on how to do that?
man zshoptions
Look at all the options in the History section...
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog:
On Jan 16, 2008 6:25 PM, Adam Hardy [EMAIL PROTECTED] wrote:
I use alot of console windows in X as well as having shells and ssh shells
open
sometimes for the same user. I notice that bash doesn't save every command
immediately and loses the history from simultaneous bash sessions, when they
Quoth Adam Hardy:
I use alot of console windows in X as well as having shells and ssh
shells open sometimes for the same user. I notice that bash doesn't save
every command immediately and loses the history from simultaneous bash
sessions, when they are not the last session to close.
Is
On 2008-01-16 18:38:08 -0500, Vikki Roemer wrote:
On Jan 16, 2008 6:25 PM, Adam Hardy [EMAIL PROTECTED] wrote:
I use alot of console windows in X as well as having shells and
ssh shells open sometimes for the same user. I notice that bash
doesn't save every command immediately and loses the
Adam Hardy wrote:
I use alot of console windows in X as well as having shells and ssh
shells open sometimes for the same user. I notice that bash doesn't save
every command immediately and loses the history from simultaneous bash
sessions, when they are not the last session to close.
Is that
On 2008-01-17 05:37:34 +0530, Raj Kiran Grandhi wrote:
set -o histappend
appends the history file instead of overwriting it.
$ set -o histappend
bash: set: histappend: invalid option name
But even if it can append commands, would bash do that *immediately*?
It seems that bash can save the
Vincent Lefevre wrote:
On 2008-01-17 05:37:34 +0530, Raj Kiran Grandhi wrote:
set -o histappend
appends the history file instead of overwriting it.
$ set -o histappend
bash: set: histappend: invalid option name
Sorry about that. It should be shopt -s histappend
But even if it can append
On Jan 16, 2008 3:25 PM, Adam Hardy [EMAIL PROTECTED] wrote:
I use alot of console windows in X as well as having shells and ssh shells
open
sometimes for the same user. I notice that bash doesn't save every command
immediately and loses the history from simultaneous bash sessions, when they
Lei Kong wrote:
[...]
Thanks for your advice, but misteriously, it is back to normal now.
I swear to god I didn't do anything, oh, wait, maybe I did an
aptitude upgrade
without even knowing about it.
maybe your bash history was accidentally reset.. or lost its cd*
commands .. maybe the
Lei Kong wrote:
Hi all,
I am using debian testing, and the bash version is 3.1.5.
I have the following lines in my .bashrc to assign arrow keys to history
search:
bind '\M-[A:history-search-backward'
bind '\M-[B:history-search-forward'
what does
$ bind -P | grep history
say?
It
Hi all,
I am using debian testing, and the bash version is 3.1.5.
I have the following lines in my .bashrc to assign arrow keys to
history search:
bind '\M-[A:history-search-backward'
bind '\M-[B:history-search-forward'
what does
$ bind -P | grep history
say?
It
Perhaps different bashes overwrite each other's history? There is a
setting for appending to the history, rather than overwriting it.
Perhaps that helps?
Kai
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
* Frank Dietrich [EMAIL PROTECTED] [21-08-2005 15:31]:
::~$ cd /tmp/
::/tmp$ mkdir LS
::/tmp$ cd LS
::/tmp/LS$ cp /bin/ls .
::/tmp/LS$ PATH=/tmp/LS:$PATH
::/tmp/LS$ ls
ls
::/tmp/LS$ rm ls
::/tmp/LS$ ls
bash: /tmp/LS/ls: Datei oder Verzeichnis nicht gefunden
Mir fehlt
Uwe Kerstan schrieb:
* Frank Dietrich [EMAIL PROTECTED] [21-08-2005 15:31]:
::~$ cd /tmp/
::/tmp$ mkdir LS
::/tmp$ cd LS
::/tmp/LS$ cp /bin/ls .
::/tmp/LS$ PATH=/tmp/LS:$PATH
::/tmp/LS$ ls
ls
::/tmp/LS$ rm ls
::/tmp/LS$ ls
bash: /tmp/LS/ls: Datei oder
* Jan Kohnert [EMAIL PROTECTED] [21-08-2005 16:02]:
Mit history -c vergisst sie alle zuvor gespeicherten Eingaben.
Den Befehl kenne ich, er bewirkt aber an dieser Stelle *nur* das Löschen
der history. Man muss aber den Cache löschen, damit /bin/ls wieder
gefunden wird. Ich werde mal in
Hi Uwe,
Uwe Kerstan [EMAIL PROTECTED] wrote:
* Frank Dietrich [EMAIL PROTECTED] [21-08-2005 15:31]:
Mir fehlt leider gerade der richtige Befehl, um diesen
Cache wieder zu löschen - muss mal wieder man bash lesen. ;-)
Mit history -c vergisst sie alle zuvor gespeicherten Eingaben.
Dirk Haage wrote:
On Sat, 11 Jan 2003 18:11:04 +0100 Wolfgang Bär wrote:
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei und log
^^
Das ist doch etwas hart, geht auch ohne, beim naechsten einloggen
funktionieren dann auch noch
Wolfgang Bär schrieb am Sonntag, 12. Januar 2003 um 12:57:08 +0100:
Dirk Haage wrote:
On Sat, 11 Jan 2003 18:11:04 +0100 Wolfgang Bär wrote:
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei und log
^^
Das ist doch etwas
Moin,
* Joerg Friedrich [EMAIL PROTECTED] [2003-01-12 15:52]:
Wolfgang Bär schrieb am Sonntag, 12. Januar 2003 um 12:57:08 +0100:
Tja, geb ich Dir ja recht - aber wie man die bestehenden Duplikate
rausbekommt wußte ich halt nicht, also die Idee einfach eine neue
History aufzubauen - jetzt weiß
On Son, 12 Jan 2003 at 12:57 (+0100), Wolfgang Bär wrote:
Dirk Haage wrote:
On Sat, 11 Jan 2003 18:11:04 +0100 Wolfgang Bär wrote:
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei und log
^^
Das ist doch etwas
Hi Thorsten,
On Sun, Jan 12, 2003 at 04:17:06PM +0100, Thorsten Haude wrote:
Moin,
mv .bash_history hist_alt; uniq hist_alt .bash_history; rm hist_alt
Das findet doch nur doppelte, die unmittelbar aufeinander folgen,
oder?
Ja, deshalb noch ein sort for dem uniq. Dann ist zwar die
On Sun, 12 Jan 2003 15:42:22 +0100 Jan Trippler wrote:
On Son, 12 Jan 2003 at 12:57 (+0100), Wolfgang Bär wrote:
Dirk Haage wrote:
On Sat, 11 Jan 2003 18:11:04 +0100 Wolfgang Bär wrote:
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei und
On Son, 12 Jan 2003 at 15:52 (+0100), Joerg Friedrich wrote:
[Doubletten aus .bash_history fischen]
mv .bash_history hist_alt; uniq hist_alt .bash_history; rm hist_alt
jan@k233:~/tmp$ cat unsorted
abc
xyz
abc
abc
xyz
jan@k233:~/tmp$ uniq unsorted
abc
xyz
abc
xyz
uniq funktioniert nur bei
On Son, 12 Jan 2003 at 17:04 (+0100), Dirk Haage wrote:
On Sun, 12 Jan 2003 15:42:22 +0100 Jan Trippler wrote:
[...]
Um Doubletten rauszufischen, ohne die History gleich sortieren zu
müssen, kann ein kleines Perl-Script nützlich sein:
IIRC war die History beim naechsten einloggen
On Sun, 12 Jan 2003 19:08:02 +0100 Jan Trippler wrote:
On Son, 12 Jan 2003 at 17:04 (+0100), Dirk Haage wrote:
On Sun, 12 Jan 2003 15:42:22 +0100 Jan Trippler wrote:
[...]
Um Doubletten rauszufischen, ohne die History gleich sortieren zu
müssen, kann ein kleines Perl-Script nützlich
Hallo Thomas,
Thomas Schönhoff wrote:
ich überlege gerade, wie ich Doppeleinträge in der Bash History per
Skript löschen könnte!?
Warum denn so umständlich?
man bash
Stichwort HISTCONTROL
das in die gewünschte .bashrc eintragen
und fretig ists.
mit Gruss
Frank
--
Häufig
Hallo Thomas,
Thomas Schönhoff wrote:
Hallo,
ich überlege gerade, wie ich Doppeleinträge in der Bash History per
Skript löschen könnte!?
Ne, keine Ahnung - aber wie Du Doppeleinträge verhindern kannst.
Füge
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei
Hallo Thomas,
Thomas Schönhoff wrote:
Hallo,
ich überlege gerade, wie ich Doppeleinträge in der Bash History per
Skript löschen könnte!?
Aus dem Linux Anwenderhandbuch:
~/.bash_logout wird beim Verlassen der Login-Shell ausgeführt. Diese
Datei kann beispielsweise folgende Zeilen
On Sat, 11 Jan 2003 18:11:04 +0100 Wolfgang Bär wrote:
HISTCONTROL=ignoredups
in Deine .bashrc ein, lösche Deine bestehende History-Datei und log
^^
Das ist doch etwas hart, geht auch ohne, beim naechsten einloggen funktionieren dann
auch noch die alten Kommandos
On Wed, Jan 30, 2002 at 08:07:10PM -0800, Karsten M. Self wrote:
on Wed, Jan 30, 2002 at 08:57 PM +0200, Ian Balchin ([EMAIL PROTECTED]) wrote:
Hi,
My commands are no longer recorded in .bash_history
HISTFILE. HISTFILESIZE, HISTSIZE are all set.
What have i done? This is
on Wed, Jan 30, 2002 at 08:57 PM +0200, Ian Balchin ([EMAIL PROTECTED]) wrote:
Hi,
My commands are no longer recorded in .bash_history
HISTFILE. HISTFILESIZE, HISTSIZE are all set.
What have i done? This is apparent in my user login, commands as
root are still recorded.
Thanks for
On Fri, 4 Jan 2002 00:05:43 -0200
Joel Franco Guzmán [EMAIL PROTECTED] wrote:
Olá pessoal,
Dúvidas sobre o funcionamento do history no bash.
Achei que a var de controle do histórico de comandos do bash é
HISTSIZE e o tamanho do arquivo de histórico controlado por HISTFILESIZE.
48 matches
Mail list logo
