good question, IMO I think it should retain the last namespace where it was executed, I think this most likely what user wants, I find hard to find a case where I want the same command to run in a different NS that it ran before

@cfleming ^^

@wilkerlucio Makes sense, thanks!

you'r welcome, thank you for taking the time to improve that 🙂

No worries, that will be in the next build

@wilkerlucio A common situation: I type an expression at the REPL and realize I'm in the wrong namespace because it doesn't work as expected. I switch namespaces and re-evaluate the expression from the history. So this is a concrete example where you don't want the namespace stored with the command.

ok, fair enough, but you think this is more common than switching the namespace and still want to run the same command on the new one?

to be honest, I don't care much about this scenario, I usually run commands from inside (comment) blocks on my code, so I rarely run then on the wrong namespace

but still, in the case you mentioned, you would only have to go to REPL and use up, return to rerun on the current one, and from then you could use the Run Last REPL command, sounds reasonable?

I use arrow keys in the REPL to access history, not Run Last REPL command, so as long as arrow keys aren't causing commands to run in some other namespace than the one implied by the context of the REPL, that's what matters to me.

It would be confusing to access an old command and not know what namespace it is going to run in.

we can confirm with @cfleming , but on my understanding this change would only affect the Run Last REPL Command thing, nothing about running from the REPL input should change

I agree if that changes would be confusing

How do you guys work with a project that contains multiple sub-projects? For example, take the below directory structure:

.
├── project1
├── project2
└── project3