ParetoOptimalDev <pareto.opti...@mailfence.com> writes: Hi,
>> My rough idea is to allow tramp-remote-path being nil, >> and then just don't touch anything from $PATH remotely. But I don't know >> about possible side effects. > > Oh, that's good to know because: > > - It tells me a potential avenue to explore if I look at this again out > of annoyance > - It's very possible that changing tramp-remote-path like this could > break other invariants > > Part of my confusion and frustration was not having the experience and > understanding to know for sure where issues are because of > misunderstanding or because I'm treading new ground. You might start with function tramp-set-remote-path, emulate the proposal above by just returning w/o doing anything. Afterwards, check what needs to be done in function tramp-get-remote-path. A good test is running the test suite by "make -C test tramp-tests" and see, whether everything still works. If you want to check it for the docker method, do something like "env REMOTE_TEMPORARY_FILE_DIRECTORY=/docker:alpine:/tmp make -C test tramp-tests" (I use the alpine docker image for tests). Best regards, Michael.
