Eshell doesn't remember history

[bandali0]

Description :octocat:

Eshell doesn't remember history

Reproduction guide :beetle:

• Start Emacs
• M-m a s e (start Eshell)
• Type out a few commands (e.g. pwd, ls, uname)
• C-d (exit the Eshell)
• M-m a s e (start Eshell again)
• M-p

Observed behaviour: :eyes: :broken_heart:

• M-p results in displaying Empty input ring in the minibar.
• Eshell doesn't save history (~/.emacs.d/.cache/eshell/ has no files)

Expected behaviour: :heart: :smile:

• M-p should go back through the history.

System Info :computer:

• OS: gnu/linux
• Emacs: 25.1.1
• Spacemacs: 0.200.7
• Spacemacs branch: develop (rev. e624e8f0)
• Graphic display: t
• Distribution: spacemacs
• Editing style: emacs
• Completion: ivy
• Layers:

  (aminb auto-completion
     (better-defaults :variables better-defaults-move-to-beginning-of-code-first t better-defaults-move-to-end-of-code-first t)
     bibtex c-c   emacs-lisp git haskell html ivy latex markdown org rust
     (shell :variables shell-default-height 30 shell-default-position 'bottom)
     shell-scripts spell-checking syntax-checking version-control yaml)

• System configuration features: XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GCONF GSETTINGS NOTIFY ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS GTK3 X11

Backtrace :paw_prints:

[bmag]

I can confirm that if I open Eshell via SPC a s e (spacemacs/shell-pop-eshell) then the history isn't saved when exiting the shell. However, if I open the shell via M-x eshell, then it does save the history when exiting the shell.

After running SPC a s e and closing the Eshell buffer with C-d, I invoked M-x shell-pop directly to get an Eshell buffer, and its history as well wasn't saved after I exited with C-d. (I checked if history was saved by opening a new M-x eshell and pressing M-p.)

Perhaps a problem with shell-pop or with our configuration of shell-pop, or perhaps Eshell doesn't work well with the buffer name given by shell-pop (a somewhat wild guess). If anyone wants to investigate this, sounds like an interesting bug.

[thornjad]

@aminb are you still experiencing this on the latest develop branch?

[Compro-Prasad]

I just tested it. This bug is still there.

[bandali0]

Sorry @thornjad I've long since stopped using spacemacs, and now use my own emacs configuration. For what it's worth, eshell history works fine with vanilla emacs + my configs.

[Compro-Prasad]

I found the reason. Its the value of eshell-exit-hook that is the problem. In the popup buffer its value is:

(shell-pop--kill-and-delete-window eshell-write-history eshell-write-last-dir-ring t)

While in normal M-x eshell its:

(eshell-write-history eshell-write-last-dir-ring t)

[natemoseman]

I think I found the problem. However I am not a elisp programmer, so I am not sure if my solution is the correct one.

Spacemacs shell layer uses 'shell-pop' extension.

In this file: https://github.com/kyagi/shell-pop-el/blob/master/shell-pop.el

in the 'shell-pop--set-exit-action' function on line 262... changing: (add-hook 'eshell-exit-hook 'shell-pop--kill-and-delete-window nil t)

to (add-hook 'eshell-exit-hook 'shell-pop--kill-and-delete-window t t)

This changed it so that add-hook appends the function to the hook list. So now 'eshell-exit-hook' gets set to:

(eshell-write-history eshell-write-last-dir-ring t shell-pop--kill-and-delete-window)

So I think that what was happening is that the eshell was exiting before it had a chance to write the history. Changing the order of the hooks now allows eshell to save it's history before the frame is deleted.

filed https://github.com/kyagi/shell-pop-el/issues/66

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

[bcc32]

I am still experiencing this issue but it appears there have been no responses on the issue in the upstream repo.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

[evorion]

I am experiencing this issue today. It's still not resolved.

[smile13241324]

Still there and not fixed upstream maybe we can find a workaround

[smile13241324]

I have added a workaround to Spacemacs circumventing the bug in the ticket. The issue is indeed that the window is set before the store history calls in the shutdown hook.