Linux
> >
> > I have moved to a display manager (wmd), so is my xrdb ~/.Xresources line
> > (xrdb ~/.Xresources) in .xinitrc being called into the loop, so to speak?
>
> You can use "xrdb -query" to find out.
>
> In general, I would *not* expect ~/.xinitrc
On Tue, Jul 07, 2020 at 10:07:35AM -0400, Bob Bernstein wrote:
> Sorry to be all over the court here. I am an older um gentleman, and I am on a
I take it an "um gentleman" means "übér mènsche" :)
That sounds rather awesome actually...
> --
> A test of right and wrong must be the means, one
On Ma, 07 iul 20, 10:07:35, Bob Bernstein wrote:
> Running up-to-date Buster here, amd64:
> Linux debian.localdomain 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1+deb10u1
> (2020-04-27) x86_64 GNU/Linux
>
> I have moved to a display manager (wmd), so is my xrdb ~/.Xresources line
> (
On Tue, Jul 07, 2020 at 10:07:35AM -0400, Bob Bernstein wrote:
> Running up-to-date Buster here, amd64:
> Linux debian.localdomain 4.19.0-8-amd64 #1 SMP Debian 4.19.98-1+deb10u1
> (2020-04-27) x86_64 GNU/Linux
>
> I have moved to a display manager (wmd), so is my xrdb ~/.Xresourc
Running up-to-date Buster here, amd64:
Linux debian.localdomain 4.19.0-8-amd64 #1 SMP Debian
4.19.98-1+deb10u1 (2020-04-27) x86_64 GNU/Linux
I have moved to a display manager (wmd), so is my xrdb
~/.Xresources line (xrdb ~/.Xresources) in .xinitrc being called
into the loop, so to speak
On Mon 31 Mar 2014 at 05:03:14 +0530, Anubhav Yadav wrote:
Which should be the best option for me?
xterm*color1: #f92672
or
XTerm*VT100*color1: #f92672
Both override what is in /etc/X11/app-defaults/XTerm-color. The first
option is best for me.
And what is the difference between the
On Mon, Mar 31, 2014 at 9:22 PM, Brian a...@cityscape.co.uk wrote:
On Mon 31 Mar 2014 at 05:03:14 +0530, Anubhav Yadav wrote:
Which should be the best option for me?
xterm*color1: #f92672
or
XTerm*VT100*color1: #f92672
Both override what is in /etc/X11/app-defaults/XTerm-color. The
And including that one in the list gives:
xterm*color1: #f92672
XTerm*VT100*color: #f92672?
XTerm*color: #f92672
*VT100*color1: red3
Which should be the best option for me?
xterm*color1: #f92672
or
XTerm*VT100*color1: #f92672
And what is the difference between the
So ultimately the conclusion is that for me to have the
most optimized settings, I should change all my colors
from xterm*color to XTerm*color
Is that right?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Fri 28 Mar 2014 at 22:33:20 +0530, Anubhav Yadav wrote:
So according to our discussion, my colors in *MY* .Xresources should
be more *specific* to the
resources used system wide.
Yes; especially in the light of Debian's setup.
In that case my settings for colors should be:
XTerm*VT100
My fault; the command is 'appres XTerm xterm'. There should be two
resource lines with color1 in them. One is from XTerm-color, the other
is from the merged .Xresources. Which one is more specific?
I found this
*VT100*color1: red3
and
xterm*color1: #f92672
From our discussions before, I
On Fri, Mar 28, 2014 at 10:33:20PM +0530, Anubhav Yadav wrote:
|| I found this
|| *VT100*color1: red3
|| and
|| xterm*color1: #f92672
Specificity is checked left to right. The second specifies an instance
xterm, which comes earlier than class VT100 of the first. Therefore the
second is
On Fri 28 Mar 2014 at 21:13:43 +0100, Vincent Zweije wrote:
And including that one in the list gives:
xterm*color1: #f92672
XTerm*VT100*color: #f92672?
XTerm*color: #f92672
*VT100*color1: red3
because #2 specifies VT100 in the second slot, where #3 specifies nothing
Re-read what Vincent Zweije wrote, especially his first mail. Then
re-read the answers in the stackexchange link you gave, concentrating on
what is said about specific and priority. Now re-read what you wrote:
Yes, Vincent said that the default .Xresources contain some settings
with a higher
that the default .Xresources contain some settings
with a higher priority. And the stackexchange comments says that if there
is an Xresource somewhere that has more specific settings like
XTerm*background
then it overides the generic settings like *background.
Spot on. Note *VT100*background
wrote:
One more thing I would like to point out is that, the above
outputs contains some extra lines in the output of 'xrdb -query
that are *NOT* in my version of .Xresources. Like
*customization: -color
Xft.lcdfilter: lcddefault
etc.
(The etc was ok. I misunderstood; my
On Tue, Mar 18, 2014 at 11:32:04PM +0530, Anubhav Yadav wrote:
|| So you mean to say that the resources were already being merged but
|| actually came into effect when I increased their priority or made them more
|| specific by add the class xterm* before the settings!
The default resources
.Xresources I
could use either to specify the resources. With
xterm -name Xterm
the class is unchanged but the instance is Xterm. xterm in your
.Xresources now has no effect because it is not the instance name.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
Thanks a lot Brian
That sure cleared lot of things!
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
On Tue, Mar 18, 2014 at 06:02:33AM +0530, Anubhav Yadav wrote:
|| The '-query' option to xrdb is useful. Interesting you used your original
|| .Xresources rather than one modified in the light of your experience. :)
||
|| That;s because I want my .Xresources to work, I had made colorscheme
This suggests that the resources that are loaded into your X server
by default contain settings with a higher priority than your own
.Xresources. The xrdb -merge merges your settings, but leaves the
higher priority resources there as well, so your settings seem to have
no effect. The xrdb
On Tue, Mar 18, 2014 at 04:01:36PM +0530, Anubhav Yadav wrote:
|| This suggests that the resources that are loaded into your X server
|| by default contain settings with a higher priority than your own
|| .Xresources. The xrdb -merge merges your settings, but leaves the
|| higher priority
Are those the default settings, or did you run xrdb -load already?
No I haven't run xrdb -load .Xresources yet
These are the same colors that I have used in my .Xresources.
--
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.
--
To UNSUBSCRIBE, email to debian-user
On Tue, Mar 18, 2014 at 04:01:36PM +0530, Anubhav Yadav wrote:
|| This suggests that the resources that are loaded into your X server
|| by default contain settings with a higher priority than your own
|| .Xresources. The xrdb -merge merges your settings, but leaves the
|| higher priority
Try
xrdb -query
Here is it output, the colors are exactly the same as in my .Xresources.
*background:#1b1d1e
*color0:#1b1d1e
*color1:#f92672
*color10: #b6e354
*color11: #feed6c
*color12: #8cedff
*color13: #9e6ffe
*color14: #899ca1
*color15
On Tue 18 Mar 2014 at 19:28:52 +0530, Anubhav Yadav wrote:
One more thing I would like to point out is that, the above outputs contains
some extra lines in the output of 'xrdb -query that are *NOT* in my
version of .Xresources. Like
*customization: -color
Xft.lcdfilter: lcddefault
You're
(If it wasn't clear, I intended you to try the two lines I gave you
earlier in your existing .Xresources, replacing the ones you have).
Sorry, I had the impression that you wanted me to stick to only that colors.
Ok I cleared my .Xresources and now it has only these to lines.
xterm*foreground
On Tue 18 Mar 2014 at 20:20:49 +0530, Anubhav Yadav wrote:
(If it wasn't clear, I intended you to try the two lines I gave you
earlier in your existing .Xresources, replacing the ones you have).
Sorry, I had the impression that you wanted me to stick to only that colors.
Ok I cleared my
There - it works. Is there anything you could do to your existing
.Xresources to make the rest work? Or does it so already?
Thanks a lot,
I solved it. Just had to change all instances of *color# to xterm*color#
As simple as that!
What I liked more was instead of giving me direct solution you
On Tuesday 18 March 2014 15:47:47 Anubhav Yadav wrote:
Can I change my subject header and all [SOLVED] to it? Because last
time I did it, the mail went as a new thread on the mailing list!
No, it went as a new thread on Gmail. Gmail routinely breaks
threading. It's a pain. :-( It's one of
On Tue 18 Mar 2014 at 21:17:47 +0530, Anubhav Yadav wrote:
There - it works. Is there anything you could do to your existing
.Xresources to make the rest work? Or does it so already?
Thanks a lot,
I solved it. Just had to change all instances of *color# to xterm*color#
As simple
Just in case: the command
xrdb -merge .Xresources
is definitely run when X is called. The resources in .Xresources are
merged with those in /etc/X11. If you issue the same command from a
terminal nothing happens to alter the resources available because
they have already been merged
an xterm and the background was red.
We seem to be able to rule out lightdm as the problem.
Now I used my original .Xresources and reboot. Again same error!
'xrdb -merge .Xresources' and 'xrdb -overide .Xresources' will not work
The '-query' option to xrdb is useful. Interesting you used your original
The '-query' option to xrdb is useful. Interesting you used your original
.Xresources rather than one modified in the light of your experience. :)
That;s because I want my .Xresources to work, I had made colorscheme
changes to it!
Here is the complete .Xresources that I am trying to use
http
On Tue, Mar 18, 2014 at 06:02:33AM +0530, Anubhav Yadav wrote:
The '-query' option to xrdb is useful. Interesting you used your original
.Xresources rather than one modified in the light of your experience. :)
That;s because I want my .Xresources to work, I had made colorscheme
changes
On Sun, Mar 16, 2014 at 10:22:21AM +0530, Anubhav Yadav wrote:
Solved.
Are you sure? What do you think will happen on an upgrade of Xorg?
I edited the file /etc/X11/Xsession.d/30x11-common_xresources and
changed the xorg -merge ... lines to xorge ... and it worked.
I don't know if it is a
Weird! What did you read that advised changing xorg to xorge?
Damn I don't know what happened to me while typing. Sorry. \
This is what I actually did!
The original line was
xrdb -merge $RESOURCEFILE
and
xrdb -merge $USRRESOURCES
I just removed the -merge options.
And I made the changes in
).
3. Delete $HOME/.xinitrc (It fouls up Debian's X).
4. Move $HOME/.xsession out of the way.
5. Repair self-inficted damage with
apt-get --reinstall install x11-common
6. Have 'xterm*background: red' as the only line in $HOME/.Xresources.
7. Reboot, execute startx and bring
On Sun 16 Mar 2014 at 23:36:21 +1300, Chris Bannister wrote:
On Sun, Mar 16, 2014 at 10:22:21AM +0530, Anubhav Yadav wrote:
Solved.
Are you sure? What do you think will happen on an upgrade of Xorg?
To help him with thinking this through he should find out what a
conffile is. Then
dpkg
On 2014-03-15, Anubhav Yadav anubhav1...@gmail.com wrote:
Hello,
Suddenly my .Xresources are not working on startup. Meaning I have to
manually startup a terminal and issue xrdb .Xresources and restart
the shell to see my colors.
I am using(learning to use) i3 although I have xfce installed
'xterm*background: red' as the only line in $HOME/.Xresources.
Ok
7. Reboot, execute startx and bring up an xterm.
Here are my results:
Running startx logged me in to xfce, I opened up a xterm and the
background was red.
Next I enabled lightdm: #update-rc.d lightdm enable
Rebooted and from
Is it this bug?
https://bugs.launchpad.net/lightdm/+bug/1084885
And this workaround?
https://wiki.archlinux.org/index.php/LightDM#Xresources_not_being_parsed_correctly
Yes I tried the workaround mentioned here before posting on the list.
Still thanks for talking out time and helping me out
Hello,
Suddenly my .Xresources are not working on startup. Meaning I have to
manually startup a terminal and issue xrdb .Xresources and restart
the shell to see my colors.
I am using(learning to use) i3 although I have xfce installed, and I
start i3/xfce from lightdm.
Now I remember doing two
On Sun, Mar 16, 2014 at 4:36 AM, Anubhav Yadav anubhav1...@gmail.com wrote:
Hello,
Suddenly my .Xresources are not working on startup. Meaning I have to
manually startup a terminal and issue xrdb .Xresources and restart
the shell to see my colors.
I am using(learning to use) i3 although I
On Sun, Mar 16, 2014 at 4:51 AM, John D. Hendrickson and Sara Darnell
johnandsa...@cox.net wrote:
i wrote this:
http://sourceforge.net/p/xdm-options/
it launches window manager desktop pairs. you might see something in it
that helps
this seems simple. back off your recent changes
Solved.
I edited the file /etc/X11/Xsession.d/30x11-common_xresources and
changed the xorg -merge ... lines to xorge ... and it worked.
I don't know if it is a good solution or not!
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.
--
To UNSUBSCRIBE, email to
I have been fooling around with xclock (under Icewm) but
now have a question- is it possible to prevent the window manager from
applying its' decorations to xclock? I had a look at editres but
was unable to find anything corresponding to a resource that might
prevent decorations.
Thanks
--
To
Frank McCormick debianl...@videotron.ca wrote:
I have been fooling around with xclock (under Icewm) but
now have a question- is it possible to prevent the window manager from
applying its' decorations to xclock? I had a look at editres but
was unable to find anything corresponding to a resource
On 06/11/13 05:24 PM, Jochen Spieker wrote:
Frank McCormick debianl...@videotron.ca wrote:
I have been fooling around with xclock (under Icewm) but
now have a question- is it possible to prevent the window manager from
applying its' decorations to xclock? I had a look at editres but
was
use .Xresources file instead then I get the right geometry and the
blinking cursor when I log out/in into X Window system.
Also when I start another xterm window after run the command
'xrdb -merge .Xdefaults' I can't use the xterm menus anymore (control
key and mouse buttons) because the menus
':
xterm*geometry: 90x40
xterm*renderFont: default
xterm*cursorBlink: true
If I use .Xresources file instead then I get the right geometry and
the blinking cursor when I log out/in into X Window system.
I believe .Xdefaults is no longer used. The system
file /etc/X11/Xsession assigns
option the right option for
setting up xterm for TrueType Fonts?
You could also try ‘faceName’.
These lines bellow in my ~/.Xresources did the trick: :)
xterm*geometry: 140x43
xterm*faceName: default
xterm*cursorBlink: true
xterm*cursorUnderLine: true
Check ‘man xterm’.
Yes
From: Bob Proulx b...@proulx.com
Date: Wed, 09 Feb 2011 11:24:45 -0700
To workaround the noise create an empty file.
$ touch .Xresources
Check.
The default file created automatically by vnc ... contains the
following: ...
Restored that. Yes, TightVNC works again. Whew
it the
exact *same browser* on the exact *same screen*? Changing it on one
screen will change it on the other too since there is only one browser
window being changed, right? What did I miss?
For that I'll need to use xrdb properly with screen specific
parameters in .Xresources. Documentation I've
From: Bob Proulx b...@proulx.com
Date: Thu, 10 Feb 2011 14:24:41 -0700
We are talking about VNC sharing a *single* screen.
Two machines, Dalton and Cantor in http://carnot.yi.org/NetworkExtant.jpg .
Dalton has an X server and a TightVNC server. My understanding is that
TightVNC uses X to
the resources in .Xdefaults / .Xresources which is is
somehow copied between the two (or network filesystem shared) that
this would change the default browser size when the browser starts
up. Gotcha.
Bob Proulx wrote:
Sometimes what people do is to script the setting of some resources.
So here it would
and then start up a vnc session, right?
On Cantor simply execute (click) this and the viewer opens.
Desktops.OpenDoc dalton.invalid:5901 (VNCViewerDocs.NewDoc) ~
Yes, Cantor sends a password to Dalton.
... you meant when
you change the resources in .Xdefaults / .Xresources which is is
somehow copied
Appears that I need to make a .Xresources file before
TightVNC will work. Can anyone recommend instructions
or examples for the task? The transcript from the
TightVNC follows.
Thanks, ... Peter E.
peter@dalton:~$ tightvncserver :1 -geometry 620x730 -depth 16
New 'X' desktop
Appears that I need to make a .Xresources file before
TightVNC will work. Can anyone recommend instructions
or examples for the task? The transcript from the
TightVNC follows.
Thanks, ... Peter E.
peter@dalton:~$ tightvncserver :1 -geometry 620x730 -depth 16
New 'X' desktop
Try this:
#!/bin/sh
[ -x /etc/vnc/xstartup ] exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic
#x-terminal-emulator -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop
#x-window-manager
openbox-lxde
lxsession
lxpanel
pcmanfm
On Wed, Feb 09, 2011 at 12:03:04PM EST, peasth...@shaw.ca wrote:
Appears that I need to make a .Xresources file before
TightVNC will work. Can anyone recommend instructions
or examples for the task? The transcript from the
TightVNC follows.
Thanks, ... Peter E.
peter
peasth...@shaw.ca wrote:
Appears that I need to make a .Xresources file before
TightVNC will work.
Shouldn't need one.
Can anyone recommend instructions or examples for the task?
To workaround the noise create an empty file.
$ touch .Xresources
The transcript from the TightVNC follows
Chris Jones wrote:
That's odd.. the vnc4server script on ‘lenny’ from the vnc4server
package tests the existence of the file:
[ -r ~/.Xresources ] xrdb -merge ...
The vncserver uses the alternatives. It could be one of several
different servers. From my machine:
$ update-alternatives
From: Franz Gustav Niederheitmann fra...@gmail.com
Date: Wed, 09 Feb 2011 15:26:31 -0200
Try this:
#!/bin/sh
[ -x /etc/vnc/xstartup ] exec /etc/vnc/xstartup
...
I put your text in /home/peter/.vnc/xstartup. Incidentally /home/peter/.vnc
versus /etc/vnc could be a source of
On Wed, Feb 09, 2011 at 01:28:53PM EST, Bob Proulx wrote:
Chris Jones wrote:
That's odd.. the vnc4server script on ‘lenny’ from the vnc4server
package tests the existence of the file:
[ -r ~/.Xresources ] xrdb -merge ...
The vncserver uses the alternatives. It could be one
on 11:24 Wed 09 Feb, Bob Proulx (b...@proulx.com) wrote:
peasth...@shaw.ca wrote:
Appears that I need to make a .Xresources file before
TightVNC will work.
Shouldn't need one.
Can anyone recommend instructions or examples for the task?
To workaround the noise create an empty file
Dr. Ed Morbius wrote:
Bob Proulx wrote:
That is a default because most people have a .Xresources file.
They do?
Sorry I was definitely over generalized there. :-)
An empty .Xresources should work just fine, but if that's required by
the tightvnc (or other) package, I'd file a bug.
I
and testing
something unrelated, when I saw that I was gettting the wrong fonts,
colors, etc. etc. I just duplicated did: cp .Xdefaults .Xresources.
Seems reasonable to me.
That's what gave me the idea of the empty ~/.Xresources file.
Again that seems reasonable to me.
But since debian systems
the
default place to do so, but for the bulk of the userbase, that's
probably two or three levels of obscure arcana.
.. drop your guard and reality ‘obscurely’ hits back and bites your ass.
An empty .Xresources should work just fine, but if that's required by
the tightvnc (or other) package, I'd
On Sat, Aug 21, 2010 at 09:38:01PM +0200, Mathias Bauer wrote:
Hi!
* Andreas Goesele schrieb am Sa, 07.08.2010 um 12:51 (+0200):
for me the xpdf fonts are too small. So I changed them by putting
xpdf*fontList: -*-helvetica-medium-r-*-*-*-140-*-*-*-*-iso8859-1
into .Xresources
Hi!
* Andreas Goesele schrieb am Sa, 07.08.2010 um 12:51 (+0200):
for me the xpdf fonts are too small. So I changed them by putting
xpdf*fontList: -*-helvetica-medium-r-*-*-*-140-*-*-*-*-iso8859-1
into .Xresources
But this leaves the fontsize of the textareas (Page, Search
field, printing
Hi,
for me the xpdf fonts are too small. So I changed them by putting
xpdf*fontList: -*-helvetica-medium-r-*-*-*-140-*-*-*-*-iso8859-1
into .Xresources
But this leaves the fontsize of the textareas (Page, Search field,
printing dialog) unchanged. Is there a way to change the fontsize
I have Debian Lenny basic system with X Window, Ice WM, and xdm
installed. When I try to configure Xterm, X.org seems to ignore the
~/.Xresources file.
The command xrdb -merge ~/.Xresources doesn't do any good.
I also tried creating .xinitrc file with the entry
xrdb -load $HOME/.Xresources
On Thu, 02 Apr 2009 12:54:57 +0300, Kybernetiker posted:
I have Debian Lenny basic system with X Window, Ice WM, and xdm installed.
When I try to configure Xterm, X.org seems to ignore the ~/.Xresources
file.
The command xrdb -merge ~/.Xresources doesn't do any good.
I also tried
xrdb -query to see what you actually have.
if there are NO X clients, the resource data base is reset. so you
have to make sure there is a long running X client before you try to
set the resources.
finally, I don't think XTerm is the right name. IIRC, its Xterm for
the class, and xterm for the
On Thu, Apr 02, 2009 at 08:56:12AM EDT, Marc Auslander wrote:
finally, I don't think XTerm is the right name. IIRC, its Xterm for
the class, and xterm for the program.
The class name is XTerm.. as with many X clients whose name starts with
the letter 'x' (but not all .. xpdf for instance).
On Thu, 02 Apr 2009 12:54 +0300 Kybernetiker wrote:
I have Debian Lenny basic system with X Window, Ice WM, and xdm
installed. When I try to configure Xterm, X.org seems to ignore the
~/.Xresources file.
The file ~/.Xresources contains the only line:
XTerm*font: -*-terminus-*-*-*-*-24
Hi,
I recently installed lenny on a new computer and, like all other times I
installed Debian before, I had to customise the xdm files to suit my
needs. Nothing wrong so far.
Every time I input some UTF-8 text in Xresources and change the default
font from iso8859-1 to iso10646-1 (btw, why
Ionel Mugurel Ciobica wrote:
Hi,
I recently installed lenny on a new computer and, like all other times I
installed Debian before, I had to customise the xdm files to suit my
needs. Nothing wrong so far.
Every time I input some UTF-8 text in Xresources and change the default
font from
Am 2007-11-21 00:43:39, schrieb Kumar Ravichandran:
Hi,
I am running Debian Etch on a Macbook, and I have a simple problem,
namely, that my $HOME/.Xresources file, which has a few colour options
Why not put it into
$HOME/.Xdefaults-host-alias
or
$HOME/.Xdefaults
which are read
Am 2007-11-21 19:39:26, schrieb Kelly Clowers:
I made .Xdefaults a symlink to .Xresources, and it started working.
Might be worth a try.
Please note, that
~/.Xresources
are different from
~/.Xdefaults-host_alias
or
~/.Xdefaults
While the first one is read by the xserver from
Am 2007-11-18 17:21:12, schrieb giggz:
Bonsoir,
Je suis en train de m'amuser à configurer xterm...bon j'ai créé un
.Xdefaults et j'ai mis qqs options dedans. Cela fonctionne bien. Mais en
cherchant plus loin sur internet, pas mal d'utilisateurs mettent leur
options dans le .Xresources
options dans le .Xresources.
Quel est le bon fichier pour mettre les options du type :
xterm*geometry: et autres ?
Is sont deux choses different...
~/.Xdefaults
~/.Xdefaults-$(hostname --alias)
Sont generalement les DEFASULT pour tout les applications X.
Par example wmmount:
8
a simple problem,
namely, that my $HOME/.Xresources file, which has a few colour options
for xterm, is not read at startup. I need to manually xrdb load it
I have it in ~/.xinitrc
I tried that as well :(. No good!
I made .Xdefaults a symlink to .Xresources, and it started
Kumar Ravichandran [EMAIL PROTECTED]:
I am running Debian Etch on a Macbook, and I have a simple problem,
namely, that my $HOME/.Xresources file, which has a few colour options
for xterm, is not read at startup. I need to manually xrdb load it
I have it in ~/.xinitrc
--
Any technology
On Wed, Nov 21, 2007 at 04:52:29PM +0100, s. keeling wrote:
Kumar Ravichandran [EMAIL PROTECTED]:
I am running Debian Etch on a Macbook, and I have a simple problem,
namely, that my $HOME/.Xresources file, which has a few colour options
for xterm, is not read at startup. I need
On Nov 21, 2007 7:07 PM, Kumar Ravichandran
[EMAIL PROTECTED] wrote:
On Wed, Nov 21, 2007 at 04:52:29PM +0100, s. keeling wrote:
Kumar Ravichandran [EMAIL PROTECTED]:
I am running Debian Etch on a Macbook, and I have a simple problem,
namely, that my $HOME/.Xresources file, which has
Hi,
I am running Debian Etch on a Macbook, and I have a simple problem,
namely, that my $HOME/.Xresources file, which has a few colour options
for xterm, is not read at startup. I need to manually xrdb load it
each session. I tried a variety of options, including linking it to
the system
On 2007-11-18 17:21:12 +0100, giggz wrote:
Je suis en train de m'amuser à configurer xterm...bon j'ai créé un
.Xdefaults et j'ai mis qqs options dedans. Cela fonctionne bien. Mais en
cherchant plus loin sur internet, pas mal d'utilisateurs mettent leur
options dans le .Xresources.
Le
Bonsoir,
Je suis en train de m'amuser à configurer xterm...bon j'ai créé un
.Xdefaults et j'ai mis qqs options dedans. Cela fonctionne bien. Mais en
cherchant plus loin sur internet, pas mal d'utilisateurs mettent leur
options dans le .Xresources.
Quel est le bon fichier pour mettre les options
.Xresources.
Quel est le bon fichier pour mettre les options du type :
xterm*geometry: et autres ?
On doit pouvoir mettre dans les deux, mais je pense que .Xresources est
plus global.
Tu peux lire les fichiers /etc/X11/Xsession.d/30x11-common_xresources,
/etc/X11/Xsession.optionos /etc/X11
mettent leur
options dans le .Xresources.
Quel est le bon fichier pour mettre les options du type :
xterm*geometry: et autres ?
On doit pouvoir mettre dans les deux, mais je pense que .Xresources est
plus global.
Tu peux lire les fichiers /etc/X11/Xsession.d/30x11-common_xresources,
/etc
giggz, dimanche 18 novembre 2007, 18:49:37 CET
[…]
Ok merci pour ces précisions. Je vais tout mettre
tout .Xresources et faire un lien symbolique pour .Xdefaults
C’est en effet plus simple comme cela :o)
Il y a aussi pas mal d’applications qui lisent .‹applic›rc
(genre .xdvirc) mais n’en
launched by the
window manager are clearly ignoring my Xresources settings. To be
precise:
1) Xterms launched via menu entry or via hard-coded commands in the
window manager have default settings (small fixed font, white-on
black) irrespective of the contents
Mumia W. [EMAIL PROTECTED] wrote:
What are those hard-coded commands you're talking about? That's
important because terminal emulators recognize their resources based
upon their names. So if you define resources for XTerm (note the
capitals), but you start the program as xterm, it won't
Ian Daniel Leroux [EMAIL PROTECTED] writes:
Putting a BSD kernel into an otherwise GPL system does nothing to
address that.
To be fair, Debian is not a GPL system, it's a free software system
(with a specific definition of free software independent of the GPL).
They happily package BSD-licensed
I'm having a strange (to me) problem where xterms launched by the window
manager are clearly ignoring my Xresources settings. To be precise:
1) Xterms launched via menu entry or via hard-coded commands in the
window manager have default settings (small fixed font, white-on black)
irrespective
On 09/15/2006 07:50 AM, Ian D. Leroux wrote:
I'm having a strange (to me) problem where xterms launched by the window
manager are clearly ignoring my Xresources settings. To be precise:
1) Xterms launched via menu entry or via hard-coded commands in the
window manager have default settings
On Fri, 15 Sep 2006 09:03:23 -0500, Mumia W.
[EMAIL PROTECTED] said:
On 09/15/2006 07:50 AM, Ian D. Leroux wrote:
I'm having a strange (to me) problem where xterms launched by the
window manager are clearly ignoring my Xresources settings. To be
precise:
1) Xterms launched via menu
On 09/15/2006 10:52 AM, Ian D. Leroux wrote:
On Fri, 15 Sep 2006 09:03:23 -0500, Mumia W.
[EMAIL PROTECTED] said:
On 09/15/2006 07:50 AM, Ian D. Leroux wrote:
I'm having a strange (to me) problem where xterms launched by the
window manager are clearly ignoring my Xresources settings
1 - 100 of 209 matches
Mail list logo
