unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: Jens Schmidt via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: "Spencer Baugh" <sbaugh@catern.com>, "Arsen Arsenović" <arsen@aarsen.me>
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 21:12:08 +0100	[thread overview]
Message-ID: <c3f683d3-fec2-4dd0-b4d6-977c886f5a18@vodafonemail.de> (raw)
In-Reply-To: <878r6ok5f2.fsf@catern.com>

On 2023-11-23  13:42, Spencer Baugh wrote:
> Arsen Arsenović <arsen@aarsen.me> writes:
>
>> 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.

Arsen's problem description rang a bell ... on my development server
at work I configure a non-standard history file in my .bashrc.  And
regardless of that, every now and then, the default ~/.bash_history
gets created.

So probably a work-around for your overwrite problems could be exactly
that: Just configure HISTFILE=~/.my_hidden_bash_history near the same
spot where you set 'shopt -s histappend'.  Any villain not respecting
the latter won't (hopefully) respect the former as well, leaving your
non-default Bash history untouched.  (Unless you have tried that
already, of course.)

Besides that, the contents and timestamp of the default ~/.bash_history,
should it still get created, could then help finding the villain.


---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)

  reply	other threads:[~2023-11-23 20:12 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 [this message]
     [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=c3f683d3-fec2-4dd0-b4d6-977c886f5a18@vodafonemail.de \
    --to=emacs-tangents@gnu.org \
    --cc=arsen@aarsen.me \
    --cc=brickviking@gmail.com \
    --cc=jschmidt4gnu@vodafonemail.de \
    --cc=luangruo@yahoo.com \
    --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).