On Tue, 22 Dec 2009 22:10:26 +
Jamie Griffin j...@koderize.com wrote:
On Tue, Dec 22, 2009 at 01:45:52PM -0800, Rem P Roberti wrote:
I think case matters here, i.e. XTerm*, not Xterm or xterm.
Exactly the problem. Thank you!
Curious, on my system (7.2) my ~/.Xdefaults uses
On Tue, Dec 22, 2009 at 10:10:26PM +, Jamie Griffin wrote:
On Tue, Dec 22, 2009 at 01:45:52PM -0800, Rem P Roberti wrote:
I think case matters here, i.e. XTerm*, not Xterm or xterm.
Exactly the problem. Thank you!
Curious, on my system (7.2) my ~/.Xdefaults uses lowercase 'xterm
On my desktop box I settled on an xterm font and font size by
experimenting thus:
xterm -fa 'Bitstream Vera Sans Mono' -fs 10
I went through a number of fonts until I settled on the one I liked
most. Then I created an .Xdefaults file in my home directory which
included:
Xterm*faceName
On Tue, Dec 22, 2009 at 09:38:19AM -0800, Rem P Roberti wrote:
rendered correctly, but I can't get X to read the .Xdefaults file.
ideas on why .Xdefauts works on the desktop box but not the laptop?
Could it be that you need to make sure your xterm is executing a login
shell when it starts
On 2009.12.22 18:03:00 +, Jamie Griffin wrote:
On Tue, Dec 22, 2009 at 09:38:19AM -0800, Rem P Roberti wrote:
rendered correctly, but I can't get X to read the .Xdefaults file.
ideas on why .Xdefauts works on the desktop box but not the laptop?
Could it be that you need to make sure
an .Xdefaults file in my home directory which
included:
Xterm*faceName Bitstream Vera Sans Mono
Xterm*faceSize 10
I think case matters here, i.e. XTerm*, not Xterm or xterm.
Everything works fine. However, when I tried to to this on my old
Compaq Presario on which I have 7.2 installed it doesn't
settled on the one I liked
most. Then I created an .Xdefaults file in my home directory which
included:
Xterm*faceName Bitstream Vera Sans Mono
Xterm*faceSize 10
I think case matters here, i.e. XTerm*, not Xterm or xterm.
Exactly the problem. Thank you!
Rem
On Tue, Dec 22, 2009 at 01:45:52PM -0800, Rem P Roberti wrote:
I think case matters here, i.e. XTerm*, not Xterm or xterm.
Exactly the problem. Thank you!
Curious, on my system (7.2) my ~/.Xdefaults uses lowercase 'xterm*...'
values.
At least you got it working which is the main thing
on google for the term
.Xdefaults. Often you can find all the information you need using
google.)
Aaron
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hello, I'm using FreeBSD 5.1 and came across something today. Say I
wanted to make xterms background by default i could add
XTerm*background: black
into my ~/.Xdefaults file and it would load by default. Where would I
go about finding out more options for more programs to place them in
my
On Mon, Jun 30, 2003 at 11:22:47AM -0500, [EMAIL PROTECTED] wrote:
Hello, I'm using FreeBSD 5.1 and came across something today. Say I
wanted to make xterms background by default i could add
XTerm*background: black
into my ~/.Xdefaults file and it would load by default. Where would I
go
Matthew Seaman wrote:
On Mon, Jun 30, 2003 at 11:22:47AM -0500, [EMAIL PROTECTED] wrote:
Hello, I'm using FreeBSD 5.1 and came across something today. Say I
wanted to make xterms background by default i could add
XTerm*background: black
into my ~/.Xdefaults file and it would load by default
Hello! I use KDE3.0 on FreeBSD 5.0-RELEASE.
My xterm won't accept the changes I have made to ~/.Xdefaults, but my emacs
sure does. I /have/ run $ xrdb ~/.Xdefaults, I even tried $ xrdb -merge
~/.Xdefaults even though I don't know what it does...
Now for the idiot thing (me being the idiot
in message [EMAIL PROTECTED], wrote Fredrik
Carlén thusly...
I even tried $ xrdb -merge ~/.Xdefaults even though I don't know
what it does...
From xrdb(1)...
-load This option indicates that the input should be loaded as
the new value of the specified properties, replacing
14 matches
Mail list logo
