From: Spencer Baugh <sbaugh@catern.com>
To: "Arsen Arsenović" <arsen@aarsen.me>,
"Jens Schmidt" <jschmidt4gnu@vodafonemail.de>
Cc: rms@gnu.org, brickviking <brickviking@gmail.com>,
luangruo@yahoo.com, emacs-tangents@gnu.org
Subject: Re: [OT] Not clobbering bash history
Date: Thu, 23 Nov 2023 12:42:15 +0000 (UTC) [thread overview]
Message-ID: <878r6ok5f2.fsf@catern.com> (raw)
In-Reply-To: <86il5te90a.fsf@aarsen.me>
Arsen Arsenović <arsen@aarsen.me> writes:
> Jens Schmidt <jschmidt4gnu@vodafonemail.de> writes:
>
>> Moving to tangents ... please CC me.
>>
>> On 2023-11-22 04:32, Arsen Arsenović wrote:
>>
>>>> Should we suggest that the Bash developer add a feature to handle this
>>>> case (multiple shells in parallel) the "right" way? If many users
>>>> would like it, that could make it worth building in.
>>>
>>> That would be very nice. This issue has almost been prolific enough to
>>> force me to switch shells.
>>
>> This Bash-bashing made me curious, as I do not remember having issues
>> with loss of its history, ever.
>
> I do not partake in bash-bashing enthusiastically. I'm a big fan of
> readline and appreciate how reliable bash is.
>
>> And that without such tricks as using an ever growing history file. I
>> just use "shopt -s histappend" and 4096 lines as HISTFILESIZE. Plus I
>> close my Bashes orderly before shutting down. Plus I do not use Bash
>> from Emacs, only in "real" terminals. Eh, plus I rarely use nested
>> Bashes.
>>
>> So given all that, is there a reproducer for this?
>
> Unfortunately, I have been unable to produce a decent set of
> reproduction steps. This issue happens (relatively) infrequently and
> inexplicably on my machines. It pains me to complain without solid
> information.
>
> I also have shopt -s histappend set.
>
> I suspect that something starts a bash process and does not set
> histappend (--norc?), leading bash to override history.
I've always suspected TRAMP of this.
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
next prev parent reply other threads:[~2023-11-23 12:42 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 [this message]
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
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=878r6ok5f2.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=arsen@aarsen.me \
--cc=brickviking@gmail.com \
--cc=emacs-tangents@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=luangruo@yahoo.com \
--cc=rms@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).