Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
1
answers
1913
views
Start Xterm + run command + keep open and interactive
I'm autostarting (from i3wm) an xterm and running a simple command exec xterm -hold -e "echo hello" how do I keep the xterm interactive? relevant posts: - https://askubuntu.com/questions/928536/script-to-open-terminal-run-command-and-keep-terminal-open ty
I'm autostarting (from i3wm) an xterm and running a simple command
exec xterm -hold -e "echo hello"
how do I keep the xterm interactive?
relevant posts:
- https://askubuntu.com/questions/928536/script-to-open-terminal-run-command-and-keep-terminal-open
ty
emile
(11 rep)
Mar 16, 2023, 11:30 AM
• Last activity: Jul 12, 2025, 08:10 AM
6
votes
1
answers
2068
views
Failed to start chromium on a X-forwarded ssh connection
When I tried to start chromium, I had error messages : ``` $ chromium X11 connection rejected because of wrong authentication. [10139:10139:0321/173002.675673:ERROR:ozone_platform_x11.cc(234)] Missing X server or $DISPLAY [10139:10139:0321/173002.675976:ERROR:env.cc(225)] The platform failed to init...
When I tried to start chromium, I had error messages :
$ chromium
X11 connection rejected because of wrong authentication.
[10139:10139:0321/173002.675673:ERROR:ozone_platform_x11.cc(234)] Missing X server or $DISPLAY
[10139:10139:0321/173002.675976:ERROR:env.cc(225)] The platform failed to initialize. Exiting.
$ echo $DISPLAY
localhost:10.0
$ xterm # xterm starts fine
Philippe
(1505 rep)
Mar 21, 2022, 05:40 PM
• Last activity: Jul 4, 2025, 09:11 PM
1
votes
2
answers
788
views
I have a problem with windows xterm in airgeddon
VMware Linux 2024.3 This problem appeared with me after updating Kali Linux windows xterm It became small and I had to enlarge it manually. When I search for networks or attack the evil twin, the windows that appear automatically are very small. They used to appear normally before the update. What i...
VMware
Linux 2024.3
This problem appeared with me after updating Kali Linux windows xterm It became small and I had to enlarge it manually. When I search for networks or attack the evil twin, the windows that appear automatically are very small. They used to appear normally before the update. What is the solution to the problem?

Ahmed magdy
(11 rep)
Sep 22, 2024, 11:57 PM
• Last activity: May 29, 2025, 10:05 AM
0
votes
1
answers
93
views
Moving word forward and word backward in zsh on uxterm on a PC
[It has long been known](http://wwwbroy.in.tum.de/~malkis/howToReviewPapers.htm) that in certain editors and shells on a PC, to go one word forward, you hit Alt + f or Ctrl + → , and to go one word backward, you hit Alt + b or Ctrl + ← . In zsh in uxterm on Gnome+Xorg on Debian 12 bookworm on a PC,...
[It has long been known](http://wwwbroy.in.tum.de/~malkis/howToReviewPapers.htm) that in certain editors and shells on a PC, to go one word forward, you hit Alt+f or Ctrl+→, and to go one word backward, you hit Alt+b or Ctrl+←. In zsh in uxterm on Gnome+Xorg on Debian 12 bookworm on a PC, neither of these key combinations works despite
bindkey -e
in .zshrc
. The script uxterm lies in /usr/bin/uxterm
, which contains, among others, a line # $XTermId: uxterm,v 1.29 2020/03/07 15:52:31 tom Exp $
and belongs to the package xterm version 379-1.
Pressing and releasing Alt+b yields â in uxterm.
Pressing and releasing Alt+f yields æ in uxterm.
The cursor started moving wordwise on Ctrl+← and Ctrl+→ after putting
bindkey "^[[1;5D" backward-word # for Ctrl + ←
bindkey "^[[1;5C" forward-word # for Ctrl + →
into .zshrc
, of course, specifically in uxterm on the computer we use in this question. As these control sequences may change when moving from one system to another, we'd welcome it if these lines were not part of a self-made configuration in /home/username/
, which can potentially get moved or copied to other computers, but part of some system-wide script. Is there any Debian package with a zsh script that already sets up the word-forward and word-backward key combinations? Or should it be the job of bindkey -e
?
user743115
(1 rep)
May 21, 2025, 06:31 PM
• Last activity: May 24, 2025, 08:49 AM
7
votes
1
answers
513
views
rxvt-unicode and xterm different yellow colors in journalctl
Recently, I noticed something strange. If I run the command `sudo journalctl -f -u ModemManager` in `rxvt-unicode` (left) and `xterm` (right), in `rxvt-unicode` the yellow does not appear when the message is a warning. Both terminals have `TERM=xterm-256color` and I noticed this problem only in yell...
Recently, I noticed something strange. If I run the command
xterm Right:
sudo journalctl -f -u ModemManager
in rxvt-unicode
(left) and xterm
(right), in rxvt-unicode
the yellow does not appear when the message is a warning.
Both terminals have TERM=xterm-256color
and I noticed this problem only in yellow, as the red appears in both terminals.
I tried different escape sequences, but I was not able to detect the problem.

urxvt
" class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy">
cacamailg
(193 rep)
Apr 13, 2025, 07:32 PM
• Last activity: Apr 15, 2025, 10:55 AM
24
votes
2
answers
27741
views
How to configure the double click behavior in an X terminal?
Under different Unix/Linux systems I've observed different double click behavior in X terminal applications (e.g. xterm). Sometimes a double click selects everything left and right until the next non-alphabetic character (e.g. it selects the word under the cursor). Sometimes everything until the nex...
Under different Unix/Linux systems I've observed different double click behavior in X terminal applications (e.g. xterm).
Sometimes a double click selects everything left and right until the next non-alphabetic character (e.g. it selects the word under the cursor).
Sometimes everything until the next blank/eol is selected (e.g. full paths under the cursor are selected).
How can I configure the double click behavior - say - in xterm (because it is available on most systems)?
Currently, I find the 2nd mode more convenient for most use cases.
maxschlepzig
(59492 rep)
Aug 20, 2012, 06:22 PM
• Last activity: Mar 15, 2025, 07:55 PM
3
votes
3
answers
2122
views
Wrong colors in xterm
I don't quite understand XTerm's (UXTerm's in this case) behaviour regarding colors. I'm using Solarized Light color theme for Alacritty and UXTerm. They're more or less identical: `~/.alacritty.yml`: ``` # Colors (Solarized Light) colors: # Default colors primary: background: '0xfdf6e3' foreground:...
I don't quite understand XTerm's (UXTerm's in this case) behaviour regarding colors. I'm using Solarized Light color theme for Alacritty and UXTerm. They're more or less identical:
UXTerm:
Though all is fine in emacs:
Alacritty:
UXTerm:
Both pass this test I've found:
UXTerm:
The prompt:
EDIT2: Forgot to mention one (probably relevant) detail: if I get rid of the color scheme whatsoever, UXTerm starts to show colors at least _resembling_ Alacritty's:
So the direction is kinda correct. But it's plain unusable to me in this state.
~/.alacritty.yml
:
# Colors (Solarized Light)
colors:
# Default colors
primary:
background: '0xfdf6e3'
foreground: '0x586e75'
# Normal colors
normal:
black: '0x073642'
red: '0xdc322f'
green: '0x859900'
yellow: '0xb58900'
blue: '0x268bd2'
magenta: '0xd33682'
cyan: '0x2aa198'
white: '0xeee8d5'
# Bright colors
bright:
black: '0x002b36'
red: '0xcb4b16'
green: '0x586e75'
yellow: '0x657b83'
blue: '0x839496'
magenta: '0x6c71c4'
cyan: '0x93a1a1'
white: '0xfdf6e3'
~/.Xresources
:
#define S_base03 #002b36
#define S_base02 #073642
#define S_base01 #586e75
#define S_base00 #657b83
#define S_base0 #839496
#define S_base1 #93a1a1
#define S_base2 #eee8d5
#define S_base3 #fdf6e3
#define S_yellow #b58900
#define S_orange #cb4b16
#define S_red #dc322f
#define S_magenta #d33682
#define S_violet #6c71c4
#define S_blue #268bd2
#define S_cyan #2aa198
#define S_green #859900
!fonts&stuff
UXTerm*faceSize: 11
uxterm*eightBitInput: false
UXTerm*faceName: Fira Mono Regular
!Background & foreground
UXTerm*background: S_base3
UXTerm*foreground: S_base00
UXTerm*fading: 40
UXTerm*fadeColor: S_base3
UXTerm*cursorColor: S_base01
UXTerm*pointerColorBackground: S_base1
UXTerm*pointerColorForeground: S_base01
!UXTerm*borderColor: #343434
!Turning off scrollbar
UXTerm*scrollBar: off
!Starting up with a geometry
UXTerm*vt100*geometry: 160x50
!Colors
!-------------------------
!black
UXTerm*color0: S_base02
UXTerm*color8: S_base03
!red
UXTerm*color1: S_red
UXTerm*color9: S_orange
!green
UXTerm*color2: S_green
UXTerm*color10: S_base01
!yellow
UXTerm*color3: S_yellow
UXTerm*color11: S_base00
!blue
UXTerm*color4: S_blue
UXTerm*color12: S_base0
!magenta
UXTerm*color5: S_magenta
UXTerm*color13: S_violet
!cyan
UXTerm*color6: S_cyan
UXTerm*color14: S_base1
!white
UXTerm*color7: S_base2
UXTerm*color15: S_base3
Alacritty session:
trueneu@pop-os:~$ env | grep TERM
COLORTERM=truecolor
TERM=xterm-256color
UXTerm session:
trueneu@pop-os:~$ env | grep TERM
COLORTERM=truecolor
XTERM_VERSION=XTerm(353)
XTERM_SHELL=/bin/bash
XTERM_LOCALE=en_US.UTF-8
TERM=xterm-256color
But they show completely different behaviours color-wise:
Alacritty:




#!/usr/bin/env bash
awk 'BEGIN{
s="/\\/\\/\\/\\/\\"; s=s s s s s s s s;
for (colnum = 0; colnum255) g = 510-g;
printf "\033[48;2;%d;%d;%dm", r,g,b;
printf "\033[38;2;%d;%d;%dm", 255-r,255-g,255-b;
printf "%s\033[0m", substr(s,colnum+1,1);
}
printf "\n";
}'
Alacritty:


PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
Same with ls
colors.
UXTerm's infocmp
, if it helps:
Reconstructed via infocmp from file: /lib/terminfo/x/xterm-256color
xterm-256color|xterm with 256 colors,
am, bce, ccc, km, mc5i, mir, msgr, npc, xenl,
colors#0x100, cols#80, it#8, lines#24, pairs#0x10000,
acsc=``aaffggiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, blink=\E[5m, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=\r,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=\n, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dim=\E[2m,
dl=\E[%p1%dM, dl1=\E[M, ech=\E[%p1%dX, ed=\E[J, el=\E[K,
el1=\E[1K, flash=\E[?5h$\E[?5l, home=\E[H,
hpa=\E[%i%p1%dG, ht=^I, hts=\EH, ich=\E[%p1%d@,
il=\E[%p1%dL, il1=\E[L, ind=\n, indn=\E[%p1%dS,
initc=\E]4;%p1%d;rgb\:%p2%{255}%*%{1000}%/%2.2X/%p3%{255}%*%{1000}%/%2.2X/%p4%{255}%*%{1000}%/%2.2X\E\\,
invis=\E[8m, is2=\E[!p\E[?3;4l\E[4l\E>, kDC=\E[3;2~,
kEND=\E[1;2F, kHOM=\E[1;2H, kIC=\E[2;2~, kLFT=\E[1;2D,
kNXT=\E[6;2~, kPRV=\E[5;2~, kRIT=\E[1;2C, kb2=\EOE, kbs=^?,
kcbt=\E[Z, kcub1=\EOD, kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\EOP, kf10=\E[21~,
kf11=\E[23~, kf12=\E[24~, kf13=\E[1;2P, kf14=\E[1;2Q,
kf15=\E[1;2R, kf16=\E[1;2S, kf17=\E[15;2~, kf18=\E[17;2~,
kf19=\E[18;2~, kf2=\EOQ, kf20=\E[19;2~, kf21=\E[20;2~,
kf22=\E[21;2~, kf23=\E[23;2~, kf24=\E[24;2~,
kf25=\E[1;5P, kf26=\E[1;5Q, kf27=\E[1;5R, kf28=\E[1;5S,
kf29=\E[15;5~, kf3=\EOR, kf30=\E[17;5~, kf31=\E[18;5~,
kf32=\E[19;5~, kf33=\E[20;5~, kf34=\E[21;5~,
kf35=\E[23;5~, kf36=\E[24;5~, kf37=\E[1;6P, kf38=\E[1;6Q,
kf39=\E[1;6R, kf4=\EOS, kf40=\E[1;6S, kf41=\E[15;6~,
kf42=\E[17;6~, kf43=\E[18;6~, kf44=\E[19;6~,
kf45=\E[20;6~, kf46=\E[21;6~, kf47=\E[23;6~,
kf48=\E[24;6~, kf49=\E[1;3P, kf5=\E[15~, kf50=\E[1;3Q,
kf51=\E[1;3R, kf52=\E[1;3S, kf53=\E[15;3~, kf54=\E[17;3~,
kf55=\E[18;3~, kf56=\E[19;3~, kf57=\E[20;3~,
kf58=\E[21;3~, kf59=\E[23;3~, kf6=\E[17~, kf60=\E[24;3~,
kf61=\E[1;4P, kf62=\E[1;4Q, kf63=\E[1;4R, kf7=\E[18~,
kf8=\E[19~, kf9=\E[20~, khome=\EOH, kich1=\E[2~,
kind=\E[1;2B, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
kri=\E[1;2A, mc0=\E[i, mc4=\E[4i, mc5=\E[5i, meml=\El,
memu=\Em, oc=\E]104\007, op=\E[39;49m, rc=\E8, rev=\E[7m,
ri=\EM, rin=\E[%p1%dT, ritm=\E[23m, rmacs=\E(B,
rmam=\E[?7l, rmcup=\E[?1049l\E[23;0;0t, rmir=\E[4l,
rmkx=\E[?1l\E>, rmm=\E[?1034l, rmso=\E[27m, rmul=\E[24m,
rs1=\Ec\E]104\007, rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7,
setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
sgr=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p5%t;2%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m,
sgr0=\E(B\E[m, sitm=\E[3m, smacs=\E(0, smam=\E[?7h,
smcup=\E[?1049h\E[22;0;0t, smir=\E[4h, smkx=\E[?1h\E=,
smm=\E[?1034h, smso=\E[7m, smul=\E[4m, tbc=\E[3g,
u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?%[;0123456789]c,
u9=\E[c, vpa=\E[%i%p1%dd,
Am I missing some configuration here? Is this how XTerm works? I don't really understand how's it capable of passing that test though.
EDIT:
After Thomas Dickey's answer, I've indeed tried to redefine .Xresources to be without C preprocessor #define
s. Here's the result:
!fonts&stuff
UXTerm*faceSize: 11
uxterm*eightBitInput: false
UXTerm*faceName: Fira Mono Regular
!Background & foreground
UXTerm*background: #fdf6e3
UXTerm*foreground: #657b83
UXTerm*fading: 40
UXTerm*fadeColor: #fdf6e3
UXTerm*cursorColor: #586e75
UXTerm*pointerColorBackground: #93a1a1
UXTerm*pointerColorForeground: #586e75
!UXTerm*borderColor: #343434
!Turning off scrollbar
UXTerm*scrollBar: off
!Starting up with a geometry
UXTerm*vt100*geometry: 160x50
!Colors
!-------------------------
!black
UXTerm*color0: #073642
UXTerm*color8: #002b36
!red
UXTerm*color1: #dc322f
UXTerm*color9: #cb4b16
!green
UXTerm*color2: #859900
UXTerm*color10: #586e75
!yellow
UXTerm*color3: #b58900
UXTerm*color11: #657b83
!blue
UXTerm*color4: #268bd2
UXTerm*color12: #839496
!magenta
UXTerm*color5: #d33682
UXTerm*color13: #6c71c4
!cyan
UXTerm*color6: #2aa198
UXTerm*color14: #93a1a1
!white
UXTerm*color7: #eee8d5
UXTerm*color15: #fdf6e3
Loaded the settings without -merge
just to be sure:
xrdb ~/.Xresources
And launched UXTerm:


Pavel Gurkov
(165 rep)
Sep 10, 2020, 09:45 PM
• Last activity: Feb 23, 2025, 11:47 PM
2
votes
2
answers
1587
views
Unable to see the menu in xterm
Not sure what the deal is, but I can't see the menu in xterm when I Ctrl+Right Click or Ctrl+Left Click . My `.Xresources` file is pretty generic; nothing fancy, so I don't think that's the problem. [![enter image description here][1]][1] [1]: https://i.sstatic.net/kGzuM.png
Not sure what the deal is, but I can't see the menu in xterm when I Ctrl+Right Click or Ctrl+Left Click.
My
My
.Xresources
file is pretty generic; nothing fancy, so I don't think that's the problem.

John DeBord
(169 rep)
Apr 8, 2018, 02:53 AM
• Last activity: Feb 2, 2025, 09:28 PM
0
votes
1
answers
114
views
How do I remove white border of XTerm window?
Couldn't find any answers to this. [![Problem itself][1]][1] `XTerm*internalBorder` actually is a padding between the black border and terminal contents; `XTerm*borderWidth` is the black border. Couldn't find a resource for the white one, I've built XTerm from source and could it be from `--enable-X...
Couldn't find any answers to this.

XTerm*internalBorder
actually is a padding between the black border and terminal contents;
XTerm*borderWidth
is the black border.
Couldn't find a resource for the white one, I've built XTerm from source and could it be from --enable-Xaw3d
since the border is 3d-ish if you look closely?
**EDIT**: I've rebuilt it with bare ./configure
without any flags and the border is gone, I guess I'll try to debug which one does enable it and then make an answer for this.

ay0ks
(1 rep)
Jan 16, 2025, 04:34 PM
• Last activity: Jan 20, 2025, 10:25 AM
11
votes
5
answers
24129
views
xterm not displaying unicode
i have never been able to get my terminal to display unicode symbols. for example, before i had my present os, i mapped ctrl+a to the greek mu in vim, and it works on other computers, but not on my current xterm. here is the relevant section of my `.vimrc`: set encoding=utf-8 "map control-a to mu im...
i have never been able to get my terminal to display unicode symbols. for example, before i had my present os, i mapped ctrl+a to the greek mu in vim, and it works on other computers, but not on my current xterm. here is the relevant section of my
.vimrc
:
set encoding=utf-8
"map control-a to mu
imap m*
also, i need to output sympy equations in python, and this works on other computers, but not on my current xterm. instead of this:
$ python
Python 2.7.3 (default, Mar 14 2014, 11:57:14)
[GCC 4.7.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sympy
>>> x = sympy.symbols('x')
>>> sympy.init_printing()
>>> (sympy.sqrt(x**3/(x+1)), 1)
⎛ _______ ⎞
⎜ ╱ 3 ⎟
⎜ ╱ x ⎟
⎜ ╱ ───── , 1⎟
⎝╲╱ x + 1 ⎠
i get this:
>>> (sympy.sqrt(x**3/(x+1)), 1)
n ------- n
n n 3 n
n n x n
n n ───── , 1n
nnnn x + 1 n
infact it seems to just use the n
character whenever it can't display a unicode character.
i'm running xterm from an ~/.xinitrc
file and setting some fonts and colors for the terminal in ~/.Xresources
. here is all the relevant information i could think of:
$ uname -a
Linux mypcname 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
$ xterm -version
XTerm(278)
$ cat ~/.xinitrc
#!/bin/bash
#update the xterm colors, font size, etc
[[ -f ~/.Xresources ]] && xrdb -merge ~/.Xresources
# run the window manager in the background first
metacity &
# get the window manager process id
wm_pid=$!
# wait a little while for the window manager to load (extend this if the xterm is not being properly maximised)
sleep 2
# run the xterm in fullscreen
#xterm +u8 -js -fullscreen &
xterm -en en_AU.UTF-8 -js -fullscreen &
# do not let the window manager become a zombie
wait $wm_pid
# this would run xterm first, then the window manager. doesn't maximise properly the first time startx is run
#xterm -fullscreen &
#exec mutter
$ cat ~/.Xresources
! see man xterm under the resources heading for explanations
! run xrdb -merge ~/.Xresources
after altering this file
! run xrdb -query -all
to see the current settings
xterm.vt100.faceName: Terminus
xterm.vt100.faceSize: 14
! do not display bold fonts in bold
xterm.vt100.AllowBoldFonts: false
! display bold fonts in a different color to make them stand out
xterm.vt100.colorBDMode: true
! use green as the bold color (same as in ~/.bashrc)
xterm.vt100.colorBD: #98E34D
! cols x lines ... update with values from $(echo $COLUMNS) and $(echo $LINES)
xterm.vt100.geometry: 126x52
! dark green foreground (same as in ~/.bashrc)
*foreground: #4E9A06
! black background
*background: #000000
! scroll quickly
xterm*fastScroll: true
! enable utf-8 encoding
xterm*locale: true
xterm*utf8: 1
! flash the current line instead of making the bell sound
*visualBell: true
*visualBellLine: true
! black
*color0: #2E3436
! darkred
*color1: #CC0000
! dark green
*color2: #4E9A06
! brown
*color3: #C4A000
! darkblue
*color4: #3465A4
! darkmagenta
*color5: #75507B
! darkcyan
*color6: #06989A
! lightgrey
*color7: #D3D7CF
! darkgrey
*color8: #555753
! red
*color9: #EF2929
! green
*colorA: #8AE234
! yellow
*colorB: #FCE94F
! blue
*colorC: #729FCF
! magenta
*colorD: #AD7FA8
! cyan
*colorE: #34E2E2
! white
*colorF: #EEEEEC
$ tail -10 .bashrc
PATH=/usr/local/bin:/usr/bin:/bin:/sbin
export LC_ALL=en_AU.UTF-8
export LANG=en_AU.UTF-8
export LANGUAGE=en_AU.UTF-8
# final logon actions:
# go straight to x on login. only do this for tty1 so that we can still use the other tty consoles without starting x. also only do this when there is not already a display, otherwise the xterm will try and do this after x starts aswell
[[ -z $DISPLAY ]] && [[ $(tty) = /dev/tty1 ]] && startx
$ locale
LANG=en_AU.UTF-8
LANGUAGE=en_AU.UTF-8
LC_CTYPE="en_AU.UTF-8"
LC_NUMERIC="en_AU.UTF-8"
LC_TIME="en_AU.UTF-8"
LC_COLLATE="en_AU.UTF-8"
LC_MONETARY="en_AU.UTF-8"
LC_MESSAGES="en_AU.UTF-8"
LC_PAPER="en_AU.UTF-8"
LC_NAME="en_AU.UTF-8"
LC_ADDRESS="en_AU.UTF-8"
LC_TELEPHONE="en_AU.UTF-8"
LC_MEASUREMENT="en_AU.UTF-8"
LC_IDENTIFICATION="en_AU.UTF-8"
LC_ALL=en_AU.UTF-8
$ printenv XTERM_LOCALE
en_AU.UTF-8
$ xrdb -query -all
*background: #000000
*color0: #2E3436
*color1: #CC0000
*color2: #4E9A06
*color3: #C4A000
*color4: #3465A4
*color5: #75507B
*color6: #06989A
*color7: #D3D7CF
*color8: #555753
*color9: #EF2929
*colorA: #8AE234
*colorB: #FCE94F
*colorC: #729FCF
*colorD: #AD7FA8
*colorE: #34E2E2
*colorF: #EEEEEC
*foreground: #4E9A06
*visualBell: true
*visualBellLine: true
xterm*fastScroll: true
xterm*locale: true
xterm*utf8: 1
xterm.vt100.AllowBoldFonts: false
xterm.vt100.colorBD: #98E34D
xterm.vt100.colorBDMode: true
xterm.vt100.faceName: Terminus
xterm.vt100.faceSize: 14
xterm.vt100.geometry: 126x52
**how can i get utf-8 working to display greek symbols in vim and equations in sympy
?**
***
extra information requested
$ echo $TERM
xterm
$ appres XTerm
*form.Thickness: 0
*tekMenu*tekreset*Label: RESET
*tekMenu*tektext2*Label: #2 Size Characters
*tekMenu*tekhide*Label: Hide Tek Window
*tekMenu*tekcopy*Label: COPY
*tekMenu*tektext3*Label: #3 Size Characters
*tekMenu*vtshow*Label: Show VT Window
*tekMenu*tektextsmall*Label: Small Characters
*tekMenu*vtmode*Label: Switch to VT Mode
*tekMenu*tektextlarge*Label: Large Characters
*tekMenu*tekpage*Label: PAGE
*tekMenu.Label: Tek Options
*mainMenu*redraw*Label: Redraw Window
*mainMenu*sunKeyboard*Label: VT220 Keyboard
*mainMenu*terminate*Label: Send TERM Signal
*mainMenu*backarrow key*Label: Backarrow Key (BS/DEL)
*mainMenu*logging*Label: Log to File
*mainMenu*hpFunctionKeys*Label: HP Function-Keys
*mainMenu*kill*Label: Send KILL Signal
*mainMenu*num-lock*Label: Alt/NumLock Modifiers
*mainMenu*print-immediate*Label: Print-All Immediately
*mainMenu*scoFunctionKeys*Label: SCO Function-Keys
*mainMenu*quit*Label: Quit
*mainMenu*alt-esc*Label: Alt Sends Escape
*mainMenu*print-on-error*Label: Print-All on Error
*mainMenu*tcapFunctionKeys*Label: Termcap Function-Keys
*mainMenu*meta-esc*Label: Meta Sends Escape
*mainMenu*toolbar*Label: Toolbar
*mainMenu*print*Label: Print Window
*mainMenu*suspend*Label: Send STOP Signal
*mainMenu*delete-is-del*Label: Delete is DEL
*mainMenu*print-redir*Label: Redirect to Printer
*mainMenu*fullscreen*Label: Full Screen
*mainMenu*continue*Label: Send CONT Signal
*mainMenu*oldFunctionKeys*Label: Old Function-Keys
*mainMenu*securekbd*Label: Secure Keyboard
*mainMenu*interrupt*Label: Send INT Signal
*mainMenu*8-bit control*Label: 8-Bit Controls
*mainMenu*allowsends*Label: Allow SendEvents
*mainMenu*sunFunctionKeys*Label: Sun Function-Keys
*mainMenu*hangup*Label: Send HUP Signal
*mainMenu.Label: Main Options
*VT100.utf8Fonts.font4: -misc-fixed-medium-r-normal--13-120-75-75-c-80-iso10646-1
*VT100.utf8Fonts.font2: -misc-fixed-medium-r-normal--8-80-75-75-c-50-iso10646-1
*VT100.utf8Fonts.font6: -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
*VT100.utf8Fonts.font5: -misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1
*VT100.utf8Fonts.font3: -misc-fixed-medium-r-normal--14-130-75-75-c-70-iso10646-1
*VT100.utf8Fonts.font: -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1
*VT100.font4: 7x13
*VT100.font2: 5x7
*VT100.font6: 10x20
*VT100.font5: 9x15
*VT100.font3: 6x10
*VT100.font1: nil2
*vtMenu*selectToClipboard*Label: Select to Clipboard
*vtMenu*reversewrap*Label: Enable Reverse Wraparound
*vtMenu*softreset*Label: Do Soft Reset
*vtMenu*cursesemul*Label: Enable Curses Emulation
*vtMenu*autolinefeed*Label: Enable Auto Linefeed
*vtMenu*hardreset*Label: Do Full Reset
*vtMenu*visualbell*Label: Enable Visual Bell
*vtMenu*appcursor*Label: Enable Application Cursor Keys
*vtMenu*clearsavedlines*Label: Reset and Clear Saved Lines
*vtMenu*bellIsUrgent*Label: Enable Bell Urgency
*vtMenu*appkeypad*Label: Enable Application Keypad
*vtMenu*tekshow*Label: Show Tek Window
*vtMenu*poponbell*Label: Enable Pop on Bell
*vtMenu*scrollbar*Label: Enable Scrollbar
*vtMenu*scrollkey*Label: Scroll to Bottom on Key Press
*vtMenu*tekmode*Label: Switch to Tek Mode
*vtMenu*scrollttyoutput*Label: Scroll to Bottom on Tty Output
*vtMenu*jumpscroll*Label: Enable Jump Scroll
*vtMenu*cursorblink*Label: Enable Blinking Cursor
*vtMenu*vthide*Label: Hide VT Window
*vtMenu*allow132*Label: Allow 80/132 Column Switching
*vtMenu*reversevideo*Label: Enable Reverse Video
*vtMenu*titeInhibit*Label: Enable Alternate Screen Switching
*vtMenu*altscreen*Label: Show Alternate Screen
*vtMenu*keepSelection*Label: Keep Selection
*vtMenu*autowrap*Label: Enable Auto Wraparound
*vtMenu*activeicon*Label: Enable Active Icon
*vtMenu.Label: VT Options
*SimpleMenu*menuLabel.font: -adobe-helvetica-bold-r-normal--*-120-*-*-*-*-iso8859-*
*SimpleMenu*menuLabel.vertSpace: 100
*SimpleMenu*Sme.height: 16
*SimpleMenu*BackingStore: NotUseful
*SimpleMenu*HorizontalMargins: 16
*SimpleMenu*Cursor: left_ptr
*SimpleMenu*borderWidth: 2
*menubar.borderWidth: 0
*tek4014*fontLarge: 9x15
*tek4014*font2: 8x13
*tek4014*font3: 6x13
*tek4014*fontSmall: 6x10
*MenuButton*borderWidth: 0
*fontMenu*render-font*Label: TrueType Fonts
*fontMenu*fontdefault*Label: Default
*fontMenu*font6*Label: Huge
*fontMenu*allow-window-ops*Label: Allow Window Ops
*fontMenu*utf8-mode*Label: UTF-8 Encoding
*fontMenu*font1*Label: Unreadable
*fontMenu*fontescape*Label: Escape Sequence
*fontMenu*utf8-fonts*Label: UTF-8 Fonts
*fontMenu*fontsel*Label: Selection
*fontMenu*allow-bold-fonts*Label: Bold Fonts
*fontMenu*utf8-title*Label: UTF-8 Titles
*fontMenu*font-linedrawing*Label: Line-Drawing Characters
*fontMenu*font2*Label: Tiny
*fontMenu*allow-color-ops*Label: Allow Color Ops
*fontMenu*font-doublesize*Label: Doublesized Characters
*fontMenu*font3*Label: Small
*fontMenu*allow-font-ops*Label: Allow Font Ops
*fontMenu*font-loadable*Label: VT220 Soft Fonts
*fontMenu*font4*Label: Medium
*fontMenu*allow-tcap-ops*Label: Allow Termcap Ops
*fontMenu*font-packed*Label: Packed Font
*fontMenu*font5*Label: Large
*fontMenu*allow-title-ops*Label: Allow Title Ops
*fontMenu.Label: VT Fonts
*colorD: #AD7FA8
*color5: #75507B
*backarrowKeyIsErase: true
*colorE: #34E2E2
*color6: #06989A
*ptyInitialErase: true
*colorF: #EEEEEC
*background: #000000
*color7: #D3D7CF
*saveLines: 1024
*color8: #555753
*color0: #2E3436
*foreground: #4E9A06
*IconFont: nil2
*color9: #EF2929
*color1: #CC0000
*visualBell: true
*colorA: #8AE234
*color2: #4E9A06
*visualBellLine: true
*colorB: #FCE94F
*color3: #C4A000
*colorC: #729FCF
*color4: #3465A4
$ xterm -u8 -fa "DejaVu Sans Mono"
# the following is typed in the resulting terminal:
$ echo -e "\xE2\x98\xA0"
n
# however when i copy the result from echo -e "\xE2\x98\xA0"
# into my browser, i get this: ☠ (a skull) but it does not show
# up as a skull in my xterm
$ lsof -p $PPID | grep fonts
xterm 5990 me mem REG 254,1 4971 13501810 /usr/share/fonts/X11/misc/ter-u18b_iso-8859-1.pcf.gz
xterm 5990 me mem REG 254,1 4897 13505403 /usr/share/fonts/X11/misc/ter-u18n_iso-8859-1.pcf.gz
i also ran $ fc-list
but the output was too large to paste into this question. so i have put it here
what it shows in my browser:
/usr/share/fonts/truetype/freefont/FreeSansBold.ttf: FreeSans:style=Bold,получерен,negreta,tučné,fed,Fett,Έντονα,Negrita,Lihavoitu,Gras,Félkövér,Grassetto,Vet,Halvfet,Pogrubiony,Negrito,gros,Полужирный,Fet,Kalın,huruf tebal,жирний,Krepko,treknraksts,pusjuodis,đậm,Lodia,धृष्ट
what i see in my terminal:
/usr/share/fonts/truetype/freefont/FreeSansBold.ttf: FreeSans:style=Bold,nnnnnnnnn,negreta,tunné,fed,Fett,nnnnnn,Negrita,Lihavoitu,Gras,Félkövér,Grassetto,Vet,Halvfet,Pogrubiony,Negrito,gros,nnnnnnnnnn,Fet,Kalın,huruf tebal,nnnnnn,Krepko,treknraksts,pusjuodis,nậm,Lodia,nnn
interestingly, some "special" characters do show up in my terminal, but most are relaced by n
. you can see in the previous output that none of получерен
can be displayed, but the final character of tučné
can be displayed (while the middle č
cannot - it is replaced by n
)
***
as per @apaul's comments it seems that xterm isn't loading the right font. try to set a dummy class so it doesn't load the xterm resources:
$ xterm -class Foo -name foo -u8 -fa "DejaVu Sans Mono:style=Book"
$ # the following commands are all executed in the resulting terminal:
$ echo -e "\xE2\x98\xA0"
☠
$ # the above skull actually shows up now. and so does the unicode
$ # output from sympy and also vi can display greek symbols now :)
all that remains is to figure out why xterm cannot set the font using ~/.Xresoureces
, and to get this working. it seems like something must be overriding the font settings?
actually i just thought to try above command with the terminus font, and it seems that this is the problem:
$ xterm -class Foo -name foo -u8 -fa "Terminus"
$ # the following commands are all executed in the resulting terminal:
$ echo -e "\xE2\x98\xA0"
n
maybe terminus is not properly installed? or is being mapped to something else. how could i find that out?
mulllhausen
(2751 rep)
Apr 14, 2015, 01:21 PM
• Last activity: Dec 16, 2024, 11:37 AM
2
votes
2
answers
217
views
Vim over SSH problem when connecting from a RHEL 8 to a remote macOS Sonoma
When I connect to a remote macOS Sonoma from a Linux RHEL 8 with `ssh -J user@portal user@mac` and, once connected, I run `vim somefile`, I get some extraneous characters at the top-left of the "page" and also at the shell prompt after exiting Vim: ESC `[>4;m` **note:** Thanks to @LorinczyZsigmond t...
When I connect to a remote macOS Sonoma from a Linux RHEL 8 with
ssh -J user@portal user@mac
and, once connected, I run vim somefile
, I get some extraneous characters at the top-left of the "page" and also at the shell prompt after exiting Vim:
ESC[>4;m
**note:** Thanks to @LorinczyZsigmond tip of using script
I managed to capture those bytes
It's not the first time I'm experiencing this problem, with differents local/remote OS combinations (Solaris/FreeBSD/AIX/Linux/macOS), but previously I only had to install the terminfo
packages on the remote NIXes to fix it.
On macOS Sonoma though, the terminfo for the xterm-256color
used by RHEL 8 is already in /usr/share/terminfo/78/xterm-256color
, and changing TERM
to xterm
doesn't help.
Any thoughts on what to do to fix the problem?
Fravadona
(1581 rep)
Dec 7, 2024, 11:46 AM
• Last activity: Dec 11, 2024, 06:47 AM
-1
votes
2
answers
86
views
Does this exist: xterm bash in frame window custom?
Is there a style to [xterm + bash scripts, commands] inside a custom frame? i will wish this style, see example: ╭─────────────────────────┤text title1├────────────────────────╮ │ │ │text, command, script, if else, echo, cat, sed, any command │ ├──────────────────────────────────────────────────────...
Is there a style to [xterm + bash scripts, commands] inside a custom frame?
i will wish this style, see example:
╭─────────────────────────┤text title1├────────────────────────╮
│ │
│text, command, script, if else, echo, cat, sed, any command │
├──────────────────────────────────────────────────────────────┤
│text, command, script, if else, echo, ca t, sed, any command │
│text, command, script, if else, echo, cat , sed, any command │
│text, command, script, if else, echo, cat, sed, any command │
├──────────────────────────────────────────────────────────────┤
├─────────────────────────┤text title2├────────────────────────┤
│text, command, script, if else, echo, cat, sed, any command │
╰──────────────────────────────────────────────────────────────╯
font: Monospace
Manuel songokuh
(1 rep)
Nov 23, 2024, 09:40 AM
• Last activity: Nov 23, 2024, 04:31 PM
1
votes
0
answers
18
views
Is it possible to instruct XTerm to use two specific weights for the regular font and the bold faces?
[![semibold, regular][1]][1] Yellow XTerm from `xterm -fa 'Cascadia SemiBold'` Pink XTerm from `xterm -fa Cascadia` As you can see, when I use Cascadia SemiBold the text is slightly heavier but the headers are rendered with the same weight, while in the other XTerm, using plain Cascadia, the headers...
![semibold, regular ][1]
Yellow XTerm from
xterm -fa 'Cascadia SemiBold'
Pink XTerm from xterm -fa Cascadia
As you can see, when I use Cascadia SemiBold the text is slightly heavier but the headers are rendered with the same weight, while in the other XTerm, using plain Cascadia, the headers are rendered with, I think so because it's heavier than Semibold, Cascadia Bold.
If it is possible to instruct XTerm to use two specific weights for the regular font and the bold faces, I was unable to find the solution in its man page.
Is it possible to instruct XTerm to use two specific weights for the regular font and the bold faces?
---
## Addendum
Pink is "regular" Cascadia, yellow is "Cascadia Code ExtraLight" and here XTerm was able to deduce a proper bold face. It's a little bit puzzling…
![regular, extra light ][2]
gboffi
(1376 rep)
Nov 13, 2024, 06:35 PM
• Last activity: Nov 14, 2024, 05:08 PM
0
votes
0
answers
31
views
plymouth + xterm + sudo: not work...why?
i create file sh, i click file sh will start to executive. but Xterm not work to run plymouthd... instead kdesu is worked to run plymouthd..but i want to use xterm.. maybe i missing something parameter.. this is KDESU **(works)** #!/bin/bash kdesu -c "sudo plymouthd; plymouth --show-splash; sleep 10...
i create file sh, i click file sh will start to executive. but Xterm not work to run plymouthd... instead kdesu is worked to run plymouthd..but i want to use xterm.. maybe i missing something parameter..
this is KDESU **(works)**
#!/bin/bash
kdesu -c "sudo plymouthd; plymouth --show-splash; sleep 10; plymouth quit"
this is xterm **(not work)**
#!/bin/bash
xterm -geometry 130x15 -fg Plum1 -bg Purple4 -fa 'Monospace' -fs 10 -e 'sudo plymouthd; plymouth --show-splash; sleep 10; plymouth quit'
I checked in google but nothing find..damn...
Manuel songokuh
(1 rep)
Nov 9, 2024, 12:18 PM
3
votes
2
answers
1950
views
How can I get the dimensions of the current font in a terminal?
I am working on an ncurses application that creates some very blocky graphics using alpha‐numeric characters. I’d like to be able to detect the dimensions (specifically the aspect ratio) of the font glyphs so that I can correct for it by changing how I render my graphics (such that a square always l...
I am working on an ncurses application that creates some very blocky graphics using alpha‐numeric characters. I’d like to be able to detect the dimensions (specifically the aspect ratio) of the font glyphs so that I can correct for it by changing how I render my graphics (such that a square always looks like a square).
I am able to use the
void getmaxyx(WINDOW *win, int y, int x);
function in ncurses to get the size of the screen/window in character cells, but since many windows can be freely resized, it is not reliable. Is there a similar function (or external mechanism) for retrieving the font dimensions?
ttyj
(31 rep)
Jan 30, 2022, 02:04 AM
• Last activity: Nov 8, 2024, 08:53 PM
0
votes
1
answers
122
views
Where are default fonts located
I am running Xterm and need to find the directory of the default bitmap font (misc-fixed). I have looked everywhere but still can't find it. Any ideas? Here's my output when I run ```xterm -report-fonts```: ``` Loaded VTFonts(default) fNorm: fixed all chars: no default char: 0 direction: 0 ascent: 1...
I am running Xterm and need to find the directory of the default bitmap font (misc-fixed). I have looked everywhere but still can't find it. Any ideas?
Here's my output when I run
-report-fonts
:
Loaded VTFonts(default)
fNorm: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fBold: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fWide: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fWBold: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
xterm: cannot load font "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1"
Loaded VTFonts(default)
fNorm: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fBold: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
descent: -10
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fWide: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
fWBold: fixed
all chars: no
default char: 0
direction: 0
ascent: 11
descent: 2
first char: 0
last char: 255
maximum-chars: 256
missing-chars: 33
present-chars: 223
min_byte1: 0
max_byte1: 0
properties: 22
min_bounds:
lbearing: 0
rbearing: 0
width: 6
ascent: -1
descent: -10
max_bounds:
lbearing: 2
rbearing: 6
width: 6
ascent: 11
descent: 2
Per-character: 222/255
...
I recently installed Arch with the i3-wm group package for context. Is it also possible the font is simply embedded inside a binary since I didn't explicitly install any fonts?
Would love any insight!!
Kyle
(3 rep)
Oct 22, 2024, 03:54 AM
• Last activity: Oct 22, 2024, 04:37 AM
25
votes
3
answers
5570
views
Is it still unsafe to cat an arbitrary file?
I read [this][1] post today and the answers claimed that certain escape sequences could be dangerous in some terminals, [this][2] post also has people saying that it can even be unsafe to simply view log files. Note the word "view" there, ever since I started using GNU/Linux I've always thought of c...
I read this post today and the answers claimed that certain escape sequences could be dangerous in some terminals, this post also has people saying that it can even be unsafe to simply view log files. Note the word "view" there, ever since I started using GNU/Linux I've always thought of cat as a way to view text files, but the more I read about it, the more I see that cat shouldn't be used for that at all.
My questions are: are these answers still true today? Have there been many patches to secure terminals? Should I be afraid of running applications over an ssh connection because they can infect the terminal I'm viewing them on?
user9503
(379 rep)
Jul 27, 2024, 10:07 PM
• Last activity: Jul 30, 2024, 07:16 AM
1
votes
0
answers
83
views
-fa 'Cascadia Code' → "xterm: no absolute path found for shell"
I have recently installed Cascadia Code (because I love its "4") and **I can use it in XTerm** $ xrdb -merge XTerm*faceName: Cascadia Code ^D $ **but**, otoh, if I try using the command line $ xterm -fa 'Cascadia Code' $ xterm: No absolute path found for shell: Code (above, the error message is prin...
I have recently installed Cascadia Code (because I love its "4") and **I can use it in XTerm**
$ xrdb -merge
XTerm*faceName: Cascadia Code
^D
$
**but**, otoh, if I try using the command line
$ xterm -fa 'Cascadia Code'
$ xterm: No absolute path found for shell: Code
(above, the error message is printed after the prompt!).
I know the Unix SE Q&A https://unix.stackexchange.com/questions/269351/xterm-no-absolute-path-found-for-shell , and I can understand the error message except that XTerm shouldn't look at
Code
in isolation.
What I'm missing?
---
As a follow up to a now deleted comment (ty Chris Davies) I tried xterm -fa 'Cascadia\ Code'
, xterm -fa 'Cascadia\\ Code'
, xterm -fa 'Cascadia\\\ Code'
, xterm -fa 'Cascadia\\\\ Code'
to finally realize that any number of backslashes, it doesn't matter.
---
I'm on Suse Tumbleweed,
$ xterm -v
$ XTerm(389)
(also here the message is printed after the next prompt).
Here it is the output of fc-list
:
$ fc-list 'Cascadia Code'
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-Italic.otf: Cascadia Code:style=Italic
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-SemiBoldItalic.otf: Cascadia Code,Cascadia Code SemiBold:style=SemiBold Italic,Italic
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-LightItalic.otf: Cascadia Code,Cascadia Code Light:style=Light Italic,Italic
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-SemiBold.otf: Cascadia Code,Cascadia Code SemiBold:style=SemiBold,Regular
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-SemiLight.otf: Cascadia Code,Cascadia Code SemiLight:style=SemiLight,Regular
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-Light.otf: Cascadia Code,Cascadia Code Light:style=Light,Regular
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-ExtraLight.otf: Cascadia Code,Cascadia Code ExtraLight:style=ExtraLight,Regular
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-ExtraLightItalic.otf: Cascadia Code,Cascadia Code ExtraLight:style=ExtraLight Italic,Italic
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-Bold.otf: Cascadia Code:style=Bold
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-BoldItalic.otf: Cascadia Code:style=Bold Italic
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-Regular.otf: Cascadia Code:style=Regular
/usr/share/fonts/texlive-cascadia-code/CascadiaCode-SemiLightItalic.otf: Cascadia Code,Cascadia Code SemiLight:style=SemiLight Italic,Italic
$
gboffi
(1376 rep)
Jun 24, 2024, 03:00 PM
• Last activity: Jun 24, 2024, 05:17 PM
2
votes
1
answers
204
views
less command stops working after setting terminal title in .tcshrc
After I add the following command to my `~/.tcshrc`: echo "\033]0;${PROJECT_NAME}\007" The `less` command in a new `gnome-terminal` stops working properly. But `more` command is not affected. This is what I see when trying to run `less` command: less log ESC]0;MYPROJ^G log (END)
After I add the following command to my
~/.tcshrc
:
echo "\033]0;${PROJECT_NAME}\007"
The less
command in a new gnome-terminal
stops working properly.
But more
command is not affected.
This is what I see when trying to run less
command:
less log
ESC]0;MYPROJ^G
log (END)
Roman Kaganovich
(171 rep)
Jan 30, 2018, 08:23 AM
• Last activity: Jun 18, 2024, 04:05 PM
27
votes
9
answers
48665
views
How can I find the default (font) resource XTerm is using?
If I launch `xterm` with its default bitmap fonts and then select the 'Large' font from the 'VT Fonts' menu (via `ctrl+right mouse`), I get a very usable bitmap font with apparently good Japanese character support. **I'd like to know what this font is** so that I can use it elsewhere. Unfortunately,...
If I launch
xterm
with its default bitmap fonts and then select the 'Large' font from the 'VT Fonts' menu (via ctrl+right mouse
), I get a very usable bitmap font with apparently good Japanese character support.
**I'd like to know what this font is** so that I can use it elsewhere. Unfortunately, I've found no information on what default settings XTerm uses (i.e. when none are explicitly specified). Lots of sites show how to use X resources to specify new settings (e.g. particular fonts), but none I've seen say what defaults are used if I do nothing.
I've tried eyeballing the font, and it looks similar to and is the same width as 9x15
, but it uses more vertical space. It appears not to be 9x15
with different line spacing, though, as specifying this font directly fails to display some Japanese characters that 'Large' can handle just fine.
Although I'll be happy to know what this specific font is, I really want to know where to find **what defaults XTerm uses for its resources** more generally. If it makes any difference, I'm running Ubuntu 12.04 LTS, 64-bit.
[I have seen [this question](https://unix.stackexchange.com/q/35748/5602) on the subject already, which is why I'm specifically asking about defaults rather than trying to get live values from a running XTerm.]
Paul Whittaker
(373 rep)
Oct 21, 2013, 12:39 PM
• Last activity: May 9, 2024, 11:44 AM
Showing page 1 of 20 total questions