It's possible for a given resource to be matched by multiple patterns. Few applications support this protocol, but Xterm is one of them. You can explore the resource tree of an application that supports the editres protocol with editres. For example xterm*background defines a background for absolutely everything inside the Xterm window. There are wildcards: ? means “any widget”, and * means “any widget sequence”.Other widgets include the menus mainMenu, fontMenu and vtMenu of class SimpleMenu. Xterm has a single widget of class VT100, called vt100, which is the terminal emulator part that covers the whole window. At the widget level, there can be multiple widgets with the same class, for example multiple buttons in the same window.For example sets a value of the geometry property for the vt100 widget of any instance of the XTerm class it applies to xterm -name foo but not to xterm -class Foo. Applications using the X toolkit support an option -class to set the class name, as well -name to set the instance name (which defaults to the base name of the executable). At the application level, the class name is usually fixed for a given application, typically to the capitalized application name, and sometimes other letters are also in uppercase, e.g.Conventionally, instance names start with a lowercase letter while class names start with a capital letter. You can use a class name instead of an instance name for any component. There are two ways to make a specification apply to multiple resources. Specifications of X resources can apply to a single resource or to a set of resources matching a pattern. Widgets can be nested, so there can be more than three components, or just two for a property of the application. The first component is the name of the application, the second component is a widget in that application, and the last component is a property of the widget.
Uxterm or xterm series#
X11 resources have a name which consists of a series of components separated by a dot, such as. Also, I somehow managed to completely screw up Xterm menues (Ctrl+mouse click) - they show up as a small yellow line. In fact it looks like : 160x40 takes precedence over other ones since that the instance I keep getting. 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.
Uxterm or xterm install#
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.
Uxterm or xterm how to#
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 kommentar(er)
