You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The shell writes the history file to $PWD/.shell_history. This creates this file in all sorts of places and can be somewhat annoying as well as breaking the shell when the user has no write permission in the current directorp (as experienced here https://groups.google.com/forum/#!topic/neo4j/4RVKnET9nlc).
Would a patch to change this behaviour to write to ~/.neo4j_shell_history instead be welcome? There might be an issue with multiple shells open at the same time, writing into the same history file, but that problem also exists when multiple shells are started from the same directory.
The text was updated successfully, but these errors were encountered:
@tinwelint I'm not aware of the shell history file, could you give input on this?
The only thing I can think is that maybe it's confusing if different shells share history, eg. if you run multiple dbs. But actually, I could find that pretty useful. It's like how zsh has shared history across shells, and that ends up being very useful.
@tinwelint@jakewins While this isn't a bug, it appears to be rather annoying on Windows too, where the shell launches from something like C:\Program Files\Neo4j Community, which is r/o for a non-priviliged user, causing the entered commands to become invisible without any clue as to the cause, as describe by Mark Needham here.
So, I'm thinking maybe this can be adressed pre-GA, to avoid more people running into this?
The shell writes the history file to $PWD/.shell_history. This creates this file in all sorts of places and can be somewhat annoying as well as breaking the shell when the user has no write permission in the current directorp (as experienced here https://groups.google.com/forum/#!topic/neo4j/4RVKnET9nlc).
Would a patch to change this behaviour to write to ~/.neo4j_shell_history instead be welcome? There might be an issue with multiple shells open at the same time, writing into the same history file, but that problem also exists when multiple shells are started from the same directory.
The text was updated successfully, but these errors were encountered: