browserlink.vim
browserlink.vim copied to clipboard
Node server stops and needs to be started manually from a separate terminal
trafficstars
The first save of the document starts node browserlink.js& in the background, but when it tries to send some output to stdout and does not have a controlling terminal attached (Vim has it) the process dies, so the server needs to be started in a separate terminal (that cannot be closed).
Tested in GNU/Linux [Arch].
Seem to have this issue with the most recent version
@michaelmrose have you tried #40 ?