I would keep things simpler and just stick to providing it if you want it, or not having it at all.
On Mon, 16 Mar 2026 at 00:33, Clebert Suconic <[email protected]> wrote: > > Just thought about an idea... > > > I can ask the prompt at the first time the shell is running: > > - do you want to persist the history of commands? (Y/N) > > > if Y: > > > I will print a message at the start of the shell, saying that history > of commands in this shell is preserved at (file-path-TBD) > > On Sat, Mar 14, 2026 at 2:23 PM Clebert Suconic > <[email protected]> wrote: > > > > I am adding the possibility to enable a history of commands on ./artemis > > shell > > > > > > Currently I'm enabling this as optional, as you would have to do: > > > > ./artemis shell --history my-file.txt > > > > > > > > you can see the PR at https://github.com/apache/artemis/pull/6297 .. > > .as it's pretty simple. > > > > > > > > The question I have is if I should use a default file (or even allow > > having a default file)? > > > > if I allowed a default file, where should we keep it? > > > > > > The issue why I didn't do it automatically is if people used things like: > > > > Apache Artemis 2.53.0-SNAPSHOT > connect --user=clebert > > --password=mypassword > > > > > > Such thing would be on the history file. > > > > > > > > > > Opt in is of course a non issue as the file would be clearly managed > > by the user. > > > > > > -- > > Clebert Suconic > > > > -- > Clebert Suconic > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
