unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Liu Hui <liuhui1610@gmail.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 66700@debbugs.gnu.org
Subject: bug#66700: 30.0.50; Some history is missing with multiple eshell buffers
Date: Tue, 14 Nov 2023 12:40:00 +0800	[thread overview]
Message-ID: <CAOQTW-Pd8D3ASVj+jEK8utZOXgYFCr_QC9YQ54G-SX2BdEJrZw@mail.gmail.com> (raw)
In-Reply-To: <CAOQTW-P_ZBYKm+cmZgEGBfG9NStKKb--ivpU4iiyZOqE+=d4LA@mail.gmail.com>

Hi Jim,

> Eshell saves history by default when quitting the buffer or emacs, but
> some history is missing when there are multiple eshell buffers. For
> example,
>
> 1. emacs -Q
> 2. M-x eshell, and type foo
> 3. C-u M-x eshell, and type bar
> 4. quit emacs
>
> I would expect both commands are saved, but in fact only one command
> is saved in the file eshell-history-file-name. I think the reason is
> the history file is always overwritten when an eshell buffer tries to
> save the history, so maybe eshell should save commands by appending
> to the file?

Since Eshell can append new history now, I think it makes sense to
change the default behavior from overwriting to appending, i.e., using
'(eshell-write-history nil t)' in eshell-exit-hook and
eshell-save-some-history. WDYT?





  reply	other threads:[~2023-11-14  4:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 12:14 bug#66700: 30.0.50; Some history is missing with multiple eshell buffers Liu Hui
2023-11-14  4:40 ` Liu Hui [this message]
2023-11-14 12:32   ` Eli Zaretskii
2023-11-14 12:43     ` Sean Whitton
2023-11-14 17:15       ` Jim Porter
2023-11-16  9:47         ` Liu Hui
2023-12-06 15:33           ` Sean Whitton
2023-12-07 10:23             ` Liu Hui
2023-12-07 11:33               ` Sean Whitton
2023-12-08 22:53                 ` Jim Porter
2023-11-15  9:59     ` Liu Hui
2023-11-15 12:22       ` Eli Zaretskii

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=CAOQTW-Pd8D3ASVj+jEK8utZOXgYFCr_QC9YQ54G-SX2BdEJrZw@mail.gmail.com \
    --to=liuhui1610@gmail.com \
    --cc=66700@debbugs.gnu.org \
    --cc=jporterbugs@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).