From: Yuri Khan <yuri.v.khan@gmail.com>
To: mbork@mbork.pl
Cc: rms@gnu.org, "Arsen Arsenović" <arsen@aarsen.me>,
brickviking@gmail.com, sbaugh@catern.com, luangruo@yahoo.com,
emacs-tangents@gnu.org
Subject: Re: [OT] Not clobbering bash history
Date: Thu, 7 Dec 2023 12:52:09 +0700 [thread overview]
Message-ID: <CAP_d_8VYJXqW6KKmC2sO=dauT3a+EoeE1oDtk-A1wejK1q1xYQ@mail.gmail.com> (raw)
In-Reply-To: <87zfymy3i6.fsf@mbork.pl>
On Thu, 7 Dec 2023 at 12:40, <mbork@mbork.pl> 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 terminal I did it.
To add to this: The original terminal where I issued the command I
need might be busy, e.g. if I started some application in it. It might
be inconvenient to suspend that application just to get at the
command. Important special case: the application that’s occupying the
terminal where the original command was entered is Midnight Commander
running a sub-shell in which I want to repeat that command.
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2023-12-07 5:52 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
2023-12-07 9:34 ` mbork
2023-12-07 5:52 ` Yuri Khan [this message]
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='CAP_d_8VYJXqW6KKmC2sO=dauT3a+EoeE1oDtk-A1wejK1q1xYQ@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=arsen@aarsen.me \
--cc=brickviking@gmail.com \
--cc=emacs-tangents@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mbork@mbork.pl \
--cc=rms@gnu.org \
--cc=sbaugh@catern.com \
/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).