Differences

This shows you the differences between two versions of the page.

--- localization_and_you_-_utf_8_on_netbsd [2021/04/01 04:53] – [Localization and You -- UTF–8 on NetBSD] hc9
+++ localization_and_you_-_utf_8_on_netbsd [2022/02/07 20:56] – [Rxvt-Unicode] jquah
@@ Line 36: / Line 36: @@
 <file config add these lines>
-if [ $TERM == "rxvt-unicode" ] || [ $TERM == "rxvt-unicode-256color" ]; then
+if [ "$TERM" == "rxvt-unicode" ] || [ "$TERM" == "rxvt-unicode-256color" ]; then
    export TERM="rxvt"
 fi
 </file>
-In simple terms, this tricks NetBSD into thinking your terminal is rxvt, the original program urxvt is based on. If you have a MetaArpa account, don’t worry - the MetaArray is running CentOS, which understands urxvt just fine.
+In simple terms, this tricks NetBSD into thinking your terminal is rxvt, the original program urxvt is based on. However, the same volume of home directories is mounted by the OpenBSD machine //beastie//, which //does// have an entry for rxvt-unicode in its terminfo database! So if you log in to both systems on a regular basis, and on both systems you use a shell that sources ''.profile'', your OpenBSD experience might be needlessly downgraded. In that case, check that the machine you're logged into is actually NetBSD before exporting the changed value of $TERM.
+<file config add these lines>
+if [ "$TERM" == "rxvt-unicode" ] || [ "$TERM" == "rxvt-unicode-256color" ]; then
+      [ "$(uname)" == "NetBSD" ] && export TERM="rxvt"
+fi
+</file>
+(The latter code should work in any case, but it's pointless to run 'uname' on every login if you know you'll only ever be sourcing ''.profile'' from a NetBSD machine.)
+If you have a MetaArpa account, don’t worry - the MetaArray is running Debian, which understands urxvt just fine.
 ===== Escape Characters =====