Open adamwight opened 7 years ago
I tried this simple workaround, but still unable to set things up with two local editors:
mv ~/PhpstormProjects/proj1
to a new location.:FlooJoinWorkspace https://floobits.com/adamwight/photo-booth/
Save workspace files to: /home/you/proj1
The gotcha is that PHPStorm will now use nvim's project directory when trying to re-join the workspace.
I'm seeing errors every time I switch between a web editor and nvim, with a third IntelliJ editor idling in the background.
Steps to reproduce:
It looks like nvim is able to detect that the local clone is in ~/PhpstormProjects, and edits there. My wild guess is that the local processes are contending for access or modification time.
This is an edge case, but not totally unreasonable--I can imagine wanting to edit in nvim and PHPStorm at the same time to take advantage of their strengths, and meanwhile connecting to a group Floo.
It would be fine to clone two separate repos and use the local editors on different copies, using Floo for synchronization--but floobits-neovim seems to insist on reusing PHPStorm's checkout. I haven't figured out how nvim discovers that local path.