Closed daniprado closed 2 years ago
I understand the problem better now. Some nvim GUIs (nvim-qt, neovide,...) require "--" before accepting parameters meant for the nvim backend. Others do not require this.
This minimal change would allow defining NVR_CMD to take this situation into account.
In my previous example:
NVR_CMD="nvim-qt --" nvr -s --servername ~/test p.txt
would work as expected.
Starting with version 2.5.0, the use of custom $NVR_CMD fails without opening the server. My guessing is: the "listen" option is not sent in the right position to be processed by the nvim backend. Example:
NVR_CMD=nvim-qt nvr -s --servername ~/test p.txt
results innvim-qt: Unknown option 'listen'.
This worked well in 2.4.x (and previous) versions.
Software versions: