Currently, running buffer-env-update over tramp on an .env or shell script results in the program running with arguments locally it seems
Example of the error gotten:
/gnu/store/cdwviyfnsfv7k57qrwmym0mrynjixc1i-bash-5.1.16/bin/bash: line 1: /sudo:root@192.168.100.236:/root/.env: No such file or directory
Process buffer-env stderr finished
Itd be cool if atleast .env and shell scripts could be supported to run remotely via buffer-env-update, im not too familiar with tramp but i think modifying tramp-remote-process-environment would be how you achieve this. Personally my usecase for using buffer-env is usually to point to programs not in PATH, (like gopls in /usr/local/go/bin/ or a virtualenv in a directory with some development packages like lsp and linters) and allow then Emacs to find LSP servers/programs to run. This works well locally, would be great if it worked remotely too! Thanks alot for the package
Currently, running buffer-env-update over tramp on an .env or shell script results in the program running with arguments locally it seems
Example of the error gotten:
/gnu/store/cdwviyfnsfv7k57qrwmym0mrynjixc1i-bash-5.1.16/bin/bash: line 1: /sudo:root@192.168.100.236:/root/.env: No such file or directory
Process buffer-env stderr finished
Itd be cool if atleast .env and shell scripts could be supported to run remotely via buffer-env-update, im not too familiar with tramp but i think modifying tramp-remote-process-environment would be how you achieve this. Personally my usecase for using buffer-env is usually to point to programs not in PATH, (like gopls in /usr/local/go/bin/ or a virtualenv in a directory with some development packages like lsp and linters) and allow then Emacs to find LSP servers/programs to run. This works well locally, would be great if it worked remotely too! Thanks alot for the package