Summary: | eshell should set an appropriate TERM | ||
---|---|---|---|
Product: | Branch 4.0 | Reporter: | Ivan Zakharyaschev <imz> |
Component: | emacs22-common | Assignee: | Nobody's working on this, feel free to take it <nobody> |
Status: | CLOSED WONTFIX | QA Contact: | Q.A. 4.0 <qa-4.0> |
Severity: | normal | ||
Priority: | P2 | ||
Version: | 4.0 | ||
Hardware: | all | ||
OS: | Linux |
Description
Ivan Zakharyaschev
2009-03-18 18:32:41 MSK
It's about M-x eshell. This is a bug only in a graphical instance of Emacs. Inside terminals, it's ok to use the inherited TERM. How about post this bugs direct to upstream (M-x report-emacs-bug)? (В ответ на комментарий №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. (В ответ на комментарий №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. В 4.0/branch исправления не будут вноситься уже технически (заглушена очередь на сборку), поэтому прошу ошибки, актуальные для sisyphus/p7/t7, перевесить на текущие ветки или сизиф. |