Bug 19231 - eshell should set an appropriate TERM
Summary: eshell should set an appropriate TERM
Status: CLOSED WONTFIX
Alias: None
Product: Branch 4.0
Classification: Distributions
Component: emacs22-common (show other bugs)
Version: 4.0
Hardware: all Linux
: P2 normal
Assignee: Nobody's working on this, feel free to take it
QA Contact: Q.A. 4.0
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-18 18:32 MSK by Ivan Zakharyaschev
Modified: 2014-11-05 20:17 MSK (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Zakharyaschev 2009-03-18 18:32:41 MSK
emacs22-common-22.1-alt2 

Now eshell inherits the TERM from the environment in which Emacs was started. But of course, eshell is not suited to process the escape-chars of the other terminals. Demonstration (see the junk in the output):

~/tmp/test-git $ git status
# On branch A
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	[31md[m
nothing added to commit but untracked files present (use "git add" to track)
~/tmp/test-git $ echo $TERM
rxvt-unicode
~/tmp/test-git $ 

Expected: eshell should pass to the child programs a suitable TERM.

I don't know which one is the best, for now, I use dumb (the output becomes at least readable):

~/tmp/test-git $ export TERM=dumb
~/tmp/test-git $ git status
# On branch A
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	d
nothing added to commit but untracked files present (use "git add" to track)
~/tmp/test-git $
Comment 1 Ivan Zakharyaschev 2009-03-18 18:33:26 MSK
It's about M-x eshell.
Comment 2 Ivan Zakharyaschev 2009-03-18 20:53:19 MSK
This is a bug only in a graphical instance of Emacs. Inside terminals, it's ok to use the inherited TERM.
Comment 3 Eugene Vlasov 2009-03-18 21:51:12 MSK
How about post this bugs direct to upstream (M-x report-emacs-bug)?
Comment 4 Ivan Zakharyaschev 2010-05-20 06:46:22 MSD
(В ответ на комментарий №3)
> How about post this bugs direct to upstream (M-x report-emacs-bug)?

Discussing the issues with upstream developers would be the next step for me; first, I take a note of the missing feature here.

If I write these things down here, then I and other people will have a list of bugs and wishes relevant for a certain distro, which they can consult and grasp what problems they will meet if they use this distro, what missing features they would like to be implemented.

Even for "feature requests", I'd like to have a single (not per package) public (so that others can join) place with a list of the features missed, so that I can look at the list at any time in the future and decide whether I want to put more effort into one or another issue.
Comment 5 Ivan Zakharyaschev 2010-05-20 06:46:23 MSD
(В ответ на комментарий №3)
> How about post this bugs direct to upstream (M-x report-emacs-bug)?

Discussing the issues with upstream developers would be the next step for me; first, I take a note of the missing feature here.

If I write these things down here, then I and other people will have a list of bugs and wishes relevant for a certain distro, which they can consult and grasp what problems they will meet if they use this distro, what missing features they would like to be implemented.

Even for "feature requests", I'd like to have a single (not per package) public (so that others can join) place with a list of the features missed, so that I can look at the list at any time in the future and decide whether I want to put more effort into one or another issue.
Comment 6 Michael Shigorin 2014-11-05 20:17:03 MSK
В 4.0/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.