161–170 of 198 posts
Earlier quoted context omitted.
This is so insane that I love it. Do you also save your belly button lint since 2005? Or nail clippings? :)
I'm only a digital packrat. Bits are so much cheaper to hoard, even deciding to throw something away is often more work.
Do you rebase your git repos regularly to delete commits older than 6 months?
It looks like it's not possible to export the history to a format the shell can import[0], so if I wanted to try this out, my commands would be locked there. It looks interesting, so if I'm overlooking a way to do this with fish, I'd experiment with it. [0]: https://github.com/ellie/atuin/issues/816
We’d like to be able to also export history, but atuin doesn’t actually stop your old shell history from functioning either So you could uninstall it, and you won’t have lost a thing
I have been using sqlite database since 2017 [1], has over 100,000 items in the database at this point. The database is almost 0.5GB, but I also use Full-Text-Search capabilities of sqlite. 2 years ago I have built a mac application [2], that syncs items via iCloud, and it only works on the macOS. I would highly recommend anyone who spend a lot of time in terminal to improve their shell history by using atuin or simi…
Wow so it looks like I'm in the minority in having shell command history disabled? I have a small number of commands (20) that go into the live history of login shells for convenience, but nothing gets saved when I log out. If there's something I do repeatedly, I make an alias or a function for it.
Earlier quoted context omitted.
Wow so it looks like I'm in the minority in having shell command history disabled? I have a small number of commands (20) that go into the live history of login shells for convenience, but nothing gets saved when I log out. If there's something I do repeatedly, I make an alias or a function for it.
I think you have an unusual take on this. Why do you disable history?
How does this compare to McFly? https://github.com/cantino/mcfly
I see two major differences: - how active the development is[1] - having a distributed option (McFly does not have one) 1. Seeking co-maintainers: I don't have much time to maintain this project these days. If someone would like to jump in and become a co-maintainer, it would be appreciated!
Is there a way to say, “I don’t care about which terminal a command is written to, just log them all chronologically in the same file”?
Would this SQLite approach work that way?
I have been using sqlite database since 2017 [1], has over 100,000 items in the database at this point. The database is almost 0.5GB, but I also use Full-Text-Search capabilities of sqlite. 2 years ago I have built a mac application [2], that syncs items via iCloud, and it only works on the macOS. I would highly recommend anyone who spend a lot of time in terminal to improve their shell history by using atuin or simi…
At 0.5GB that's 5k per entry -- what are you storing for each? For comparison, my (non-work) history since 2012 (plain text) is 181k entries, and takes 25MB. I store the command along with when and where you ran it. ( https://www.jefftk.com/p/logging-shell-history-in-zsh )