-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jupyter lab terminals do not remember history #16045
Comments
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗 |
This is down to specific terminal shell that you use. This is a typical behaviour of a bash shell history, nothing to do with JupyterLab itself.
This is a question best answered by https://github.com/jupyter/docker-stacks but the answer will likely depend on whether you use the default terminal shell, or customize it, and have little to do with Jupyter itself but more with the shell of choice. |
I see: Now there is .bash_history. Originally I got confused because I started a brand new container, and since the terminal does not write to bash history before closing, there is no such file... Thanks! So to confirm, do I understand correctly: JupyterLab does nothing special, but just uses the system's normal shell? |
@fzyzcjy On Linux, this is generally true; JupyterLab uses whichever shell you've chosen to use. |
Thank you! |
Description
Hi thanks for the tool! However, the terminal does not seem to remember command history.
For example, open terminal 1 and input command A, then open terminal 2 and the history of "command A" will not be found. The terminal 1 needs to be closed in order to let later terminals see its history.
By the way, as a side question, where is the command history file stored? I am using jupyter's official docker stack, thus would be great to know that folder and mount to host to avoid losing history between restarts.
Reproduce
Expected behavior
Context
Troubleshoot Output
Command Line Output
Browser Output
The text was updated successfully, but these errors were encountered: