Re: Readline initialization in .bash_profile -> Xquartz crash
Re: Readline initialization in .bash_profile -> Xquartz crash
- Subject: Re: Readline initialization in .bash_profile -> Xquartz crash
- From: Knut Arild Lisæter <email@hidden>
- Date: Tue, 19 Feb 2008 09:30:51 +0100
No custom .xinitrc here... Any other configuration files that could
be causing this?
I have the newest Xquartz, and the problem is still there.
--Knut
On Feb 18, 2008, at 8:28 PM, Jeremy Huddleston wrote:
Nope... it works fine for me.
Do you have a custom ~/.xinitrc? If so, can you please move it
aside and try again?
On Feb 18, 2008, at 02:33, Knut Arild Lisæter wrote:
Hi,
I've had some problems upgrading to the newest versions of Xquartz,
due to the presence of "readline" initialization in my
bash_profile. The offending command was
set bell-style visible
which caused Xquartz to crash with the error message :
xterm: fatal IO error 32 (Broken pipe) or KillClient on X server "/
tmp/launch-8C8kTO/:0"
and /var/log/system.log says:
xterm: bad command line option "xterm"
On my system this behaviour is consistent (adding the above command
in .bash_profile, quitting X11 and restarting with "xterm" in
terminal.app then Xquartz will crash). It would be nice if someone
else can confirm this as well - I have seen other people have had
similar problems, for instance: http://forums.macosxhints.com/showthread.php?p=445567
.
As I understand (now) the proper place for these commands are in
the ~/.inputrc file, but is it possible to avoid Xquartz crashing
like this? Or maybe add a tip to the FAQ?
I have attached the system.log output below
Best Regards,
Knut Liseter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden