unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: (getenv "TERM") always returns "dumb"
Date: Fri, 03 Sep 2004 13:24:06 -0400	[thread overview]
Message-ID: <E1C3HnC-00047G-6a@fencepost.gnu.org> (raw)
In-Reply-To: <86656xox9d.fsf@ketchup.de.uu.net> (message from Kai Grossjohann on Thu, 02 Sep 2004 11:06:38 +0200)

    Most processes started from within Emacs do not talk to a smart
    terminal, but they believe they do.

Why do they believe they do?  Is it because the Lisp code that starts
them does not specify "dumb" as the terminal type?
If so, the straightforward solution is to change the Lisp code
that invokes them.

It may seem inelegant, but at least it doesn't cause any problems.

So I have reverted the change.

    A side remark: Emacs running in a window system appears to inherit the
    terminal type from the terminal it was started from.  That is, this
    Emacs has (getenv "TERM") => "linux" because it was started from
    ~/.xinitrc, but an Emacs started from an xterm will have (getenv
    "TERM") => "xterm".  But in both cases, M-x shell RET provides the
    same terminal capabilities.

Yes, and M-x shell (through comint) sets TERM to `dumb' or `emacs'.

  reply	other threads:[~2004-09-03 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-31  0:21 (getenv "TERM) always returns "dumb" Peter Heslin
2004-08-31  9:30 ` Andreas Schwab
2004-08-31 13:35   ` Stefan
2004-08-31 19:57     ` Peter Heslin
2004-08-31 20:11     ` (getenv "TERM") " Davis Herring
2004-09-01 19:24       ` Richard Stallman
2004-09-02  9:06         ` Kai Grossjohann
2004-09-03 17:24           ` Richard Stallman [this message]
2004-09-03 18:16             ` Stefan Monnier
2004-09-03 22:34               ` Juri Linkov
2004-09-04 22:12               ` Richard Stallman
2004-09-06 16:09                 ` Stefan

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=E1C3HnC-00047G-6a@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).