bug#57556: 28.1; Eshell not finding executables in PATH when tramp-integration loaded

[Jim Porter]

On 10/16/2022 1:51 PM, Richard Stallman wrote:
> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
> [[[ whether defending the US Constitution against all enemies,     ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
>    > My intent was to make that display as all-caps in the HTML documentation
>    > as well. In that excerpt, 'NAME' should always be an environment
>    > variable, so I used the capitalization conventions that env vars usually
>    > use. 'name', on the other hand, could be a Lisp variable or an env var.
>
> It should be @var{name} to express that it is a metasyntactic variable
> that stands for something called ``name''.

Thanks. I've fixed my changes in the Eshell manual to use this 
convention now, and also added some further cross-references.

I've attached (hopefully) the final version of these patches, which I'll 
merge in the next day or so, unless someone finds any other issues.

0001-Remove-over-quoting-of-application-values-in-connect.patch
Description: Text document

0002-Add-helpers-to-dynamically-assign-connection-local-v.patch
Description: Text document

0003-Allow-ignoring-errors-when-calling-eshell-match-comm.patch
Description: Text document

0004-Obsolete-eshell-define.patch
Description: Text document

0005-Allow-setting-the-values-of-variable-aliases-in-Eshe.patch
Description: Text document

0006-Improve-handling-of-PATH-in-Eshell-for-remote-direct.patch
Description: Text document

0007-Print-the-correct-PATH-when-Eshell-s-which-fails-to-.patch
Description: Text document