unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: TERM and shell mode
Date: Thu, 2 Mar 2023 17:18:29 -0700	[thread overview]
Message-ID: <CAJcAo8s1nhRpyrHMgQ1yMJtRNNW+cvCfSgpr2B4GDWP4JjUTYw@mail.gmail.com> (raw)

ok, so this is going to be a really dumb question that i should have
figured out over the years.  and ... i sorta kinda but not really did
but i have too many notes and can't fiure them out.

and even legacy shell stuff from xemacs days and such.

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.

i can't actually figure out where in my shell code or elsewhere the
following occurs: TERM gets set to xterm.  it works well or seems to
but it might be WRONG on the internet.  and root vs. user and linux vt
console might require special casing.

-Q says supposed to be dumb, except i also recall emacs as a terminal
type.  dunno where that came from.

literally i have no shell code that sets the var althuogh it is used
as a prefix to grep and such.  of course i am not asking you to intuit
where the variable is being set but you might have interesting
comments about TERM.

example.  thisis probably bad code but it helps with grep

    TERM=xterm \
        LC_ALL=C grep -i --color=auto --devices=skip --directories=skip "$@"

-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com



             reply	other threads:[~2023-03-03  0:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03  0:18 Samuel Wales [this message]
2023-03-03  1:37 ` TERM and shell mode 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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJcAo8s1nhRpyrHMgQ1yMJtRNNW+cvCfSgpr2B4GDWP4JjUTYw@mail.gmail.com \
    --to=samologist@gmail.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).