Re: bash history

This is how I keep a long-term record of bash commands from different sessions: https://www.reddit.com/r/bash/comments/ak9c3r/ HTH -- Karl Vogel I don't speak for anyone but myself Comment: I use a screwdriver a lot Reply: I'm all out of orange juice. Will straight vodka

Re: bash history

On Sun, Jul 28, 2024 at 5:16 AM songbird wrote: > not that i would want that, > > but it would be possible for various terminals to save to > their own unique history files based upon terminal pty or > tty or anything else you'd like and to reload those upon > starting up again. Yes. Setting

Re: bash history

On Sat, Jul 27, 2024 at 11:23 PM Jeffrey Walton wrote: > On Sun, Jul 28, 2024 at 12:25 AM Mike Castle wrote: > > * I keep history under source control (currently git) and regularly > > (well, for some definition of "regularly"), merge them across machines > > This is an unusual use case (to me).

Re: bash history

On Sat, Jul 27, 2024 at 11:04 PM mick.crane wrote: > If I've "su'd" I type "exit". > To close the terminal I click that X in the virtual terminal's top right > hand corner. Depending on settings, that may or may not save that invocation's history. You'll likely want to test to verify that it doe

Re: bash history

On 2024-07-28 at 09:29, Yassine Chaouche wrote: > Le 7/28/24 à 12:19, songbird a écrit : > >> to keep my own setup consistent and to not keep certain things in >> history i actually do the opposite of what you want because i want >> certain commands already preloaded in my history for all windows

Re: bash history

Le 7/28/24 à 12:19, songbird a écrit : [...] to keep my own setup consistent and to not keep certain things in history i actually do the opposite of what you want because i want certain commands already preloaded in my history for all windows when i start up and then i adjust my environment b

Re: bash history

mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? > Is this something that can be changed so history is shared between > virtual terminals? > mick not that i would want

Re: bash history

until bash exits properly. This ensures you never lose track of any command, even if your bash session ends unexpectedly. Additionally, history -n allows your shell to read the bash history again, updating it with any new entries. Imagine executing foo in terminal 1, pressing Enter, then switching to

Re: bash history

On 2024-07-27 23:58, Greg Wooledge wrote: You need to specify *exactly* what you're doing. "exactly" is at mickiwiki.com I can take the ridicule of my coding understanding. Whenever I need to reboot my computer (kernel update or the like), I decide which shells I want to retain history from,

Re: bash history

On Sun, Jul 28, 2024 at 12:25 AM Mike Castle wrote: > > On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote: > > Is this something that can be changed so history is shared between > > virtual terminals? > > [...] > For me, I see up bash with the following features: > * Unbounded history > * History

Re: bash history

On 2024-07-28 02:12, Greg Wooledge wrote: On Sun, Jul 28, 2024 at 02:01:04 +0100, mick.crane wrote: On 2024-07-27 23:58, Greg Wooledge wrote: > You need to specify *exactly* what you're doing. Sometimes I forget where I was after closing a virtual terminal and it would be handy to see the h

Re: bash history

On Sat, Jul 27, 2024 at 2:50 PM mick.crane wrote: > Is this something that can be changed so history is shared between > virtual terminals? Yes. There are all sorts of settings that can control how shells save history. Most shells are capable of doing whatever you want, but the default configur

Re: bash history

On 28/07/2024 08:01, mick.crane wrote: Sometimes I forget where I was after closing a virtual terminal  and it would be handy to see the history in a new terminal, where I "cd'd" to for example. help history less ~/.bash_history

Re: bash history

On Sun, Jul 28, 2024 at 02:01:04 +0100, mick.crane wrote: > On 2024-07-27 23:58, Greg Wooledge wrote: > > You need to specify *exactly* what you're doing. > Sometimes I forget where I was after closing a virtual terminal and it > would be handy to see the history > in a new terminal, where I "cd'

Re: bash history

On 2024-07-27 23:58, Greg Wooledge wrote: You need to specify *exactly* what you're doing. My project management skills are non-existent. If I have a script that is working I'll copy to eg. script2 and make changes to that. Sometimes, depending, I'll have similar things in other directories t

Re: bash history

On 2024-07-27 22:50:17 +0100, mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? > Is this something that can be changed so history is shared between virtual > terminals? This

Re: bash history

er presses "up key" in >>> different virtual terminals ? >> >> As your subject says, this is "bash history". And yes, each >> instance of bash has its own separate history. It has nothing to >> do with your terminal emulator or your deskto

Re: bash history

me user presses "up key" in different virtual > > > terminals ? > > > > As your subject says, this is "bash history". And yes, each instance of > > bash has its own separate history. It has nothing to do with your > > terminal emulator or your d

Re: bash history

On 2024-07-27 23:08, Greg Wooledge wrote: On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: In debian bookworm, xfce desktop, different virtual terminals have a different history if same user presses "up key" in different virtual terminals ? As your subject says, this is &qu

Re: bash history

Hi, On Sat, Jul 27, 2024 at 10:50:17PM +0100, mick.crane wrote: > Is this something that can be changed so history is shared between virtual > terminals? You may be interested in "atuin" to aggregate shell history from multiple logins and machines in a searchable interface. It can be self-hosted.

Re: bash history

On Sat, Jul 27, 2024 at 22:50:17 +0100, mick.crane wrote: > In debian bookworm, xfce desktop, different virtual terminals have a > different history if same user presses "up key" in different virtual > terminals ? As your subject says, this is "bash history". And y

bash history

In debian bookworm, xfce desktop, different virtual terminals have a different history if same user presses "up key" in different virtual terminals ? Is this something that can be changed so history is shared between virtual terminals? mick

Re: Increasing the number of bash history

oa wrote: >> > Hi, >> > I want to increase the number of bash history. >> > >> > $ history >> > ==omitting== >> > 1996 history >> > >> > After entering commands more than ten times, >> > I relaunched the terminal to se

Re: Increasing the number of bash history

PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, Feb 24, 2016 at 08:16:01PM +0800, EenyMeenyMinyMoa wrote: > > Hi, > > I want to increase the number of bash history. > > > > $ history > > ==omitting== > > 1996 history > > > > After entering co

Re: Increasing the number of bash history

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Feb 24, 2016 at 08:16:01PM +0800, EenyMeenyMinyMoa wrote: > Hi, > I want to increase the number of bash history. > > $ history > ==omitting== > 1996 history > > After entering commands more than ten times, > I rel

Increasing the number of bash history

Hi, I want to increase the number of bash history. $ history ==omitting== 1996 history After entering commands more than ten times, I relaunched the terminal to see $ history ==omitting== 1996 history I've added the following lines to /home/eeny/.bashrc about a year ago. HISTSIZE=

Re: Re: funny text in bash history

On Sun, Sep 28, 2014 at 06:04:18PM +0100, Clive Standbridge wrote: > That's just for starters. Install the bash-completion package, > un-comment the code in ~/.bashrc following the "enable programmable > completion features" comment, and start a new shell. > > Now when you start typing and press

Re: funny text in bash history

2014/09/28 20:40 "The Wanderer" : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 09/28/2014 at 07:17 AM, Cindy-Sue Causey wrote: > > > On 9/27/14, Joel Rees wrote: > > > >> Booted this morning, started my usual pattern of bringing the > >> appropriate apt-get commands up from history

Re: funny text in bash history

2014/09/28 20:17 "Cindy-Sue Causey" : > > On 9/27/14, Joel Rees wrote: > > Booted this morning, started my usual pattern of bringing the appropriate > > apt-get commands up from history. (I'm lazy, okay?) > > > > Had a bunch of unicode proxies and a reference to a backup directory that > > I have

Re: Re: funny text in bash history

> I do A LOT of computing from terminals... and use arrow up and down > ALL THE TIME.. Autocomplete would so ROCK! "Tab completion" is the key phrase. Assuming you use bash: When you want to complete a command or filename, press the Tab key. If the choices are ambiguous, you'll need to press Tab

Re: funny text in bash history

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 09/28/2014 at 07:17 AM, Cindy-Sue Causey wrote: > On 9/27/14, Joel Rees wrote: > >> Booted this morning, started my usual pattern of bringing the >> appropriate apt-get commands up from history. (I'm lazy, okay?) >> >> Had a bunch of unicode

Re: funny text in bash history

On 9/27/14, Joel Rees wrote: > Booted this morning, started my usual pattern of bringing the appropriate > apt-get commands up from history. (I'm lazy, okay?) > > Had a bunch of unicode proxies and a reference to a backup directory that > I haven't accessed in several months in my most recent thr

funny text in bash history

Booted this morning, started my usual pattern of bringing the appropriate apt-get commands up from history. (I'm lazy, okay?) Had a bunch of unicode proxies and a reference to a backup directory that I haven't accessed in several months in my most recent three lines, then the history that should

Re: Bash history not propagating.

On Sun, 29 Sep 2013 15:23:25 + (UTC) Curt wrote: > On 2013-09-29, Sharon Kimble 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, i

Re: Bash history not propagating.

On 2013-09-29, Sharon Kimble 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

Bash history not propagating.

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 that they both mirror each other please? I find it very ea

Re: bash history

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

Re: bash history

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.

Re: bash history

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 wro

Re: bash history

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

Re: bash history

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 patc

Re: bash history

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" >

Re: bash history

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

Re: bash history

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

bash history

Hola! This is debian squeeze amd64. I am reading the laudauble site http://www.markus-gattol.name/ws/bash.html about using bash history. 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:~$ histo

Re: bash history

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

Re: bash history

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

Re: bash history

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 hopin

Re: bash history

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: 100% accessible validated (X)HTML - Blog:

Re: bash history

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

Re: bash history

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

Re: bash history

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

Re: bash history

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 appen

Re: bash history

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 h

Re: bash history

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

Re: bash history

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 l

Re: bash history

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. > >

Re: bash history

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

bash history

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 normal? Or is there

Re: bash history search key binding

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 .. mayb

Re: Re: bash history search key binding

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

Re: bash history search key binding

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

bash history search key binding

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' It worked well before, one day, after I did a routine upgrade, it stop

bash history search key binding

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' It worked well before, one day, after I did a routine upgrade, it st

Re: bash history too short ?

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]

bash history too short ?

Hello, I have a difference in the size of my .bash_history and the $HISTSIZE variable: [EMAIL PROTECTED] >wc -l /home/gru/.bash_history 2217 /home/gru/.bash_history [EMAIL PROTECTED] >echo $HISTSIZE 4000 I could only explain this if I wouldn't type "new" commands, but many commands that I use

[SOLVED] Re: forcibly unmounting and bash history

First of all, why didn't post it to the list? Do you think it's too OT? But, on the other hand, both your mails were no help and also misleading. I'd like to elaborate on that. On Sun, Jul 06, 2003 at 06:51:29AM -0400, Robert August Vincent II wrote: > "history" is a bash built-in. > > Bash runs

forcibly unmounting and bash history

Hello, it's happened many time to me that I couldn't find a way to forcibly unmount a CD if the fact that it was broken caused my screen to be filled with some "drive-seek" errors or something. Further more, it seemed impossible if, say, mplayer hung because of that. Getting rid of the messages is

Re: bash history file

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?

Re: bash history file

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. > >

bash history file

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 any tips. Ian -- Ian Balchin http://www.imaginet.co.za/fables This machine is running

Bash history problem/question

Hello, System: "Debian 2.2.18pre21" - "486dx" Bash version: "2.03-6" Background: Recently I have written a shell-script that is supposed to append every minute new history lines to a alternate file where they are being processed further. Problem: The command `history -a file` can't be execu