X11 xterm settings

I have browsed through a number of the threads posted in this forum and haven't found an answer to my question. I'm affraid that it might be because it is too simple of a question.
I am not an avid UNIX user. I have learned pretty much only what I need in order to login to and run applications from a remote UNIX server. Buy the way, I think it's great that I don't need to by any third-party software to do this.
Anyway, all I would like to do is change the size and location of the default X11 xterm window. I did this once before a few of years ago when I first installed OS X. I've just recently whipped out my hard disk and upgraded to a fresh install of OS 10.4. Now I can't remember how to do this simple task.
Regards,
Jason

Jason,
Easy day - the answer has three components (assuming you don't want to mess with Xresources which can change the default values of xterm settings globally instead on the command line when calling xterm)
1) you need to supply arguments to xterm to make it get non-default settings. I use "xterm -geom 105x28 -sb -sl 2500 -bg khaki3 -fg black -cr white" and let the system position each window offset from the last.
2) When the X11 app starts, it runs your initialization file ~/.xinitrc or if it is not present, /etc/X11/xinit/xinitrc. If you want all users on the mac to get thechange then edit the line in /etc/X11/xinit/xinitrc. Otherwise, copy it to your home directory and make the change for your user only.
3) Optionally, you can customize the Applications menu for X11 to call xterm with the same commands as your xinitrc file (either global or specific to your user).
Since you asked about positioning, the geom parameter also takes an offset - try -geom 105x28+20-150
In either case, read up on the man pages man X and man xterm for details on what options do what for for all X11 window applications in general and xterm in specific. Once you are done playing and found the settings you prefer, make the changes in 2 and 3 as you prefer.
Cheers,
Mike

Similar Messages

X11 / xterm won't even launch anymore

I was using X11 with the minor glitches (i.e. cannot move x11 windows to secondary display). For some reason, x11 stopped working altogether today. I go to /Applications/Utilities/X11 and nothing happens.
I checked /var/log/system.log and it has the following errors:
Nov 5 22:04:20 initech [0x0-0x29029].org.x.X11_launcher[318]: command=/usr/X11/bin/xterm
Nov 5 22:04:20 initech com.apple.launchd[113] ([0x0-0x29029].org.x.X11_launcher[318]): Stray process with PGID equal to this dead job: PID 319 PPID 1 login
Nov 5 22:04:20 initech login[319]: USER_PROCESS: 319 tty??
Nov 5 22:04:20 initech login[319]: DEAD_PROCESS: 319 tty??
Nov 5 22:04:20 initech [0x0-0x29029].org.x.X11_launcher[0]: -xterm Xt error: Can't open display:
Nov 5 22:04:20 initech [0x0-0x29029].org.x.X11_launcher[0]: -xterm: DISPLAY is not set
Nov 5 22:04:20 initech [0x0-0x29029].org.x.X11_launcher[0]: Last login: Mon Nov 5 21:56:48 on ttys000
Coincidentally, X11 stopped working after I ran System Update to install the Quicktime and iTunes updates today.
Anyone else start having this problem?

I was checking the boards and found someone who said their org.x.X11.plist file was not being installed after they had deinstalled 10.5 X11, installed 10.4 X11, and went back to 10.5 X11.
I had did that earlier and wasn't having problems, but I went ahead and pulled that file from another 10.5 computer and copied that over to the affected Macbook.
Problem solved.

X11/xterm on 10.5.8 server broken?

I upgraded from my MacPro server from 10.4.11 to 10.5.8 recently. Since then, X11, or more precisely xterm, appear to be broken. When I click on the X11 app in the dock, it takes much longer to come up with a terminal than it did under 10.4. Furthermore, it does not show me any of the options in the top bar such as
Applications Edit Window Help
These option are now all gone with 10.5.8. This means that I can't open a second xterm. The xterm app bounces for a long time in the dock and I can see another app that has opened up called Xquartz. Usually, I can't quit xterm even by clicking on the right circle in the top left and have to 'force quit' it because it says that 'Application not responding'.
Any ideas as to what's going on?

Reinstalling X11 from scratch fixed the problem. Not sure what went wrong during initial install.

X11/xterm: can't launch from terminal in Tiger 10.4.11 PPC

[Copied over from another part of this forum (wrong place)]
I have set up my .profile PATH so that 'which' finds xterm via the terminal command line, but invoking 'xterm' gets the response:
xterm Xt error: Can't open display:
What do I need to configure so that the command 'xterm' starts X11 and opens an xterm window?
xterm runs fine from the drop down when I run X11.app
There are no DISPLAY options set anywhere.
Does this work in Tiger? (It does for me in Leopard and SL)
DN

Tiger will NOT auto launch X11 when you attempt to run an X-Windows based program.
Leopard and Snow Leopard will auto launch X11 when you attempt to run a X-Windows program.
You could change your .profile to
open -a X11 /usr/X11/bin/xterm

X11 Keyboard Settings Not Applied on Boot

I'm having problems setting my keyboard layout on boot in X11 using Xorg.conf.d. Specifically, I would like to set the default X keyboard to be Programmer Dvorak on boot with the caps:swapescape option on. I have followed the instructions on the Wiki for setting the default X keyboard; however, on boot the caps:swapescape option is applied but otherwise the layout is the standard US QWERTY layout. Setting the keyboard manually using the following command always works:
setxkbmap us -variant "dvp" -option "caps:swapescape
Here is the relevant Xorg.conf.d (10-keyboard.conf) file:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XkbLayout" "us"
Option "XkbVariant" "dvp"
Option "XkbOptions" "caps:swapescape"
EndSection
The other thing that is strange is that the output of setxkbmap doesn't change between boot (incorrect keymap) and when the keymap is set manually.
$ setxkbmap -query -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us
variant: dvp
options: caps:swapescape
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us(dvp)+inet(evdev)+capslock(swapescape)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us(dvp)+inet(evdev)+capslock(swapescape)" };
xkb_geometry { include "pc(pc104)" };
rules: evdev
model: evdev
layout: us
variant: dvp
options: caps:swapescape
Any pointers in the correct direction would be greatly appreciated.

I remember having had the same issue with Gnome which ignores the settings in Xorg.d completely. I would assume the same for Xfce although not for WMFS.
Does this help?
https://bbs.archlinux.org/viewtopic.php?id=154983

How to color file types in x11 xterm?

Hello,
How do I enable color typing files? What I mean is that when I do an ls by default a directory will have a different colors versus a file. Or the a .c file will have different color versus an executable file.
If this is possible, where can I make this setting possible?
Thanks!

If you want more flexibility in defining your directory colors, you can install the GNU coreutils and setup your own .dircolors file which gives you a huge amount of control over your ls filename coloring.
MacPorts <http://macports.org> is the easiest way to get the coreutils installed. Once you have the basic MacPorts installed on your system, you can use the following commands to install the coreutils:
sudo /opt/local/bin/port install coreutils
This will install gls and gdircolors in /opt/local/bin which you may want to add to your PATH environment variable, as well as create a shell alias for ls that points to gls
Assuming you use bash as your shell, then add the following to your .bash_profile (unless you are using .profile):
# Add MacPorts command directory to your PATH
export PATH="/opt/local/bin:$PATH"
# Create LS_COLORS environment variable from .dircolors
[[ -r $HOME/.dircolors ]] eval $(gdircolors -b $HOME/.dircolors)
and add the following to your .bashrc file:
# Create ls alias that uses the GNU coreutils gls --color command
alias ls='gls --color=auto'
To create your first $HOME/.dircolors file do the following:
gdircolors -p >$HOME/.dircolors
Edit this file to make the modifications you desire, such as adding custom colors for .h files. The comments in this initial file will tell you want numeric codes control the different background colors, forground colors, and color attributes:
# Attribute codes:
# 00=none 01=bold 04=underscore 05=blink 07=reverse 08=concealed
# Text color codes:
# 30=black 31=red 32=green 33=yellow 34=blue 35=magenta 36=cyan 37=white
# Background color codes:
# 40=black 41=red 42=green 43=yellow 44=blue 45=magenta 46=cyan 47=white
You can easily test your .dircolors changes doing (assumes /opt/local/bin is in your PATH )
nano .dircolors # edit .dircolors file
eval $(gdircolors -b $HOME/.dircolors)
ls # where this is the alias for gls --color=auto
# repeat until you have the settings you want

X11 environment variables on MacBook Pro

Hi
I have just got my new MacBook Pro and have installed Gimp to run using x11 that came on the apple installation disks however I can't seem to get the xterm to configure correctly.
GIMP is installed under /sw/bin but the default PATH for x11 does not include this location so I added PATH=$PATH:/sw/bin:/sw/sbin to a newly created .bash_profile. But x11 did not seem to use this file although terminal worked OK.
After doing a bit of research, I then created a .bashrc file with the PATH defined and changed the .bash_profile to source .bashrc with no other entries.
Again this worked OK for Terminal but now when I type 'echo $Path' in an x11 xterm the PATH displays two entries for /sw/bin & /sw/sbin. i.e.
$ echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/sw/bin:/sw/sbin:/sw/bin:/sw/sbin
Any ideas why? and how can I correct it?
Macbook Pro 17 Mac OS X (10.4.9)

Sorry this was a bit brief; I think I was still asleep when I typed it.
The reasons are these:
1. Many fink programs require environment variables and other settings. When you source that init.sh file, it ensures everything is set up to work out of the box. (Among the things it does is to in turn source every relevant file in /sw/etc/profile.d -- take a look in it to see what, if anything, is in there). There is also some code to keep your path trimmed properly, so you don't get repeats pasted on.
2. Bash is unique in that either .bashrc or .bash_profile, but not both, get sourced. In a rooted X11 environment, everything works properly, but on OS X, where X11 is "rootless," it leads to unexpected behavior like what you saw. As long as you put everything into one file and then tell the other one to source its contents, you should be ok.
You can also run X11 stuff from Apple's terminal, provided you somewhere in a startup file have something to set the DISPLAY variable, usually to .0.
I've put more discussion of these things here

How to turn off mouse (or touchpad) scrolling when running vim in an xterm?

Just updated 13" macbook pro (mid-2010) from Snow Leopard (10.6.8) to Yosemite (10.10.1). Previously, when running vim in an xterm, scrolling with the touchpad did nothing inside vim, it just scrolled the xterm history back so I could see what I had done before executing vim. Now, the same scrolling action (either with touchpad or with an external mouse with scrollwheel) moves the cursor position inside vim (if I'm in navigate mode). I want to turn this feature off. I'm sure some people like it but I do not. Anyone know whether this is something to be blocked by vim settings, or perhaps something in the xterm settings I need to change? Vim version is 7.3 (2010 Aug 15), which must be a slightly later version than I had under the original operating system, since I got it July 2010.
I've tried modifying various vim settings, but to no effect. I haven't found a comprehensive list of such settings to try systematically.

While I do not have Yosemite up and running at the moment, I cannot actually play with Yosemite Terminal.app. But you should at least look through the various Terminal -> Preferences to see if there is any configuration option that is telling the Terminal how to treat scroll operations. And try things like changing the "Declare terminal as: ............." setting, as that may affect the Terminfo database entry, which Vim uses to decide on what it does with various keyboard escape keys for input as well as displaying output (not sure if that would affect scrolling input, but it is worth a shot).
Instead of using X11 and xterm, consider giving iTerm a try. I have been using as my terminal emulator for years, and at work I live in terminal sessions, ssh'ed into various Linux, Solaris, AIX platforms.
<http://iterm2.com> A newer version
<http://iterm.sourceforge.net> an older but still viable version (I used this on my Snow Leopard 10.6.8 system)
iTerm will give you Tabbed windows just like Terminal (actually had Tabbed windows years before Terminal.app). It will allow you to define what a double-click selection thinks is a word. It has an option to automatically load anything selected into the copy/paste buffer.
NOTE: I have nothing against X11 and xterm. I also use X11 (XQuartz) all day as well as terminal sessions, with various Linux, Solaris, AIX X11 displays being sent back to my iMac at work, frequently using gvimdiff.

Xterm font problem (national characters)

Hello everyone!
I have the following problem...
I'm Slovene and the national characters (š, č, ž) work in the xterm by default, but when I change the fault, even to a line like "XTerm*font: -*-fixed-medium-r-normal-*-16-*-iso8859-2", which is identical to the default font, they stop working. They show up as a space. If I set the font to something like "XTerm*faceName: terminus:pixelsize=14", they show up as 'box' characters, but when I try to use something like Monospace, they work again.
How is it possible that the manual declaration of the -fixed- font does not work, when it's exactly like the default font if no special font is specified?
Thanks for the answers,
— Nanthiel

When I use Terminus, it shows the Š and š, Č and č, Ž and ž.
Try adding this line to your xterm settings to make sure xterm is UTF-8 compatible:
xterm*utf8: 2
I have no trouble using Terminus to show the Slovenian characters with locale set to 'en_US.utf8'.
Terminus is installed to ./usr/share/fonts/local/'. For Xorg to be fully aware of Terminus, your '/etc/X11/xorg.conf' must contain a section like this,
Section "Files"
FontPath "/usr/share/fonts/local"
EndSection
If you aren't using an 'xorg.conf' file, I think you can create one containing just those three lines. (I could be wrong). X has to be restarted for any changes in 'xorg.conf' to work.
After restarting, Terminus will show up when you run 'xfontsel'. Xfontsel is a small app that lets you display fonts and their names in the old Xorg format: "-*-terminus-medium-*-*-*-12-*-*-*-*-*-iso8859-2". The program won't show all the valid options, just some of them.
Now you should be able to load Terminus in xterm with
xterm*font: -*-terminus-medium-*-*-*-12-*-*-*-*-*-iso8859-2
Change the "12" to change the size of the font.
Or,
xterm*faceName: xft:Terminus:size=12:hinting=true
Again, change the "12" to change the size of the font.
I hope this helps you. I've learned much about xterm, and I now know that I prefer the font Inconsolata over Terminus.
Last edited by thisoldman (2009-12-01 22:59:47)

Using Mac Terminal window in combination with X11

I'm trying to log into a remote computer and bring up X11 applications
to display on my laptop, from within the Mac Terminal window. I
was able to get it to work on MacOSX10.3 by typing in
"export DISPLAY=:0.0" on the remote computer after logging in, but
the same trick isn't working on my MacOSX10.4 machine. I'm using
the "-Y" option to ssh on the 10.4 machine, following an earlier query
on that topic. If I do the ssh -Y from an X11 xterm, everything works fine.
Thanks,
Catherine

Set DISPLAY=:0.0 on the local shell (verify that 'xterm' brings up a local-machine window) before ssh'ing to the remote machine. When you use a local xterm, the DISPLAY is already set to the local screen by default (duh...xterm is an x11 thing:), but Terminal is not an x11 thing so you have to set DISPLAY manually. W11-forwarding works by having the remote machine's x11 come back to "wherever the local shell had its x11 directed".

[SOLVED] Xterm Japanese/Unicode Characters not displaying (??) instead

Hey,
So I'm new to linux and arch and I've made a point of reading every relevant thread posted when I searched for 'Japanese terminal' and I haven't been able to get my terminal to display Japanese characters. All I see are ?????.
This is my /etc/locale.config
LANG=en_CA.UTF-8
LC_COLLATE=C
This is the output from running:
$ locale
LANG=en_CA.UTF-8
LC_CTYPE="en_CA.UTF-8"
LC_NUMERIC=\"en_CA.UTF-8\"
LC_TIME=en_CA.UTF-8
LC_COLLATE=C
LC_MONETARY=\"en_CA.UTF-8\"
LC_MESSAGES=C
LC_PAPER=\"en_CA.UTF-8\"
LC_NAME=\"en_CA.UTF-8\"
LC_ADDRESS=\"en_CA.UTF-8\"
LC_TELEPHONE=\"en_CA.UTF-8\"
LC_MEASUREMENT=\"en_CA.UTF-8\"
LC_IDENTIFICATION=\"en_CA.UTF-8\"
LC_ALL=
This is the output from running:
$ locale -a
C
POSIX
en_CA.utf8
en_US.utf8
ja_JP.utf8
This is my ~/.Xresources file:
! Name
Xterm*termName: xterm-256color
! Font style
xterm*faceName: xft:monospace:size=11
xterm*faceNameDoublesize: xft:Droid Sans Japanese:style=Regular
xterm*utf8: 2
! Window size
xterm*VT100.geometry: 100x40
! No more bell
xterm*vbell: True
! Scrollback
xterm*savelines: 4096
! double-click to select whole URLs :D
xterm*charClass: 33:48,36-47:48,58-59:48,61:48,63-64:48,95:48,126:48
! Scrollbar
xterm*rightScrollBar: false
xterm*ScrollBar: false
! Foreground & background
*background:#293b3b
*foreground:#bf6e63
!terminal colours----------------------------------------------------------------------
!http://www.xcolors.net/dl/fishbone
!black
*color0:#293b3b
*color8:#344040
!red
*color5:#bf5357
*color13:#bf6367
!green
*color2:#41a551
*color10:#51a55f
!yellow
*color3:#aea64f
*color11:#aea75d
!blue
*color4:#416ea5
*color12:#5177a5
!magenta
*color1:#bf6053
*color09:#bf6e63
!cyan
*color6:#714da5
*color14:#7859a5
!white
*color7:#876868
*color15:#876f6f
Also, when I trying inputting text into xterm using ibus's anthy, nothing gets entered, and I'm assuming that is related to the problem of not being able to view the Japanese characters properly
I'm really not sure where I'm going wrong, but it's driving me nuts and any help would be greatly appreciated.
Last edited by Bipolarbearz (2014-12-24 03:24:40)

Your default xterm font is DejaVu Sans Mono. I don't know how scim and anthy may complicate setting up a locale but you do appear to have something oddly configured.
Your output from the bare locale command shows backslashed double quotes. My output shows no backslashes:
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE=C
LC_MONETARY="en_US.UTF-8"
-- snip --
LC_ALL=
The only line I have uncommented in /etc/locale.gen is:
en_US.UTF-8 UTF-8
The only possibly significant difference between your xterm settings and mine is the way we set xterm to use UTF-8. I have:
⁣ XTerm*locale: true
You have:
⁣ xterm*utf8: 2
I think they may just be different methods that reach the same end when you only have UTF-8 locales installed. I can get the Droid glyphs to display using either resource setting.
If I were in your shoes, I would work through the Archwiki's Locale page, step by step, to see if I could silence the warnings.
If the warnings still appeared, I would step back, and do things one step at a time. If you uninstall anthy, or scim-anthy, and regenerate your locales, do the warnings disappear? Does xterm display the CJK glyphs? If not, does regenerating the locales using only en_CA.UTF-8 work?
I wish I could offer more help but I don't have the knowledge to offer more.
If you want to see which installed fonts say they have Japanese language support, use this command:
fc-list ':lang=ja'
Do note that what a font advertises and what you and I would call language support may be different.

X11 and x11 apps not starting up

I've seen this question asked once before but didn't understand how to actually fix the problem from what I saw, so here it goes:
I installed X11 as an optional install from the DVD as you are supposed to do for system 10.4.3 but when I try starting up Gimp or Inkscape, X11 only starts up for a second before shutting down again. Here is the message that I see when I look at the console log:
XFree86 Version 4.4.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
[DRI] screen 0 installation complete
Screen 0 added: 1280x960 @ (0,0)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
/Users/"MYUSERID"/.xinitrc: /Users/"MYUSERID"/.xinitrc: is a directory
Quitting XDarwin...
What exactly am I supposed to do to get x11 working? Any help would be greatly appreciated.
Thanks!

I have 3 computers that I have recently updated to 10.4.4 all of them get the same error as described in the original post, but I do not have the ~/.xinitrc file at all...
I have even did a clean install of the OS on one of my computers and with a fresh install I get:
XFree86 Version 4.4.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
[DRI] screen 0 installation complete
Screen 0 added: 1024x768 @ (0,0)
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing from list!
X11 itself runs, small apps such as xeyes, xman, xlogo run, but I cannot run Eiffel 5.6 IDE. as I then get the error:
bash: no job control in this shell
when running the launch script for the X11 app.
I have seen these errors mentioned in various post regarding GIMP I have not seen a definitive answer, some are fixed by the answer in this post, others (including mine) are not.
On my freshly installed 10.4.4 I also removed the X11 Receipt and installed the X11User.pkg from the 10.4.3 installer DVD and still had error. I did not, however, remove the X11 software of components. (might try that next)
Also, this might be useful, I sometimes get this error when quitting the X11:
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server ".0"^M
Note: I had been using the X11 with Eiffel 5.6 Studio developer package with 10.4.3. Not sure when things stopped working as I have not used it since late November. Not sure if things stopped working after a Security Update, or the OS Update... any futher insights into this would be appreciated.
Regards,
JB
PBook 15 Al 1.25 Mac OS X (10.4.4)

X11 between Macs

Has anyone run X11 programs between 2 macs over ssh ? Say Xterm , clock , xeyes, etc. If so what options did you use to start the ssh (-X) ? And/or did you edit the sshd_config file or others ? I keep getting the 'can't open display' error.
Dennis

Also, it's probably a good idea to ssh into the remote system from an X11 xterm window. Terminal won't know your X11 display ID unless you set the DISPLAY variable, and if you've got more than one X11 session running at once (under different user accounts), it can be tricky to guess what the desired ID is.

X11 App Can't Display After Upgrade from 10.4.5 to 10.4.6

Hi there,
Could someone tell me how to sovle this problem from an X11 xterm:
CharlesMac:~ charles$ xterm -display localhost:0.0
xterm Xt error: Can't open display: localhost:0.0
It works for:
CharlesMac:~ charles$ xterm -display .0
I also got the same error msg from a Linux box too:
[charles@Fedora4 ~]$ xclock -display 192.168.1.3:0.0
Error: Can't open display: 192.168.1.3:0.0
I think it was working before I upgraded the OS from 10.4.5 to 10.4.6.
Thanks in advance for any help.
Cheers,
Charles

Welcome to Apple Discussions!
This sounds like something someone over at the Unix forum might be better equipped to answer:
http://discussions.apple.com/forum.jspa?forumID=735
While I do know some Unix, it has been a long time since I've played with xterm.

Cannot display x11 applications on server back to my mac running x11

Something has happened recently and I can no longer display x11 application windows running on a large SGI Server back to my mac. I am connecting via a x11 xterm window with ssh. Prior to logging onto the sgi, I add it to my xhost list with a xhost + command and get the return that the machine was being addd to the access control list. I then log onto the server with ssh or ssh -Y, set the env variable DISPLAY to my mac. I then try a simple xclock to display the clock, and get a "cannot open display display" error. IP's are correct, env variables are set right. 3 weeks ago I had no problems, but now I do. Unfortunately, I remember two security updates and 10.4.6 have been installed since I last used X11. Can anyone help?
Quad 1GHz G4 Mac OS X (10.4.6)

Hi pbuck,
   Ah, data; that helps! You don't have to delete all of those options. The one that disrupts connections made by setting the display on the remote machine is the nolisten_tcp option. If you set that to 0 or "no", your apps can connect directly to the window server on your machine via tcp.
   However, that doesn't apply to a secure shell tunnel. I don't know what happens between-the-sheets but maybe secure shell negotiates with XWindows directly because the above setting doesn't affect the ability to do window forward through a secure shell tunnel. Of course for that you have to have "X11Forwarding yes" in the sshd_config file on the server and you're supposed to have the "ForwardX11 yes" set in the ssh_config file on the client, although I've gotten by without the latter. After that, all you have to deal with is X11 itself, or more specifically, the X11 Security Extension.
   Newer versions of X11, such as the one that ships with Tiger, have an operative Security Extension. Thus, they have more stringent requirements of dangerous applications. I don't really know how to deal with it outside of SSH but again OpenSSH will handle the negotiation for you if you use the "-Y" option instead of the -X option.
Gary
~~~~
   I never thought that I'd see the day where Netscape is free
   software and X11 is proprietary. We live in interesting times.
         -- Matt Kimball <[email protected]>

X11 xterm settings

Similar Messages

Maybe you are looking for