Andrey Portnoy <aport...@fastmail.com> writes: Hi Andrey,
>> My approach is different. When tramp-remote-path is >> '(tramp-own-remote-path), I intend to check nothing, and to set >> NOTHING. The remote $PATH is already proper per definition. > > Yes, both my patches are variations on a very similar approach, which is > to skip the checks and the setting when two criteria are fullfilled: > > 1. tramp-remote-path is '(tramp-own-remote-path), and OK. > 2. tramp-optimize-remote-path is set to nil. > > The reasons I think tramp-optimize-remote-path should exist are: > > - provide backward compatibility for users who have been expecting the > checks to always be there > > - provide the ability to disable them for all possible values of > tramp-remote-path, and not just when '(tramp-own-remote-path) As I told already, I don't see this need. If we offer this as general configurTION OPTION, people will set this option blindly to nil, and will wonder if Tramp changes its behavior and/or runs into trouble. And we'll see the error reports then. Pls continue, with just 1. Best regards, Michael.
