[SOLVED] xterm is being terrible customized in -current
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It's not new, it's been around a while, but it's set to false in the app-defaults file that I use and which Pat adopted in current.
You can actually switch between bitmap and ttf fonts by holding down ctrl and right clicking: there's a truetype option about half way down the menu that pops up.
RE: .Xdefaults vs .Xresources. It varies with Distro.
Back before X11R5 (or possibly 4), there was the app-defaults file for the app, and then the user's ~/.Xdefaults. The applications would read that file directly from the local disk when it ran: usually during the libXt initialisation routines. Then with R5 someone had the idea that it'd be cool to store the resources in the XServer itself so that they could be accessed from any host that uses the display server (remember that X is network transparent so an Xserver can be shared), and xrdb and the RESOURCE_MANAGER string was invented.
What confused things is that some UNIX vendors/linux distro's chose to invent a new file from which the xrdb resources were to be loaded into the Xserver: ~/.Xresources, while others just decided to repurpose ~/.Xdefaults and load that into the Xserver. ¹
For compatibility, apps should fallback to directly reading the resources from ~/.Xdefaults on disk, but should only do so if there is no xrdb RESOURCE_MANAGER string present in the Xserver.
Which of these two approaches is more correct I'm not entirely sure, but that's the story behind the two files to the best of my understanding.
I believe Redhat still uses a .Xdefaults for this.
----
¹ alternatively, .Xresources came along later, but not everyone adopted it. Either way, we ended up with some using .Xdefaults, and some using .Xresources.
Not everyone has good eyesight and I find the new defaults comfortable, and 37 lines more than sufficient, and there's always shift-keypad-minus if you need more columns/lines, but feel free to change it however you want.
To obtain 61 lines per screen marks font to be unreadable in xterm menu. Which is evidently not correct cause in my setting green color font on black background they are quite comfortable to read. In default xterm settings to choose font to be unreadable has funny effect. Never figured out what is the purpose of this option except of course some fun. Now just came to my mind it can be useful in ascii art.
Thanks Gazl!
I did not know about the XTerm.VT100.renderfont thing. Is it a new option?
I appreciate GazL work cause one can spend life time on learning all possible settings xterm allows. It is just one of most complex terminal emulator. I never dare ventured too deep. Say: what is tektronic mode in xterm? But maybe I should be more honest and instead of whining sit down and provide myself some useful customization for xterm.
Edit: I have just upgraded xterm - but switching bold or or not makes no difference. Bold face looks exactly the same as non-bold. I just give up.
You can try the "upstream default" trick mentioned by PV on the previous page
or you can just use uxterm, the xterm wrapper for unicode environments instead
as I understand it's basically the same. I use that version normally since I
like the unicode support.
Xterm is one of the oldest X appliactions around and like almost all
open projects it has gotten it's fair share of 'creeping featuritis'
The amount of features this thing has is, well, overwhelming.
Reading the man page to solve a problem may end up consuming the
better part of your day.
If you would like to try uxterm, hese options should give you a nice
looking terminal with AA fonts:
! UXTerm*loginShell: true
UXTerm*faceName: Dejavu Sans Mono
UXTerm*faceSize: 9
! UXTerm*font: -*-terminus-*-*-*-*-22-*-*-*-*-*-*-*
UXTerm.saveLines: 4096
UXTerm*geometry: 80x40
! hacks to make alt-x and backarrow work
! with emacs in uxterm:
UXTerm*eightBitInput: false
! UXTerm.backarrowKeyIsErase: true
Edit: I have just upgraded xterm - but switching bold or or not makes no difference. Bold face looks exactly the same as non-bold. I just give up.
The "Bold Fonts" switch from Ctrl+Right_Click apparently does not force but allow bold font to be used (resource allowBoldFonts). Assuming the latest patch that changed the default font to terminus-medium, you can see the difference (only with bitmap fonts = "TrueType Fonts" unchecked!) e.g. in Midnight Commander (mc) or with
Code:
echo -e '\e[37;1mbold\e[0m'
When "Bold Fonts" is unchecked it's only brighter (color15 instead of color7 in the echo example), when checked it's really bold (and brighter).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.