Conversation

Notices

1. Meowski's Catgirl Grooming Service (meowski@fluf.club)'s status on Friday, 21-Jun-2024 19:41:54 UTC Meowski's Catgirl Grooming Service

   • Santa Claes 🇸🇪🇭🇰🎅
   • Angry Sun
   • Phantasm
   @phnt @clacke @sun would this mean
   the history could fill up the file system tho
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 21-Jun-2024 19:41:48 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     Twice the size of the full command history of the last decade should be enough for everyone.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 21-Jun-2024 19:41:49 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Angry Sun
     • Phantasm
     @meowski @phnt @sun Scripts you run will not go into the history file, unless you're running some Expect scripts to drive interactive mode.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 21-Jun-2024 19:41:49 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Angry Sun
     • Phantasm
     @meowski @phnt @sun But yes, I set my caps Very High rather than blank. Just in case.
   • Meowski's Catgirl Grooming Service (meowski@fluf.club)'s status on Friday, 21-Jun-2024 19:41:50 UTC Meowski's Catgirl Grooming Service

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     • Angry Sun
     • Phantasm
     @phnt @clacke @sun automated commands gone awry could do it. i keep my limit very high, but it is set to a value, just for safety, "bigger problems" notwithstanding
   • Phantasm (phnt@fluffytail.org)'s status on Friday, 21-Jun-2024 19:41:53 UTC Phantasm

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     • Angry Sun
     @meowski @clacke @sun If your shell history filled your FS, you have bigger problems. My zsh one is 427K (10034 entries).
   • Meowski's Catgirl Grooming Service (meowski@fluf.club)'s status on Friday, 21-Jun-2024 19:42:01 UTC Meowski's Catgirl Grooming Service

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     • Angry Sun
     • Phantasm
     @clacke @phnt @sun thats true in general, you just never know what could happen. like i said, edge cases. i'm leaving mine set to the default behavior for bash which is just truncate and save on exit. mildly annoying but i think you need a transactional database to do this 100% safely, not just file locking and append. idk wahtever good luck though, yolo and lmk how it turns out
     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 21-Jun-2024 19:42:01 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Angry Sun
     • Phantasm

     @meowski Over a decade of bash history is going fine. 😊

     @phnt @sun

   • Meowski's Catgirl Grooming Service (meowski@fluf.club)'s status on Friday, 21-Jun-2024 19:53:50 UTC Meowski's Catgirl Grooming Service

     in reply to

     • Santa Claes 🇸🇪🇭🇰🎅
     • Angry Sun
     • Phantasm
     @clacke @phnt @sun cool have you been logging in once a day, type "ls" then close the shell? cause i do a lot of simultaneous and automated stuff through shells (fortunately none of them write to history though)
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Friday, 21-Jun-2024 19:53:50 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Angry Sun
     • Phantasm

     @meowski Some days hundreds of lines of history, many days nothing, occasionally a bunch of interactive shells running in parallel, haven't had a history file corrupted so far.

     The occasional instant power loss has lost me lines that might have been saved by a `history -a` in my PROMPT_COMMAND, but I don't know what the corruption risk would be like then.

     @phnt @sun