On Mon, Mar 31, 2014 at 9:22 PM, Brian 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 first
>
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 betwe
> 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
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 listmas...@lists.debi
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
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 mor
> 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,
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*
On Fri 21 Mar 2014 at 22:26:40 +0530, Anubhav Yadav wrote:
> > 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, Vin
> 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 hi
On Wed 19 Mar 2014 at 21:57:44 +0530, Anubhav Yadav wrote:
> That sure cleared lot of things!
We preesume you are now satisfied with the solution you have. There is
nothing wrong with it but there is another aspect to the problem which
you have actually observed. You have given all the relevant
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:
https://lists.debian.org/CA+Jf9AFyyJ02xgY+feMzTmRHsxXTQvhONuq1Qz5m2_ZJ50=v...@mail.gmail.
On Tue 18 Mar 2014 at 23:32:04 +0530, Anubhav Yadav wrote:
> So my question is what do you mean by "Xterm", and then how is "xterm"
> different?
There is no meaning for Xterm without launching an xterm with the -name
option. Do you mean XTerm?
> I can guess it has something to do with the class
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 ca
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 merge
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 a
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
> 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 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 clear
> (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*foregroun
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
> 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
*color1
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 prior
> 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-use
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 prior
> 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 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 colorschem
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
> chang
> 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 Mon 17 Mar 2014 at 04:22:12 +0530, Anubhav Yadav wrote:
> Running startx logged me in to xfce, I opened up a xterm and the
> background was red.
Fine; the recommended line works.
> Next I enabled lightdm: #update-rc.d lightdm enable
> Rebooted and from lightdm logged in to i3.
> Opened up an
> 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
Okay before doing what you stated, I restored the file
/etc/X11/Xsession.d/30x11-
common_xresources to original
> 1. Prevent lightdm from being started:
>
> update-rc.d lightdm disable('enable' reverts this).
Done
> 2. Delete $HOME/.Xdefaults (It's not used).
Never used
On 2014-03-15, Anubhav Yadav 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, and I
> start
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
On Sun 16 Mar 2014 at 10:22:21 +0530, Anubhav Yadav wrote:
> 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!
I'd see it as a defeat because you are al
> 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
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
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 debi
On Sun, Mar 16, 2014 at 4:51 AM, John D. Hendrickson and Sara Darnell
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 and change onl
On Sun, Mar 16, 2014 at 4:36 AM, Anubhav Yadav 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 instal
40 matches
Mail list logo
