Re: Buffer-local process environments

[Augusto Stoffel <arstoffel@gmail.com>]

On Thu, 29 Apr 2021 at 17:37, Michael Albinus <michael.albinus@gmx.de> wrote:

> Augusto Stoffel <arstoffel@gmail.com> writes:
>
> Hi Augusto,
>

Hi Michael,

>> Point 1 is simple.  I've attached a patch for `compile' as an example.
>> In the Python REPL case, I'm not sure whether it would be better to
>> just adapt `run-python' or make a change in comint itself.
>
> Have you checked, that this works for remote processes? this is already

In fact it breaks with remote processes, see at the end of my previous
message in reply to Stefan.

But I think it's a Tramp bug.  Tramp is supposed to completely ignore
`process-environment', right?  So it shouldn't matter if that variable
is buffer local or not.

> hairy, and I fear it would be even more complicate. If we are going to
> change something in this department, I'd be happy to have also a
> rock-solid solution for remote processes.

True.  "Connection-local variable" sounds a lot like "project-local
variable" to me.  Maybe there could be a unified mechanism.

>
> See also connection-local variables, which are an attempt to make life easier.
>
> Best regards, Michael.