19231 2009-03-18 18:32:41 +0300 eshell should set an appropriate TERM 2014-11-05 20:17:03 +0300 1 1 3 Distributions Branch 4.0 emacs22-common 4.0 all Linux CLOSED WONTFIX P2 normal --- 1 imz nobody qa-4.0 oldest_to_newest 87482 0 imz 2009-03-18 18:32:41 +0300 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 $ 87483 1 imz 2009-03-18 18:33:26 +0300 It's about M-x eshell. 87487 2 imz 2009-03-18 20:53:19 +0300 This is a bug only in a graphical instance of Emacs. Inside terminals, it's ok to use the inherited TERM. 87490 3 eugvv 2009-03-18 21:51:12 +0300 How about post this bugs direct to upstream (M-x report-emacs-bug)? 109347 4 imz 2010-05-20 06:46:22 +0400 (В ответ на комментарий №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. 109348 5 imz 2010-05-20 06:46:23 +0400 (В ответ на комментарий №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. 148496 6 mike 2014-11-05 20:17:03 +0300 В 4.0/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф.