Is your feature request related to a problem? Please describe.
It's not a problem. But adding this feature will make user experience much better.
Describe the solution you'd like
If I open fileA, open a nvim terminal and open fileA in this terminal, a dialog complaining existing swapfile will occur.
But we know, fileA will ultimately be opened by the outer instance of nvim and will not cause a problem.
So this dialog is just annoying and better be bypassed.
Of course, this bypassing should be smart/conservative: if the existing of swapfile is caused by bad exit condition of a previous nvim process or if target file is opened by a third nvim instance (not the outer instance), the dialog should be displayed!
Describe alternatives you've considered
Considering the User experience, no alternatives exists: false-alarms should better be suppressed.
Additional context
None
Is your feature request related to a problem? Please describe.
It's not a problem. But adding this feature will make user experience much better.
Describe the solution you'd like
If I open fileA, open a nvim terminal and open fileA in this terminal, a dialog complaining existing swapfile will occur.
But we know, fileA will ultimately be opened by the outer instance of nvim and will not cause a problem.
So this dialog is just annoying and better be bypassed.
Of course, this bypassing should be smart/conservative: if the existing of swapfile is caused by bad exit condition of a previous nvim process or if target file is opened by a third nvim instance (not the outer instance), the dialog should be displayed!
Describe alternatives you've considered
Considering the User experience, no alternatives exists: false-alarms should better be suppressed.
Additional context
None