This is why I added them so you can select entire group with xterm*on4Clicks and entire page with xterm*on5Clicks option. The xterm*on4Clicks and xterm*on5Clicks are not used by default while xterm*on2Clicks are predefined as word and xterm*on3Clicks as line values. You are of course encouraged to investigate the CHARACTER CLASSES section of the xterm(1) man page to read more on this topic. The setting above I use is based on 15 years of experience and seems to work best. Especially with double-clicking the text. The xterm*charClass defines which sets of characters should be treated the same when doing cut and paste. % fc-match consolas:boldĬonsolas-bold-italic.ttf: "Consolas" "Bold Italic" The answer to that question comes with fc-match(1) from fontconfig package. home/vermaden/.fonts/ubuntu-mono-italic.ttf home/vermaden/.fonts/ubuntu-mono-bold.ttf home/vermaden/.fonts/ubuntu-mono-bold-italic.ttf Many times after adding fonts to my system – and renaming them to my ‘standard’ which looks like that one below I was asking myself how to properly specify the variant I need. This advice is not limited to xterm(1) but its worth to mention it. ![]() I will not discuss all possible settings as they are well described in the xterm(1) man page but I will comment some more useful and interesting ones. : select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0) \n\Ĭtrl Shift C: copy-selection(CLIPBOARD) \n\Ĭtrl Shift V: insert-selection(CLIPBOARD) Xterm*iconHint: /home/vermaden/.icons/vermaden/xterm.xpm Alternatively some people use ~/.Xresources file. Selection Buffers and Keyboard Shortcutsįirst lest start with some reasonable configuration in the ~/.Xdefaults file.This is the Table of Contents for this article. That is why I will omit it in this article – but I mention it since its also nice terminal. Recently also sakura(1) got my attention – but it’s theming possibilities are even more limited then xterm(1) with themes/colors hardcoded directly into the source code. Unfortunately it has some issues with fonts rendering – making larger spaces between the lines and making fonts bigger for example – but as I also like bitmap fonts like CLEAN or FIXED – so I use bitmap fonts for urxvt(1). The other one that always got my attention was urxvt(1) terminal. I do not remember last time when I had to manage these archaic systems but the respect for xterm(1) remains. Mostly because of its good compatibility with all UNIX systems – especially the older ones like IBM AIX or HP-UX. I already once wrote about random xterm(1) themes in the FreeBSD Desktop – Part 12 – Configuration – Openbox part – but I really wanted to expand that topic and also include other terminals.Īfter trying many terminal emulators – some more bulky like Konsole/ GNOME Terminal/ XFCE Terminal/ MATE Terminal – some more lightweight like st (1)/ rox-term(1)/ eterm(1)/… – I always went back to the most old-school and basic one – good old xterm(1) terminal. You may want to check other articles in the FreeBSD Desktop series on the FreeBSD Desktop – Global Page where you will find links to all episodes of the series along with table of contents for each episode’s contents. This post will guide you through the needed steps to make that setup working. Since then I reworked that feature a little and also added random theme and background selection for urxvt(1) terminal. It doesn't display it properly whether I use DejaVu, Source Code Pro, Fira Mono Code, or any other font I've tried, I'm starting to think I need to go back to Termite or something.ĮDIT: I got it to properly show the characters for the Wuncon Siji font, so hopefully this doesn't cause any more problems in the future.Some time ago when I was mostly writing about Openbox setup I also showed how to setup xterm(1) so it will start with new random theme with each start. That being said, URxvt is still not properly displaying it, which is still a problem. I'm having trouble finding the codepoint, but it looks kinda like a T, except the bar on top is curved. For example, the "play button" that polybar uses via Wuncon Siji font shows up as a different symbol in other fonts. So basically, even if I can get it to display the right characters for this situation, it may be the wrong characters for others. If I use the command in the comment above, but substitute Wuncon Siji, it shows me a different character than with any other fonts. What I'm gathering from some other experimenting I've been doing is that Wuncon Siji, the font that polybar is using to display symbols, uses different symbols for the same codepoints as other fonts. I think I'm starting to see the problem here and I'm not sure if it's something I can fix.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |