I'm using Oil as my file manager.
When I open Oil, it uses (if I understand correctly) a protocol oil:///<path/to/a/file> and it is used as a buffer name/path.
Opening a buffer menu shortens the path, removing a slash from buffer name, with oil it becomes oil://<path/to/a/file> making it inaccessible.
The bug reported to oil as well, as, on their side, after opening a file, oil buffer should close immediately, which is not the case. But with oil open, I cannot navigate properly to other buffers and return to oil.
Maybe, there should be a condition to check if the buffer is a protocol, with, for example a regex .*:///.* to not normalize the path.
I'm using Oil as my file manager. When I open Oil, it uses (if I understand correctly) a protocol
oil:///<path/to/a/file>and it is used as a buffer name/path. Opening a buffer menu shortens the path, removing a slash from buffer name, with oil it becomesoil://<path/to/a/file>making it inaccessible. The bug reported to oil as well, as, on their side, after opening a file, oil buffer should close immediately, which is not the case. But with oil open, I cannot navigate properly to other buffers and return to oil.Maybe, there should be a condition to check if the buffer is a protocol, with, for example a regex
.*:///.*to not normalize the path.