Re: [OT] Not clobbering bash history

2023-12-06 Thread Richard Stallman
[[[ To any NSA and FBI agents reading my email: please consider]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] I moved this to emacs-tangents because thus isn't really about Emacs, but I don't kno

Re: [OT] Not clobbering bash history

2023-12-06 Thread mbork
On 2023-12-06, at 21:49, Richard Stallman wrote: > That makes a kind of sense, but what I would envision is that each > Bash process has its own history with only the commands of that process. > > Why do you prefer the shared history file approach > to the one-history-per-process approach? Isn'

Re: [OT] Not clobbering bash history

2023-12-06 Thread Yuri Khan
On Thu, 7 Dec 2023 at 12:40, wrote: > Isn't it obvious? If I have several terminals open at the same time > (and I seldom have fewer than, say, three, usually more), sharing > history is very useful. It easy to remember that I issued some kind of > command, but much more difficult to remember i

Re: [OT] Not clobbering bash history

2023-12-06 Thread Emanuel Berg
mbork wrote: >> That makes a kind of sense, but what I would envision is >> that each Bash process has its own history with only the >> commands of that process. >> >> Why do you prefer the shared history file approach to the >> one-history-per-process approach? > > Isn't it obvious? If I have sev

Re: [OT] Not clobbering bash history

2023-12-06 Thread Emanuel Berg
Yuri Khan wrote: >> Isn't it obvious? If I have several terminals open at the >> same time (and I seldom have fewer than, say, three, >> usually more), sharing history is very useful. It easy to >> remember that I issued some kind of command, but much more >> difficult to remember in which termina