Re: Odd X resources errors
Re: Odd X resources errors
- Subject: Re: Odd X resources errors
- From: Randy Ford <email@hidden>
- Date: Tue, 17 Jun 2003 03:42:53 -0500
On Monday, June 16, 2003, at 01:47 PM, Finn Smith wrote:
On Monday, June 16, 2003, at 01:02 PM, Randy Ford wrote:
On Monday, June 16, 2003, at 10:48 AM, Finn Smith wrote:
Hi all,
I've been having some very odd errors related to attempting to
customize my environment with an .Xresources file. I'm running X11
beta 3 with the developer SDK on Mac OS 10.2.6.
I've added some basic customizations to my ~/.Xresource file such as:
xterm*saveLines: 10000
xterm*scrollBar: true
xterm*rightScrollBar: true
xterm*jumpScroll: true
xterm*Background: black
xterm*Foreground: gray70
which I load in my ~/.xinitrc with the xrdb -merge command.
All seems to go well at startup except for the fact that none of my
customizations occur. Then, when I launch an xterm from a shell,
these errors are spit out to stderr.
Does "xrdb -query" show that the resources were loaded correctly?
What editor did you use? Could it be that the file was saved with the
wrong type of newlines? Maybe it has some character other than spaces
or tabs between the colons and parameters. This needs to be a
straight text file.
Everything appears to have loaded correctly when I check with the query
flag:
[Nessus:~] fcs% xrdb -query
xterm*Background: black
xterm*Foreground: gray70
xterm*jumpScroll: true
xterm*rightScrollBar: true
xterm*saveLines: 10000
xterm*scrollBar: true
I am using vim as my editor, and they are just plain ol' ascii text
files.
It still looks to me like the newlines aren't what is expected. Try
"od -xc .xinitrc" to see what they are. They should be just "\n"
("0a"). If they are "\r\n" ("0d0a"), they are in DOS format; If they
are "\r" ("0d"), they are in old Mac format. I suspect they are DOS
format. The "\r" is the carriage return character; on a printer, it
sends the carriage back to the beginning of the same line. Your error
messages are garbaled as follows:
" is not definedWarning: Color name "black
I suspect the actual message is something like what follows:
some text ......Warning: Color name "black\r" is not defined
You could send stderr to od to see what the output really is:
xterm 2>&1 | od -xc
Vim will look at the newlines and try to determine if it is a DOS, Mac,
or Unix file. Try ":set fileformat" in vim to see what vim thinks it
is. It should be unix. If it isn't, you can convert it in vim using
the following:
:set fileformat=unix
Then save the file.
randy.
_______________________________________________
x11-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/x11-users
X11 for Mac OS X FAQ: http://developer.apple.com/qa/qa2001/qa1232.html
Report issues, request features, feedback: http://developer.apple.com/bugreporter
Do not post admin requests to the list. They will be ignored.