So my guess is that one of these takes precedence over everything else? : 100x100 I did not think to look up what exactly xrdb -merge does which resulted in this mess. Result of appres XTerm xterm | grep geometry thanks to Gilles. or * it seems to only work with little xt. I can't do it now, but I might try to recompile the latest version to see if the issue is there.įollowing the suggestions by ILMostro_7 below I tried, which still did not work. apt-get update & apt-get install -only-upgrade xterm I tried upgrading xterm, but it is still 297. So, if that link is right, then yes, I am running different Xterm versions. I don't know how to tell Xterm version from Arch's repos, but maybe this: I don't have access to my Arch box at the moment, but it would be pretty up-to-date. Why is this the case? Does it maybe have something to do with new or old resources in X? Thanks! It baffles me that the config above works since it is syntactically off. I see examples with Xterm, xterm and XTerm online. X.org on xterm did not have any examples (searching for "xterm*" did not return anything on that page). Xresources to Ubuntu14 work box because parts of it stop working, and I get different setups after running: xrdb -merge. The same is true for URxvt terminal: I can't simply port my Arch. However, my Arch box runs on "xterm" fine. XTerm*scaleHeight: 1.3 ! <- but all others work with "XTerm" Xterm*VT100.geometry: 100x80 ! <- this line would not work with "Xterm" or "XTerm" However, I don't understand why sometimes configs work with Xterm and sometimes with xterm or XTerm (lower vs upper case x and t).įor example, I have this odd config that is working on Ubuntu: XTerm*faceName: terminus After starting to use Arch I switched to xterm and urxvt terminal and enjoyed the flexibility of them (esp.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |