|
|
Set xterm dimensions using Apple's X11 terminal
Another way to set geometry (and other X defaults) is to create/modify your
.Xdefaults file in your home directory.
Add a line like: XTerm*geometry: 132x50
Set xterm dimensions using Apple's X11 terminal
Yes an .Xresources file is the way to go. That way if you type 'xterm &' in one xterm to get another one instead of using the menu, the new xterm will have the correct dimensions as well.
Just be sure that /usr/bin/cpp exists on your system. The .Xresources file is run through the preprocessor by default and this will not work if the preprocessor is not installed on your system. You need to install the BSD SDK from the DevTools in order to have /usr/bin/cpp on your system. Some other lines I have in my .Xresources are:
XTerm*saveLines: 50000
XTerm*rightScrollBar: true
You can do a 'man xterm' from the xterm to see all the resources you can set. This is generally true for all X11 apps as well, so if you want to set things for others, just add the appropriate resource settings in the .Xresource file. I made this post that explains some more about X11 resources. As a side note, if you are using xterm instead of Termial.app, you may like xman rather than man. Just do 'xman &' from the xterm and then you can search and browse man pages with mouse clicks and dialog boxes.
use .Xresources
I just noticed that your post told to use .Xdefaults. You should not do that anymore, it became obsolete with X11R5 if I recall correctly.
There is a difference between .Xdefaults and .Xresources. The .Xresources file is sourced when the X11 server starts (usually from an .xsession, but the system defaults do this even if you do not have a .xsession file in your home dir). The .Xdefaults are read whenever any X11 application starts. That is nice of course, but unfortunately the .Xdefaults file does not work any longer by default. With modern X11 servers the file that is sourced upon start-up of all X11 applications is now .Xdefaults-hostname instead.
The thing is that there is an environment variable
If you want your .Xresources file to take effect immediately without having to restart the X11 server, just do a I hope this comment helps and does not cause too much confusion.
use .Xresources
X11 with 10.3.2 uses .Xdefaults just fine.
use .Xresources
X11 with 10.3.2 uses .Xdefaults just fine. Did with 10.2.8 too.
Yes until you have an .Xresources file. (set-up that way for backwards comaptibility) If you have both then the settings in your .Xdefaults never take, because Xlib looks for .Xdefaults-hostname unless you set the XRESOURCES environment variable to point to .Xdefaults instead. Try it, then you will believe me. (Make sure that hostname is the full output of Because of all this wierdness, it is a good idea to just use the .Xresources file instead of .Xdefaults. This way if you ever create an .Xresources file, you will not wonder why your settings in .Xdefaults are not taking any longer. If you ever create your own .xsession, be sure to load the resources in the system xresources file and the .Xresources file in your home dir.
use .Xresources
Ok, I created a working .Xdefaults but I had a problem with the .Xresources file. I renamed the .Xdefaults to .Xresources after I saw that it was working. When I tried to open an xterm in X11.app with the command "xterm &", the window opened up without any of my settings.
use .Xresources
Do the following in your home dir.
use .Xresources
One more thing, do you have an .xinitrc file in your home dir? You should not. That is supposed to be used in cases where you use a command like startx to start the X11 server and your window manager. You might have such a file and it may not source your .Xresources file. In fact you might do this command in your home dir and post the output:
use .Xresources
Yep, that must be it. I have an .xinitrc file. I thought that this was needed for X11.app in order for it to use the quartz-wm window manager. This is what I have in that file: xterm &
Can I just remove the .xinitrc file or should I add in the xrdb command to "source" the .XResources file? Hmm, I just tried removing the .xinitrc file and now the .XResources file works fine. I think that I had added a .xinitrc file in order to start up with a formatted X11 window. I used to have this code in there before I changed over to having a .XResources file: xterm -rightbar -sb -sl 2000 -geometry 100x40 -bg black -fg white -fa Monaco -fs 11 &
use .Xresources
I am happy I was able to help. If you like what the default starts for you, then you have no need for an .xinitrc file. If you really wish to change it, you can try creating an .xsession file in your home dir. (.xsession is intended for something like xdm plus xsm while .xinitrc is intended for something like startx. startx or somehting similar would be a script that assumes a terminal and can prompt the user asking things like which window manager to start, this is not how X11 is started on MacOS X so the .xsession file makes more sense.) .xsession is a script that takes no args and it should begin on the first line:
It should be executable as well. It depends what the scripts on your system are like how it is started-up so to be safe on all systems you should always put the bourne shell shebang as the first line, make it executable, and assume that it is sourced by sh. On X11 by default is is started by part of a script that looks like this but these scripts do change from version to version:
# The startup script is not intended to have arguments. startup=$HOME/.xsession resources=$HOME/.Xresources if [ -s "$startup" ]; then if [ -x "$startup" ]; then exec "$startup" else exec /bin/sh "$startup" fi ... fi In your .xsession script you would like to have something like this:
resources=$HOME/.Xresources if [ -r "$resources" ]; then xrdb -load "$resources" fi You may like to do -merge instead in case you have created some Xresources under /etc/X* or /usr/X* that you like to use but by now people should be using app-defaults instead.
After this you could have some lines like you had in the parent comment. Alternatively you might just have it start xsm. Do a So as you can see there is a LOT of detail to making good .xsession/.xinitrc files. I had to do it in the past when I had a networked home directory and several machines that I would run X sessions on with some having more or less heads (monitors). I have not done any of this compicated scripting on MacOS X though, so I have no idea what sort of gotcha's you might run into. I would just avoid as much of this as possible. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|