From: "andrés ramírez" <rrandresf@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Trevor Spiteri <tspiteri@ieee.org>, emacs-devel@gnu.org
Subject: Re: tramp compilation buffer also affected
Date: Mon, 09 Dec 2019 05:54:12 +0000 [thread overview]
Message-ID: <86a7826o3f.fsf@gmail.com> (raw)
In-Reply-To: <875ziq961a.fsf@mail.linkov.net>
Hi Juri.
Juri> Actually, tramp-cleanup-... don't update the existing
Juri> process-environment. You need restart Emacs after customizing
Juri> tramp-remote-process-environment.
Juri> It's easier to check whether TERM has the right value in Tramp
Juri> by simply:
Juri> M-x compile RET echo $TERM RET
--8<---------------cut here---------------start------------->8---
-*- mode: compilation; default-directory: "/ssh:aramirez@x220c:/home/aramirez/dev/wxwidgets/mamacha/src/tests/" -*-
Compilation started at Mon Dec 9 05:49:33
echo $TERM
ansi
Compilation finished at Mon Dec 9 05:49:34
--8<---------------cut here---------------end--------------->8---
It seems my snippet is not working then:
--8<---------------cut here---------------start------------->8---
(progn (setq comint-terminfo-terminal "ansi") (require
'compile)(add-to-list 'compilation-environment "TERM=dumb") (require
'tramp)(add-to-list 'tramp-remote-process-environment "TERM=dumb"))
--8<---------------cut here---------------end--------------->8---
Juri> For testing compilation highlighting, I just touch xterm.c and
Juri> compile it, because compilation of xterm.o always produces
Juri> warnings:
Juri> M-x compile RET touch xterm.c; TERM=ansi make xterm.o RET
Juri> It produces unhandled escape sequences in the compilation output
Juri> buffer:
Same case for me.
Juri> But running compile with a prefix arg processes escape sequences
Juri> and produces nice output even when Tramp process-environment is
Juri> not customized:
Juri> C-u M-x compile RET touch xterm.c; TERM=ansi make xterm.o RET
This workaround works for me. Actually IMO It should not be necessary to
restart emacs. after customizing tramp-remote-process-environment.
Thanks for the workaround. Best Regards
prev parent reply other threads:[~2019-12-09 5:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 12:37 Emacs shell: set TERM to ansi instead of dumb Trevor Spiteri
2019-11-23 15:42 ` Colin Baxter
2019-12-01 21:57 ` Juri Linkov
2019-12-04 1:48 ` rrandresf
2019-12-04 22:41 ` Juri Linkov
2019-12-05 0:11 ` tramp compilation buffer also affected (was: Emacs shell: set TERM to ansi instead of dumb) andrés ramírez
2019-12-08 21:33 ` tramp compilation buffer also affected Juri Linkov
2019-12-09 5:54 ` andrés ramírez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a7826o3f.fsf@gmail.com \
--to=rrandresf@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=tspiteri@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.