Re: Reliably sending binary codes to TRAMP processes

Howdy,


Piggybacking off of this I've turned on direct async via 
connection-local-variables

	  (tramp-direct-async-process . t)

and I notice that my comint buffer now has escape codes in it. 
ansi-color-for-comint-mode is t and ansi-color-process-output is in 
comint-output-filters-functions. It's just the 
tramp-direct-async-process usage affecting this.

I'll have a look at tramp-verbose logs, maybe some double-escaping idk; 
short-cutting that do you know of a fix?


/Jordan

P.S. I hope you're doing ok Michael!