From: Emanuel Berg <incal@dataswamp.org>
To: emacs-tangents@gnu.org
Subject: Re: [OT] Not clobbering bash history
Date: Thu, 07 Dec 2023 06:48:42 +0100 [thread overview]
Message-ID: <87fs0e5zr9.fsf@dataswamp.org> (raw)
In-Reply-To: 87zfymy3i6.fsf@mbork.pl
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 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 terminal I did it. Sharing history
> lessens my cognitive load.
How do you access history? One item at a time?
Because if you do one task in one terminal, maybe vading
through history one item at a time will then be annoying since
items from everywhere else, from other tasks, will make you
have to cycle a lot before you find what you look for?
Not saying you are wrong, just the discussion can go both ways.
I'm not a history user myself, really, but my zsh history
isn't shared between tmux panes. Not in xterm, not in the
Linux console.
But I never gave it any thought until now.
--
underground experts united
https://dataswamp.org/~incal
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2023-12-07 5:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wmufm7r7.fsf@catern.com>
[not found] ` <87fs12jkik.fsf@yahoo.com>
[not found] ` <d858823d-d95a-1865-7331-671e3fa6b4e4@gutov.dev>
[not found] ` <s0d34x1q050.fsf@yahoo.com>
[not found] ` <87ttphlqlo.fsf@catern.com>
[not found] ` <CAHWye8693z4hSJgEosPH9_ZrH88F5dbWXPS78EdfeT393FYG7g@mail.gmail.com>
[not found] ` <E1r5dUV-00019J-Gz@fencepost.gnu.org>
[not found] ` <87v89ujwa6.fsf@aarsen.me>
2023-11-22 20:43 ` [OT] Not clobbering bash history Jens Schmidt via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-11-22 21:50 ` Arsen Arsenović via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-11-23 12:42 ` Spencer Baugh
2023-11-23 20:12 ` Jens Schmidt via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
[not found] ` <E1r6isT-000665-Pt@fencepost.gnu.org>
[not found] ` <86il5g9qs9.fsf@aarsen.me>
[not found] ` <E1r9zM4-000405-Gg@fencepost.gnu.org>
[not found] ` <864jgy85g5.fsf@aarsen.me>
2023-12-07 2:49 ` Richard Stallman
2023-12-07 5:34 ` mbork
2023-12-07 5:48 ` Emanuel Berg [this message]
2023-12-07 9:34 ` mbork
2023-12-07 5:52 ` Yuri Khan
2023-12-07 6:22 ` Emanuel Berg
2023-12-07 6:44 ` Jean Louis
2023-12-11 12:09 ` Arsen Arsenović via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-07 13:06 ` Arsen Arsenović via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-08 3:56 ` Richard Stallman
2023-12-08 10:15 ` Arsen Arsenović via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
2023-12-08 3:54 ` Richard Stallman
2023-12-08 6:22 ` brickviking
2023-12-08 10:13 ` Arsen Arsenović via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs0e5zr9.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=emacs-tangents@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).