How important is it that $TERM is correct? Unicorn Meta Zoo #1: Why another podcast? ...
Obeylines and gappto from etoolbox
How to find the stem of any word?
Do I need to watch Ant-Man and the Wasp and Captain Marvel before watching Avengers: Endgame?
A strange hotel
Does Mathematica have an implementation of the Poisson binomial distribution?
A faster way to compute the largest prime factor
English or Hindi translation of Vyasa Smriti
How do I reattach a shelf to the wall when it ripped out of the wall?
Older movie/show about humans on derelict alien warship which refuels by passing through a star
Has a Nobel Peace laureate ever been accused of war crimes?
How much of a wave function must reside inside event horizon for it to be consumed by the black hole?
What does a straight horizontal line above a few notes, after a changed tempo mean?
Jaya, Venerated Firemage + Chandra's Pyrohelix = 4 damage among two targets?
std::unique_ptr of base class holding reference of derived class does not show warning in gcc compiler while naked pointer shows it. Why?
How does the mezzoloth's teleportation work?
Multiple fireplaces in an apartment building?
Was Dennis Ritchie being too modest in this quote about C and Pascal?
Are there moral objections to a life motivated purely by money? How to sway a person from this lifestyle?
Which big number is bigger?
"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?
What's the difference between using dependency injection with a container and using a service locator?
Is there any pythonic way to find average of specific tuple elements in array?
Can a stored procedure reference the database in which it is stored?
Air bladders in bat-like skin wings for better lift?
How important is it that $TERM is correct?
Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
2019 Community Moderator Election Results
Why I closed the “Why is Kali so hard” questionUsing putty, Left and Right keys move cursor one word, instead of one charPrevent SSH client passing TERM environment variable to server?TERM variable in chrootIs it correct to set the $TERM variable manually?Modular $TERM for different terminal emulatorsterm definitions not foundHow and where is $TERM interpreted?Where does the TERM environment variable default get set?Does “color” in TERM always mean I can use colors?linux + tput: No value for $TERM and no -T specifiedTabbed terminal emulator that has “Save state” functionality
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I recently switched from rxvt-unicode to st. This means I went from $TERM=rxvt-unicode-256color to $TERM=st-256color.
I'm happy with the switch and want to continue to use st. However, I've noticed that certain terminal applications are unhappy with the new $TERM value. For example, emacs will not load in st with full color support unless I "trick" it into thinking that $TERM is something recognizable like $TERM=xterm-256color.
My question is: what's the risk of simply setting $TERM=xterm-256color? It seems to me that the important part of $TERM=*-256color is the 256color part and the value of * seems less important.
terminal environment-variables terminal-emulator
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
add a comment |
I recently switched from rxvt-unicode to st. This means I went from $TERM=rxvt-unicode-256color to $TERM=st-256color.
I'm happy with the switch and want to continue to use st. However, I've noticed that certain terminal applications are unhappy with the new $TERM value. For example, emacs will not load in st with full color support unless I "trick" it into thinking that $TERM is something recognizable like $TERM=xterm-256color.
My question is: what's the risk of simply setting $TERM=xterm-256color? It seems to me that the important part of $TERM=*-256color is the 256color part and the value of * seems less important.
terminal environment-variables terminal-emulator
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
add a comment |
I recently switched from rxvt-unicode to st. This means I went from $TERM=rxvt-unicode-256color to $TERM=st-256color.
I'm happy with the switch and want to continue to use st. However, I've noticed that certain terminal applications are unhappy with the new $TERM value. For example, emacs will not load in st with full color support unless I "trick" it into thinking that $TERM is something recognizable like $TERM=xterm-256color.
My question is: what's the risk of simply setting $TERM=xterm-256color? It seems to me that the important part of $TERM=*-256color is the 256color part and the value of * seems less important.
terminal environment-variables terminal-emulator
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
I recently switched from rxvt-unicode to st. This means I went from $TERM=rxvt-unicode-256color to $TERM=st-256color.
I'm happy with the switch and want to continue to use st. However, I've noticed that certain terminal applications are unhappy with the new $TERM value. For example, emacs will not load in st with full color support unless I "trick" it into thinking that $TERM is something recognizable like $TERM=xterm-256color.
My question is: what's the risk of simply setting $TERM=xterm-256color? It seems to me that the important part of $TERM=*-256color is the 256color part and the value of * seems less important.
terminal environment-variables terminal-emulator
terminal environment-variables terminal-emulator
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
asked 4 hours ago
Brian FitzpatrickBrian Fitzpatrick
85021123
85021123
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The important part of the value of TERM is that it matches an entry in the terminfo or termcap databases, and that that entry correctly describes your terminal.
You cannot reasonably go telling softwares that your terminal is XTerm, when it blatantly is not. And it is an outright error to think that other terminal emulators use all the same input/output control sequences as XTerm or provide all the same functionality.
-256color is simply a part of a name, it has no inherent meaning to most softwares (albeit that a very few do look for feature suffixes). It (primarily) only has meaning to human beings, as it is human beings that group the entries in the terminfo/termcap databases into families by their names. The feature suffixes in terminal type names are primary for humans, not for softwares.
The thing that has meaning to softwares is whether the record in the database that is so named says that the terminal supports 256 colours, and provides the control sequences for using them on that type of terminal.
That said, emacs does do its own thing, and does not simply rely upon the terminfo/termcap database. For example, it is known that its frame-set-background-mode function matches the value of TERM against ^\(xterm\|\rxvt\|dtterm\|eterm\), which is probably wrong nowadays. The correct approach here is to fix emacs so that, at last, it properly recognizes the st-256color terminal type (and putty-256color, vte-256color, and others).
Further reading
- Jonathan de Boyne Pollard (2019). "TERM". Miscellany. nosh toolset.
- https://unix.stackexchange.com/a/419092/5132
- https://stackoverflow.com/a/49364532/340790
- "Terminal-Specific Initialization". emacs Lisp. Free Software Foundation.
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
Thanks for the info. I fixed my emacs problem by adding(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!
– Brian Fitzpatrick
31 mins ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f515471%2fhow-important-is-it-that-term-is-correct%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The important part of the value of TERM is that it matches an entry in the terminfo or termcap databases, and that that entry correctly describes your terminal.
You cannot reasonably go telling softwares that your terminal is XTerm, when it blatantly is not. And it is an outright error to think that other terminal emulators use all the same input/output control sequences as XTerm or provide all the same functionality.
-256color is simply a part of a name, it has no inherent meaning to most softwares (albeit that a very few do look for feature suffixes). It (primarily) only has meaning to human beings, as it is human beings that group the entries in the terminfo/termcap databases into families by their names. The feature suffixes in terminal type names are primary for humans, not for softwares.
The thing that has meaning to softwares is whether the record in the database that is so named says that the terminal supports 256 colours, and provides the control sequences for using them on that type of terminal.
That said, emacs does do its own thing, and does not simply rely upon the terminfo/termcap database. For example, it is known that its frame-set-background-mode function matches the value of TERM against ^\(xterm\|\rxvt\|dtterm\|eterm\), which is probably wrong nowadays. The correct approach here is to fix emacs so that, at last, it properly recognizes the st-256color terminal type (and putty-256color, vte-256color, and others).
Further reading
- Jonathan de Boyne Pollard (2019). "TERM". Miscellany. nosh toolset.
- https://unix.stackexchange.com/a/419092/5132
- https://stackoverflow.com/a/49364532/340790
- "Terminal-Specific Initialization". emacs Lisp. Free Software Foundation.
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
Thanks for the info. I fixed my emacs problem by adding(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!
– Brian Fitzpatrick
31 mins ago
add a comment |
The important part of the value of TERM is that it matches an entry in the terminfo or termcap databases, and that that entry correctly describes your terminal.
You cannot reasonably go telling softwares that your terminal is XTerm, when it blatantly is not. And it is an outright error to think that other terminal emulators use all the same input/output control sequences as XTerm or provide all the same functionality.
-256color is simply a part of a name, it has no inherent meaning to most softwares (albeit that a very few do look for feature suffixes). It (primarily) only has meaning to human beings, as it is human beings that group the entries in the terminfo/termcap databases into families by their names. The feature suffixes in terminal type names are primary for humans, not for softwares.
The thing that has meaning to softwares is whether the record in the database that is so named says that the terminal supports 256 colours, and provides the control sequences for using them on that type of terminal.
That said, emacs does do its own thing, and does not simply rely upon the terminfo/termcap database. For example, it is known that its frame-set-background-mode function matches the value of TERM against ^\(xterm\|\rxvt\|dtterm\|eterm\), which is probably wrong nowadays. The correct approach here is to fix emacs so that, at last, it properly recognizes the st-256color terminal type (and putty-256color, vte-256color, and others).
Further reading
- Jonathan de Boyne Pollard (2019). "TERM". Miscellany. nosh toolset.
- https://unix.stackexchange.com/a/419092/5132
- https://stackoverflow.com/a/49364532/340790
- "Terminal-Specific Initialization". emacs Lisp. Free Software Foundation.
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
Thanks for the info. I fixed my emacs problem by adding(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!
– Brian Fitzpatrick
31 mins ago
add a comment |
The important part of the value of TERM is that it matches an entry in the terminfo or termcap databases, and that that entry correctly describes your terminal.
You cannot reasonably go telling softwares that your terminal is XTerm, when it blatantly is not. And it is an outright error to think that other terminal emulators use all the same input/output control sequences as XTerm or provide all the same functionality.
-256color is simply a part of a name, it has no inherent meaning to most softwares (albeit that a very few do look for feature suffixes). It (primarily) only has meaning to human beings, as it is human beings that group the entries in the terminfo/termcap databases into families by their names. The feature suffixes in terminal type names are primary for humans, not for softwares.
The thing that has meaning to softwares is whether the record in the database that is so named says that the terminal supports 256 colours, and provides the control sequences for using them on that type of terminal.
That said, emacs does do its own thing, and does not simply rely upon the terminfo/termcap database. For example, it is known that its frame-set-background-mode function matches the value of TERM against ^\(xterm\|\rxvt\|dtterm\|eterm\), which is probably wrong nowadays. The correct approach here is to fix emacs so that, at last, it properly recognizes the st-256color terminal type (and putty-256color, vte-256color, and others).
Further reading
- Jonathan de Boyne Pollard (2019). "TERM". Miscellany. nosh toolset.
- https://unix.stackexchange.com/a/419092/5132
- https://stackoverflow.com/a/49364532/340790
- "Terminal-Specific Initialization". emacs Lisp. Free Software Foundation.
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
The important part of the value of TERM is that it matches an entry in the terminfo or termcap databases, and that that entry correctly describes your terminal.
You cannot reasonably go telling softwares that your terminal is XTerm, when it blatantly is not. And it is an outright error to think that other terminal emulators use all the same input/output control sequences as XTerm or provide all the same functionality.
-256color is simply a part of a name, it has no inherent meaning to most softwares (albeit that a very few do look for feature suffixes). It (primarily) only has meaning to human beings, as it is human beings that group the entries in the terminfo/termcap databases into families by their names. The feature suffixes in terminal type names are primary for humans, not for softwares.
The thing that has meaning to softwares is whether the record in the database that is so named says that the terminal supports 256 colours, and provides the control sequences for using them on that type of terminal.
That said, emacs does do its own thing, and does not simply rely upon the terminfo/termcap database. For example, it is known that its frame-set-background-mode function matches the value of TERM against ^\(xterm\|\rxvt\|dtterm\|eterm\), which is probably wrong nowadays. The correct approach here is to fix emacs so that, at last, it properly recognizes the st-256color terminal type (and putty-256color, vte-256color, and others).
Further reading
- Jonathan de Boyne Pollard (2019). "TERM". Miscellany. nosh toolset.
- https://unix.stackexchange.com/a/419092/5132
- https://stackoverflow.com/a/49364532/340790
- "Terminal-Specific Initialization". emacs Lisp. Free Software Foundation.
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
edited 23 mins ago
Jeff Schaller♦
45.4k1164147
45.4k1164147
answered 36 mins ago
JdeBPJdeBP
38.8k479186
answered 36 mins ago
JdeBPJdeBP
38.8k479186
answered 36 mins ago
JdeBPJdeBP
38.8k479186
38.8k479186
Thanks for the info. I fixed my emacs problem by adding(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!
– Brian Fitzpatrick
31 mins ago
add a comment |
Thanks for the info. I fixed my emacs problem by adding(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!
– Brian Fitzpatrick
31 mins ago
Thanks for the info. I fixed my emacs problem by adding
(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!– Brian Fitzpatrick
31 mins ago
Thanks for the info. I fixed my emacs problem by adding
(add-to-list 'term-file-aliases '("st-256color" . "xterm-256color")). However, this is killing my emacs startup time so I was curious if taking a sledgehammer to the problem would cause issues... and it sounds like it probably would!– Brian Fitzpatrick
31 mins ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f515471%2fhow-important-is-it-that-term-is-correct%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
