From: Samuel Wales <samologist@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: TERM and shell mode
Date: Wed, 8 Mar 2023 17:53:21 -0700 [thread overview]
Message-ID: <CAJcAo8ttV823EuGxRhBgQZ8UjLFYn191c=XY0_wBe7ntzAs0vQ@mail.gmail.com> (raw)
In-Reply-To: <83lekecnbz.fsf@gnu.org>
that var does not exist in my emacs version, so i did not set it. i
guess i should let sleeping dogs lie until new versions.
i want shell mode's features, not a terminal. shell mode works with
ansi colors. i find emacs term to be buggy.
yes, i should try vterm at some point. and coterm.
i have no settings of xterm in shell or elisp.
On 3/3/23, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Samuel Wales <samologist@gmail.com>
>> Date: Thu, 2 Mar 2023 17:18:29 -0700
>>
>> emacs -Q says dumb for TERM for shell mode. one issue with this i
>> have a note saying is that colored output can silently corrupt cmd |
>> grep if TERM=dumb. or similr. idr the details. but i recall the
>> problem and debugged it to the TERM variable.
>>
>> termprarily setting term to xterm fixed that problem but i have no
>> idea where it is being set permanntly.
>
> Did you try to change the value of comint-terminfo-terminal?
>
> Also, if you want to run programs that need colors or other features
> of a terminal emulator, I think you should use "M-x ansi-term" instead
> of "M-x shell", or at least try that to see if it solves your
> problems.
>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2023-03-09 0:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 0:18 TERM and shell mode Samuel Wales
2023-03-03 1:37 ` Emanuel Berg
2023-03-03 1:39 ` Emanuel Berg
2023-03-03 5:05 ` Akib Azmain Turja
2023-03-03 7:21 ` Eli Zaretskii
2023-03-03 7:39 ` Emanuel Berg
2023-03-09 0:53 ` Samuel Wales [this message]
2023-03-09 4:47 ` Akib Azmain Turja
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='CAJcAo8ttV823EuGxRhBgQZ8UjLFYn191c=XY0_wBe7ntzAs0vQ@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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.