bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#29583: [PATCH] 25.2.50; Allow setting a custom TERM for comint


From: Allen Li
Subject: bug#29583: [PATCH] 25.2.50; Allow setting a custom TERM for comint
Date: Tue, 12 Dec 2017 19:35:47 -0800

On Tue, Dec 12, 2017 at 1:16 AM, Michael Albinus <michael.albinus@gmx.de> wrote:
> Allen Li <vianchielfaura@gmail.com> writes:
>
> Hi Allen,
>
>> +@vindex comint-terminfo-terminal
>> +Emacs sets the @code{TERM} environment variable to a safe value, but
>> +this value may not reflect the full features of comint.  For example,
>> +color is disabled for some applications that use @code{TERM} to
>> +determine if color is supported.  On systems that use terminfo, you
>> +can configure @code{comint-terminfo-terminal} to a terminal that is
>> +present in your system's terminfo database.
>
> You might mention that some applications will override this. For
> example, Tramp will always use `tramp-terminal-type' (which is
> "dumb"). This is because Tramp will run into problems if color is enabled.
>
> Btw, environment variables in the Emacs manual are emphazised as @env{TERM}.
>
> Best regards, Michael.

Thanks, fixed to use @env.  I've changed it to say that Comint uses
this, rather than Emacs.  Naturally, derived modes may override this
behavior; I don't think it's necessary to point that out unless it
turns out to be a common misconception.

Attachment: 0001-Add-option-to-configure-comint-TERM.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]