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
Empty history with sqlite file_format #9438
Comments
I think what you're experiencing is this config setting
|
@fdncred I didn't change this option at all since nushell install |
is your history_isolaion set to true or false? This statement
Says to me that it's set to true because that's how it works when it's true. If you don't want it to work that way, you can try setting it to false. |
@fdncred as I said - no change from default |
I don't think I understand what you're saying. I'm missing something. I don't have any issues with history_isolation = false. ctrl+r/hints sees the full history. up/down arrow sees the full history. history_isolation = true does nothing in plaintext mode. It's exclusively for sqlite. history_isolation = true only works in sqlite and isolates your history to each nushell session. ctrl+r and hints will still see the entire history but up/down will only see the history from the current nushell session. This is how it's supposed to work. If it's not doing this, then there may be a bug. |
@fdncred thanks for clarification. |
We're probably accept a PR for this change. Glad we're finally understanding each other. LOL |
Describe the bug
The default
plaintext
file_format allows to see command history either by Ctrl+r or navigate history list with up/down arrows.After switching to
sqlite
seems there are only session command history available with up/down arrows. Ctrl+r still shows full history.How to reproduce
plaintext
file_format in config and restart nushell.up
to see executed earlier commands (normal expected behavior).sqlite
file_format in config and restart nushell.up
and get no history (wrong behavior).Expected behavior
Full command history should be available in any file_format.
Screenshots
No response
Configuration
Additional context
No response
The text was updated successfully, but these errors were encountered: