Tim Golden

The conventional approach is to attempt to acquire a mutex of some sort and, on failure, switch focus to the already-activated version of the app. Trying to activate an existing...

Alternatively, we can ignore the single-instance notion and work harder to *merge* session files when saving. Again, I don't know if this complexity outweighs the risk.

That's basically technique (1) for my post above. And it's good to have something already written and working. But it does complicate the startup of the app and leaves the...

@tonybaloney would you mind running a `make tidy` over the PR and re-push, please? I'd be very keen to get this in once it's passing tests.

@OldManTechWorld depending on what "deletes their profile" means, the following might or might not help. When it starts up, Mu will look for a file located at `%LOCALAPPDATA%\python\mu\settings.json`. (By default...

BTW I clearly need to document the "settings" setup: I had to go and revisit the code to remind myself before writing that reply. And I wrote that code in...

Sorry -- one more piece of info: the settings file does honour environment variables. So, if it helped, that setting could read, eg: `{ "workspace" : "%USERPROFILE%/mu-workspace" }`

Current state of play: Mu will detect that another instance is blocking it and will report the PID of the blocking instance. Also, all instance now log their PID with...

Thanks for the comments, @carlosperate. I realise that I have unpushed changes on my local branch, several of which will address some of the points you raise. I'll try to...

To make this concrete, I propose to add a section to the `settings` module which does the `argparse` dance to read into a `Settings`-style object called, eg, `Switches`. Those could...