Uxterm change font size7/3/2023 ![]() However, when I manually change the settings, the freshly opened terminal recognizes font face & size settings: xterm -fa VeraMono -fs 12Īdditionally, this new terminal also recognizes the *dpi: 165 setting: fontSize 12 looks big. The font looks a bit like the default system tty's. ![]() Special characters like ~ look weird and font face & size do not get recognized. While *dpi for example is recognize by Firefox and other applications and the color configurations do work (background is black, foreground white. Xresources file looks like this: *dpi: 165 Depending on your fontconfig arrangement, you can get a workable coverage from the TrueType fonts (with the caveat that some of those are sized incorrectly).Echo $TERM replies xterm-256color and my. : 100000 Increase-decrease font size using Ctrl-/+ xtermVT100.Translations: override Ctrl minus: smaller-vt-font () n Ctrl plus: larger-vt-font () Sign up for free to join this conversation on GitHub.In xterm, it is treated as a nuisance (see menuLocale resource).īesides bitmap-fonts, xterm also supports TrueType fonts, and will automatically lookup fonts as needed to fill in for missing glyphs from the family specified with the -fa option. There is a font-set feature in the X libraries, but it has severe performance problems and was never widely used. XTermsaveLines: 5000 returns XTermsaveLines:: Too many arguments. I use VNC to access a server, which I think is CentOS/GNOME. typing the XTermsaveLines: 5000 and then merging your resources like so: xrdb -merge /.Xresources. Xterm uses only one of these bitmap-fonts at a time (along with automatically using bold- and italic-versions). The Arch Wiki mentions making a change in an xterm, i.e. ![]() Xresources so that if the default one doesn't have some unicode characters, the additional one can display them? While one could make font sets using bitmap fonts, which would allow one to do what's asked in the question:Ĭan I have an additional font in my. You can specify in your X resources which file to use by prefixing the resources with XTerm or UXTerm, respectively. If the locale does not use UTF-8 encoding, you are able to change these menu entries and see the resulting differences. If your locale uses UTF-8 encoding (and if the locale resource uses the default value), then xterm pre-selects these menu items and disables them from being changed. ![]() Xterm has menu items for UTF-8 Encoding and UTF-8 Fonts. The uxterm script selects the latter at startup using the -class option, but as described in the manual page, xterm will automatically select the utf8Fonts at startup based on the locale settings. There is more than one app-defaults file because that seemed a simpler solution than the utf8Fonts arrangement. But they have only 192 characters (256 - 64 control characters), while the bitmap UTF-8 fonts have thousands. ![]() Those short names are (as detailed in xterm cannot load font) aliases for ISO-8859-1 fonts, which (unsuprisingly given the history of UTF-8) have the same appearance as the UTF-8 fonts. Just reading the XTerm app-defaults file, most users would not notice that the non-UTF-8 fonts given here look something like the UTF-8 fonts: *VT100.font1: nil2 PS1: I have installed 100 DPI fonts for X. All changes in /.Xresources require you to do: xrdb /.Xresources to make them register in the current X session. You might also need to call the wrapper script uxterm instead of xterm for utf-8 to work properly in your terminal. Here is the content from the XTerm app-defaults file: *2: -misc-fixed-medium-r-normal-8-80-75-75-c-50-iso10646-1 PS2: Fontforge which also uses Xlib, uses a nice theme and normal font sizes. You use xtermutf8: 1 and choose iso10646-1 if you want utf-8. The app-defaults files XTerm and UXTerm have both of these, but in the latter, those Unicode fonts are not inside the utf8Fonts layer.
0 Comments
Leave a Reply. |