I'm curious to hear what people's usecases are for retaining long shell history. For myself, I never really use it beyond the current work day (up arrow)
for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.
I quit my job to work full time on my open source project
161–170 of 190 posts
Re: I quit my job to work full time on my open source project
#162I'm curious to hear what people's usecases are for retaining long shell history. For myself, I never really use it beyond the current work day (up arrow)
Re: I quit my job to work full time on my open source project
#163Earlier quoted context omitted.
for work, there are a lot of commands with complex invocations that I do not use regularly enough to bother remembering all the flags. it is really useful to just grep through my full shell history to find all the times I ran that command and just copy/paste the relevant one.
I end up manually curating skeleton command lines in a text file - partly because I've never had functional full badh history
Re: I quit my job to work full time on my open source project
#164Has anyone who uses fish shell compared that to Atuin? I suspect that having my entire shell history accessible might not really be necessary.
Fish has smoother usability, autocompletion and search. It is useful on fresh machine in vanilla configuration. Installing bash plugins is not always possible. Installing some sync plugin on sensitive server is nono! Also my biggest problem with bash, sometimes it does not keep part of recent history, if bash process gets killed. Fish does not have this problem. I usually keep useful commands in notes, and sync my no…
Re: I quit my job to work full time on my open source project
#165Re: I quit my job to work full time on my open source project
#166Has anyone who uses fish shell compared that to Atuin? I suspect that having my entire shell history accessible might not really be necessary.
With fish's own autocomplete I get most of what I need. Add fzf to search the history (ctrl-r), and it's highly comparable to the post topic.
Re: I quit my job to work full time on my open source project
#167I love the idea of Atuin but it's just way too slow with large history files. I've synced my history on my own for the past decade and have like 170k lines and the history search the ctrl-r search just crawls. I don't need most of the history, but there's 0 chance in hell I'm auditing that many lines to decide what I need and what I don't need.
> but it's just way too slow with large history files hey! what issues were you having here? slow to open or slow to search? we have a whole bunch of people with way more than 170k lines, so that shouldn't be happening :/
I Love the project (will donate now, I remember when the project wasn’t taking donations, and I suggested they should) Thanks
Edit: I should add: I have the client on about 15 to 20 different VM‘s, all with various OSes and versions. The server part I’m running w docker (I think, via the exact steps suggested in the docs). All Works great in my use case, and I do have some very long and complex commands that it’s storing
Re: I quit my job to work full time on my open source project
#168Re: I quit my job to work full time on my open source project
#169I keep my shell history in sqlite database since 2017. Around 120k records at this point. Never synced history from the work laptops. Only personal history. In 2017 wrote my own bash script (later optimized for zsh) to just record everything in sqlite with hooks on prompt. [1] I mostly work right now on Mac, don't need to support Linux anymore, so wrote an app for Mac, that syncs the history over iCloud, and has a GU…
Do you know any way to accomplish the same thing but keeping the history in plaintext? Would love to still be able to run SQL over it.