Re: .Xresources not loading on start

[Anubhav Yadav]

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
> option is best for me.

Thanks that should be enough to mark this thread as solved :)

> For example, DIR is 01;34. This corresponds to color12.
>
> I'd suggest we are now going well beyond your original (solved) problem.

That brings to light another problem that I am facing now. I am not
able to set the
dircolors right for the ls command. But I think I should start a new
thread for the same.

Thanks for helping me out everyone. Cheers :)


-- 
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+Jf9AF3EDHTbvY7+z50a3o=ug8gyu2m6qc_tlg26wxxcj8...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 resources
> color1 and color?

First read about the -p option in dircolors(1). There are 8 available
colours (30-37) for a terminal outside X. In an xterm color0, color1 etc
correspond to 30, 31 etc. colors 8-15 corresond to the bold variants of
these colors. Please see xterm(1) and /etc/X11/app-defaults/XTerm-color.

For example, DIR is 01;34. This corresponds to color12.

I'd suggest we are now going well beyond your original (solved) problem.


-- 
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/20140331155257.gi3...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 resources
color1 and color?

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+Jf9AGqvvzOTE9M4FT05x2YNa=LvAUM6i=v+vgkd0goij7...@mail.gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

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.debian.org
Archive: 
https://lists.debian.org/ca+jf9agfrpt_h528cpowommdro5mipnnwvtoy_ozxbqqewj...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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
> (the "color" is the third slot). Maybe this way of writing it makes
> this clearer:
> 
>   
>   
>   
>   
> 
> And now I see that there's actually not even about the same resource! #1
> and #4 are about resource instance "color1", #2 and #3 are about resource
> instance "color".
> 
> Oh well, I guess you see things work.

It's "spot the typo" time! Made once and then repeated, unfortunately.


-- 
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/20140329002312.gb3...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Vincent Zweije]

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 more specific, and gets priority.

||  In that case my settings for colors should be:
||
||  XTerm*VT100*color: #f92672?

Depends, because there is a second rule: the instance name (xterm)
is more specific than the class name (XTerm).

So from high to low specificity and thus priority:

xterm*color1:   #f92672
XTerm*VT100*color: #f92672?
*VT100*color1:  red3

Your example falls in between.

On Fri, Mar 28, 2014 at 05:32:12PM +, Brian wrote:

||  That should do it but
||
||  XTerm*color: #f92672
||
||  is ok too (and less typing :))

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
(the "color" is the third slot). Maybe this way of writing it makes
this clearer:

  
  
  
  

And now I see that there's actually not even about the same resource! #1
and #4 are about resource instance "color1", #2 and #3 are about resource
instance "color".

Oh well, I guess you see things work.

Vincent.
-- 
Vincent Zweije| "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: Digital signature

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 think *VT100*color1 should be more specific
>> > Now add the line
>> >*customization:
>> > to the original .Xresources and run the appres command again, Can you
>> > predict what should happen to an xterm when you start X?
>>

> Yes - you've missed my propensity to mistype; :) correct it and you're
> there.

Sorry for the epic late response here, had a placement drive in my
college. CCing it to Brian, only because of such a late
reply to this thread .

So according to our discussion, my colors in *MY* .Xresources should
be more *specific* to the
resources used system wide.

In that case my settings for colors should be:

XTerm*VT100*color: #f92672?

Is that right?


-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9afrvyynmfb94rdn1xfvb2ehjcn15yfsb90dfu0zorh...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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*color: #f92672?
> 
> Is that right?

That should do it but

XTerm*color: #f92672

is ok too (and less typing :))


-- 
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/28032014172633.a69033326...@desktop.copernicus.demon.co.uk

Re: .Xresources not loading on start

[Brian]

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, Vincent said 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 is also more specific than *background.

> > "*customization: -color" is from /etc/X11/Xresources/x11-common. It tells
> > X what application specific resource file in /etc/X11/app-defaults to use.
> > Normally the resource file used corresponds to the application name; for
> > example, XTerm for xterm. The customization resource adds -color to the
> > normal resource file name and so XTerm-color is used.
> 
> It's very confusing to me. From what I interpret, the *customization: -color
> simply selects XTerm-color resources instead of XTerm from
> /etc/X11/app-defaults?

Correct. Note that XTerm-color (you can check) includes XTerm, but this
is of no importance for our purposes.

> > Note that .Xresources is merged with XTerm-color but from your re-reading
> > (and from your experience) you should realise it does not mean everything
> > in it is applied.
> > Take your *original* .Xresources and, in the light of your reading, look
> > at the output (color1 etc in particular) of 'appres XTERM xterm'.
> 
> color1 is #f92672

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?

> > Now add the line
> >*customization:
> > to the original .Xresources and run the appres command again, Can you
> > predict what should happen to an xterm when you start X?
> 
> I am typing this *before* I make any changes in my .Xresources and
> before "xrdb .Xresources"

Don't use "xrdb .Xresources". It will wipe out averything from XTerm.
Not that it really matters here but it is not part of the testing
strategy.

> I feel that this should overide the *customization: -color settings in
> /etc/x11/Xresources and the settings in XTerm should be loaded.

That's the correct conclusion; the color settings from XTerm-color will
be absent and what is in .Xresources should prevail.

> Okay after adding the said line in .Xresources (*customization:) and
> reloading them
> (xrdb .Xresource) color1 is
> xterm*color1:   #f92672
> 
> Which is the same?
> 
> Am I missing something? Sorry for a delayed response!

Yes - you've missed my propensity to mistype; :) correct it and you're
there.


-- 
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/20140321184220.ge4...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 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.

> "*customization: -color" is from /etc/X11/Xresources/x11-common. It tells
> X what application specific resource file in /etc/X11/app-defaults to use.
> Normally the resource file used corresponds to the application name; for
> example, XTerm for xterm. The customization resource adds -color to the
> normal resource file name and so XTerm-color is used.

It's very confusing to me. From what I interpret, the *customization: -color
simply selects XTerm-color resources instead of XTerm from
/etc/X11/app-defaults?

> Note that .Xresources is merged with XTerm-color but from your re-reading
> (and from your experience) you should realise it does not mean everything
> in it is applied.
> Take your *original* .Xresources and, in the light of your reading, look
> at the output (color1 etc in particular) of 'appres XTERM xterm'.

color1 is #f92672

> Now add the line
>*customization:
> to the original .Xresources and run the appres command again, Can you
> predict what should happen to an xterm when you start X?

I am typing this *before* I make any changes in my .Xresources and
before "xrdb .Xresources"
I feel that this should overide the *customization: -color settings in
/etc/x11/Xresources and the settings in XTerm should be loaded.

Okay after adding the said line in .Xresources (*customization:) and
reloading them
(xrdb .Xresource) color1 is
xterm*color1:   #f92672

Which is the same?

Am I missing something? Sorry for a delayed response!

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+Jf9AFDxm-FTSXY=hHvwG+j2Ex_eqjjt=KbqRr_+6_C9=5...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 information
in your posts and from it we can get another (but not necessarily better)
solution.

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:

   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 previous comment on it can be
ignored. :))

"*customization: -color" is from /etc/X11/Xresources/x11-common. It tells
X what application specific resource file in /etc/X11/app-defaults to use.
Normally the resource file used corresponds to the application name; for
example, XTerm for xterm. The customization resource adds -color to the
normal resource file name and so XTerm-color is used.

Note that .Xresources is merged with XTerm-color but from your re-reading
(and from your experience) you should realise it does not mean everything
in it is applied.

Take your *original* .Xresources and, in the light of your reading, look
at the output (color1 etc in particular) of 'appres XTERM xterm'.

Now add the line

   *customization:

to the original .Xresources and run the appres command again, Can you
predict what should happen to an xterm when you start X?


-- 
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/20140320115858.gp26...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

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.com

Re: .Xresources not loading on start

[Brian]

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 of applications/ instance of
> applications!

Resources are specified with either

   instance*resource: value

or

   class*resource: value

The xprop program will tell you what the instance and class are. I have

   WM_CLASS(STRING) = "xterm", "XTerm"

"xterm" is the instance and "XTerm" the class. With your .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 of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140319104002.go26...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Vincent Zweije]

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 can be found (on my system) under
/etc/X11/app-defaults.

If you look in the files for xterm, you'll see the default resource
settings. The resources that you load yourself have to be at least as
specific as those, otherwise the defaults override yours. Prefixing with
xterm* normally makes your resources specific enough.

||  So my question is what do you mean by "Xterm", and then how is "xterm"
||  different?
||  I can guess it has something to do with the class of applications/ instance
||  of applications!

Play with editres. It's a bit clunky but may give you a feel about what
classes and instances mean.

By the way, the class for xterm is called XTerm, not Xterm.

Vincent.
-- 
Vincent Zweije| "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: Digital signature

Re: .Xresources not loading on start

[Anubhav Yadav]

 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.
>
>xrdb .Xresources (xrdb -load .Xresources)
>
> wipes out the resources loaded from /etc/X11 and gives you only what
> is in .Xresources.
>
> Your initial understanding of this led you away from a solution to the
> actual problem. Not to worry; everyone does it and everybody learns. :)
>

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!

I tried to do this before, I remember very well, but I used Xterm
instead of xterm.
It was mentioned here.
http://unix.stackexchange.com/questions/90608/xterm-not-loading-color-schemes
When that never worked I posted on the mailing list.

So my question is what do you mean by "Xterm", and then how is "xterm"
different?
I can guess it has something to do with the class of applications/ instance of
applications!


-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9aen5gqhu4ysat4fg0upz01yxehgcft5y17p6kalou2...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 as that!
> 
> What I liked more was instead of giving me direct solution you
> motivated me to find
> the solution myself. Cheers for that.

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.

   xrdb .Xresources (xrdb -load .Xresources)

wipes out the resources loaded from /etc/X11 and gives you only what
is in .Xresources.

Your initial understanding of this led you away from a solution to the
actual problem. Not to worry; everyone does it and everybody learns. :)


-- 
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/20140318161341.gl26...@copernicus.demon.co.uk

SOLVED: Re: .Xresources not loading on start

[Lisi Reisz]

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 the reasons that I use 
Gmail as my address - but download to a "proper" email client.  I 
have marked this as SOLVED for you.  Unfortunately, Gmail will 
therefore start a new"conversation". 

Lisi


-- 
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/201403181556.58253.lisi.re...@gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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
motivated me to find
the solution myself. Cheers for that.

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!

Thanks again, really appreciated your time and effort!
-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+Jf9AEgKoXbjrjWPWGnz6qMr8aZXJ+ZazVN1HKiK1Bbnxn=8...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 .Xresources and now it has only these to lines.

It would have been sufficient to have just replaced the *foreground and
*background lines.

> xterm*foreground:#fd971f
> xterm*background:#82b414
> 
> Restarting the laptop and firing up an xterm sure changes the colors
> according to .Xresources.

There - it works. Is there anything you could do to your existing
.Xresources to make the rest work? Or does it so already?
 
> Here is the output for -query
> 
> neo1691@Innovator:~$ xrdb -query
> *customization: -color
> Xft.hinting:-1
> Xft.hintstyle:  hintnone
> xterm*background:   #82b414
> xterm*foreground:   #fd971f
> Xft.antialias:  -1
> Xft.rgba:   none
> Xcursor.theme:  Adwaita
> Xcursor.theme_core: true
> Xcursor.size:   0

Now do 'xrdb .Xresources' or 'xrdb -load .Xresources' (they are the same
command; please see  (xrdb(1)). Notice any difference? Why should there
be one? 


-- 
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/18032014150957.ae7e9d40a...@desktop.copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> (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:#fd971f
xterm*background:#82b414

Restarting the laptop and firing up an xterm sure changes the colors
according to .Xresources.

Here is the output for -query

neo1691@Innovator:~$ xrdb -query
*customization: -color
Xft.hinting:-1
Xft.hintstyle:  hintnone
xterm*background:   #82b414
xterm*foreground:   #fd971f
Xft.antialias:  -1
Xft.rgba:   none
Xcursor.theme:  Adwaita
Xcursor.theme_core: true
Xcursor.size:   0


-- 
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+jf9aghqvwxxxgef7dhared-+p9a1ponjw_vjxbusrbrmq...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 getting there. :)

Where do you think the other lines come from? What is your .Xresources
merged with?

> etc.

It's not very helpful to edit.

(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).


-- 
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/18032014141806.19485039d...@desktop.copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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:   #f8f8f2
*color2:#82b414
*color3:#fd971f
*color4:#56c2d6
*color5:#8c54fe
*color6:#465457
*color7:#c6
*color8:#505354
*color9:#ff5995
*customization: -color
*foreground:#a0a0a0
XTerm*ScrollBar:false
XTerm*locale:   true
XTerm*metaSendsEscape:  true
XTerm*selectToClipboard:true
Xcursor.theme:  Pulse-Glass
Xft.antialias:  1
Xft.autohint:   0
Xft.dpi:96
Xft.hinting:1
Xft.hintstyle:  hintfull
Xft.lcdfilter:  lcddefault
Xft.rgba:   rgb
Xterm*saveLines:9000
xterm*VT100.geometry:   80x32
xterm*eightBitInput:false
xterm*faceName: xft:Inconsolata:size=15:antialias=true
xterm*loginShell:   true
xterm*scaleHeight:  1.01
xterm*termName: xterm-256color


One thing I will like to say that
> appres XTerm xterm

Xterm*saveLines:9000
xterm*VT100.geometry:   80x32
xterm*scaleHeight:  1.01
xterm*faceName: xft:Inconsolata:size=15:antialias=true
xterm*termName: xterm-256color
xterm*loginShell:   true
xterm*eightBitInput:false
*color7:#c6
*color13:   #9e6ffe
*color8:#505354
*color14:   #899ca1
*color9:#ff5995
*background:#1b1d1e
*color15:   #f8f8f2
*color2:#82b414
*color0:#1b1d1e
*customization: -color
*color3:#fd971f
*color1:#f92672
*foreground:#a0a0a0
*color4:#56c2d6
*color10:   #b6e354
*color5:#8c54fe
*color11:   #feed6c
*color6:#465457
*color12:   #8cedff

Again the colors are the same.

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.

Also here is what my terminal looks like when I start my laptop and
how it should look actually:
http://imgur.com/a/C3EZi

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9ag+vymmw217206j+1hje-6dbqrols4qmwszwj6hwar...@mail.gmail.com

Re: .Xresources not loading on start

[Vincent Zweije]

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 resources there as well, so your settings seem to have
||  > no effect. The xrdb -load throws away all settings including the higher
||  > priority ones, thus letting your settings take effect.
||  >
||  > Use the appres tool to find out what the actual settings are that are
||  > loaded in your X server. If this confirms the theory, you can start
||  > finding out where the higher priority settings come from.
||  
||  Hi! appres tool gives me this output, and these are the same values
||  that are in my current .Xresources!
||  Any pointers?
||  
||  -- *color8:#505354
||  *color14:   #899ca1
||  *color9:#ff5995
||  *background:#1b1d1e
||  *color15:   #f8f8f2
||  *color2:#82b414
||  *color0:#1b1d1e
||  *customization: -color
||  *color3:#fd971f
||  *color1:#f92672
||  *foreground:#a0a0a0
||  *color4:#56c2d6
||  *color10:   #b6e354
||  *color5:#8c54fe
||  *color11:   #feed6c
||  *color6:#465457
||  *color12:   #8cedff
||  *color7:#c6
||  *color13:   #9e6ffe

Memory fault, sorry.

Try

xrdb -query

to see all resources being used. Alternatively, pass application class
and instance name to appres, for example:

appres XTerm xterm

Vincent.
-- 
Vincent Zweije| "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: Digital signature

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9ah6bz2q-79snhmfcwuvfhzacepk8vdid8onhrcd-h8...@mail.gmail.com

Re: .Xresources not loading on start

[Vincent Zweije]

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 resources there as well, so your settings seem to have
||  > no effect. The xrdb -load throws away all settings including the higher
||  > priority ones, thus letting your settings take effect.
||  >
||  > Use the appres tool to find out what the actual settings are that are
||  > loaded in your X server. If this confirms the theory, you can start
||  > finding out where the higher priority settings come from.
||  
||  Hi! appres tool gives me this output, and these are the same values
||  that are in my current .Xresources!
||  Any pointers?
||  
||  -- *color8:#505354
||  *color14:   #899ca1
||  *color9:#ff5995
||  *background:#1b1d1e
||  *color15:   #f8f8f2
||  *color2:#82b414
||  *color0:#1b1d1e
||  *customization: -color
||  *color3:#fd971f
||  *color1:#f92672
||  *foreground:#a0a0a0
||  *color4:#56c2d6
||  *color10:   #b6e354
||  *color5:#8c54fe
||  *color11:   #feed6c
||  *color6:#465457
||  *color12:   #8cedff
||  *color7:#c6
||  *color13:   #9e6ffe

Are those the default settings, or did you run xrdb -load already?

Vincent.
-- 
Vincent Zweije| "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: Digital signature

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 -load throws away all settings including the higher
> priority ones, thus letting your settings take effect.
>
> Use the appres tool to find out what the actual settings are that are
> loaded in your X server. If this confirms the theory, you can start
> finding out where the higher priority settings come from.

Hi! appres tool gives me this output, and these are the same values
that are in my current .Xresources!
Any pointers?

-- *color8:#505354
*color14:   #899ca1
*color9:#ff5995
*background:#1b1d1e
*color15:   #f8f8f2
*color2:#82b414
*color0:#1b1d1e
*customization: -color
*color3:#fd971f
*color1:#f92672
*foreground:#a0a0a0
*color4:#56c2d6
*color10:   #b6e354
*color5:#8c54fe
*color11:   #feed6c
*color6:#465457
*color12:   #8cedff
*color7:#c6
*color13:   #9e6ffe

Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9af5zy7zlt3iiwr8wk9o9b9f6pgyyp_vjzwvbskzcca...@mail.gmail.com

Re: .Xresources not loading on start

[Vincent Zweije]

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 to it!
||  Here is the complete .Xresources that I am trying to use
||  http://paste.debian.net/88298/
||  
||  The only thing that works for me is "xrdb -load .Xresources" and "xrdb
||  .Xresources"

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 -load throws away all settings including the higher
priority ones, thus letting your settings take effect.

Use the appres tool to find out what the actual settings are that are
loaded in your X server. If this confirms the theory, you can start
finding out where the higher priority settings come from.

Vincent.
-- 
Vincent Zweije| "If you're flamed in a group you
  | don't read, does anybody get burnt?"
[Xhost should be taken out and shot] |-- Paul Tomblin on a.s.r.


signature.asc
Description: Digital signature

Re: .Xresources not loading on start

[Chris Bannister]

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 to it!

What happens if you copy 'n' paste lines from the so called faulty file
to the working one?

IOW, for some reason your .Xresources is faulty or you have a crook
entry. 

You have a good one (the one which gives you the red background)
which you have proved works, so test each entry from the faulty
.Xresources in the good one. Eventually, the files will be identical,
but hopefully you'll find the problem by then. :)

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
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/20140318034556.GB22947@tal

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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://paste.debian.net/88298/

The only thing that works for me is "xrdb -load .Xresources" and "xrdb
.Xresources"

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9ahgiqedvvtj10xzju4gm12mehjlbzjxvpaqicru4+k...@mail.gmail.com

Re: .Xresources not loading on start

[Brian]

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 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
.Xresources rather than one modified in the light of your experience. :)

Try
   xterm*foreground:#fd971f
   xterm*background:#82b414


-- 
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/17032014161305.09b0d2c7a...@desktop.copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 here. Much
appreciated.

-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9ag6joykzanblywbycj3myp3i52owg3xcwe-sk+r-8b...@mail.gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

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 it in the first place.

> 3. Delete $HOME/.xinitrc   (It fouls up Debian's X).

I tried to use it never worked. So deleted it.

> 4. Move $HOME/.xsession out of the way.

Its not there.

> 5. Repair self-inficted damage with
>apt-get --reinstall install x11-common
Ok did this too!

> 6. Have '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 lightdm logged in to i3.
Opened up an xterm and the background was red.

Now I used my original .Xresources and reboot. Again same error!
'xrdb -merge .Xresources' and 'xrdb -overide .Xresources' will not work
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9ag32igynb-g_9sjatckrjd+xe2rvfpr2oftnvmj-qy...@mail.gmail.com

Re: .Xresources not loading on start

[Curt]

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 i3/xfce from lightdm.

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


-- 
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/slrnlibl8l.33d.cu...@einstein.electron.org

Re: .Xresources not loading on start

[Brian]

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 -S /etc/X11/Xsession.d/30x11-common_xresources

followed by

   dpkg --status 


-- 
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/16032014113342.2605202a7...@desktop.copernicus.demon.co.uk

Re: .Xresources not loading on start

[Brian]

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 altering a system file to achieve
something which is capable of being done under your own user.

You need to get back to something basic which works.

1. Prevent lightdm from being started:

update-rc.d lightdm disable('enable' reverts this).

2. Delete $HOME/.Xdefaults (It's not used).

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 up an xterm.


-- 
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/20140316112333.gd26...@copernicus.demon.co.uk

Re: .Xresources not loading on start

[Anubhav Yadav]

> 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 this file: /etc/X11/Xsession.d/30x11-common_xresources

I have made a backup of the above file! Just to be safe!


-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9agd9r+efo_m81cwf+raq8-aad73bbdzrjzrdzf5w6n...@mail.gmail.com

Re: .Xresources not loading on start

[Chris Bannister]

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 good solution or not!

Weird! What did you read that advised changing "xorg" to "xorge"?

P.S. I got lost in your original mail. I hope you've kept a record as to
what changes you made to any system files. Also, don't just edit a
system file, but comment out the line you are changing and add the
altered line below it.

-- 
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who are doing the 
oppressing." --- Malcolm X


-- 
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/20140316103621.GE18433@tal

Re: .Xresources not loading on start

[Anubhav Yadav]

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 debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/ca+jf9ah0pe1eq+krgvgzmabfv+cy4eeguz_zsef2waymgeo...@mail.gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

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 only one thing
> at a time.  you can then say which change caused a problem
>
>
> i would guess an "exit 1" signaled by any app during the X starup might give
> you headaches.  it's better to wait until after X starts (run a script then)
> unless you got everything down or are doing something special.

Hi, Thanks for taking out time and replying. Is that a complete new
display manager. Does it have a package for debian?
Also I pressed the send button my mistake, so I completed my question
in the next mail. Its link is,
https://lists.debian.org/debian-user/2014/03/msg00888.html
-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9ahem0fsdwaoanx0nbhx4z8doh74qylwzo3zfqjzzfo...@mail.gmail.com

Re: .Xresources not loading on start

[Anubhav Yadav]

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 installed, and I
> start i3/xfce from lightdm.
>
> Now I remember doing two things after which this started happening:
>
> 1) I changed the colors of my .Xresources from base16-tomorrow to molokai.
> Here is my .Xresources http://paste.debian.net/87922
>
> To be a little more precise, the previous scheme had the colors
> defined like this:
>
> #define t_background #1d1f21
> #define t_current_line #282a2e
> #define t_selection #373b41
> #define t_foreground #c5c8c6
> #define t_comment #969896
> #define t_red #cc
> #define t_orange #de935f
> #define t_yellow #f0c674
> #define t_green #b5bd68
> #define t_aqua #8abeb7
> #define t_blue #81a2be
> #define t_purple #b294bb
>
>
> *.foreground: t_foreground
> *.background: t_background
> *.cursorColor: #aeafad
>
> ! Black / Grey
> *.color0: #00
> *.color8: #66
>
> ! Red / Bright Red
> *.color1: t_red
> *.color9: #FF3334
>
> ! Green + Bright Green
> *.color2: t_green
> *.color10: #9ec400
> ..
> [snipped]
>
> And the new colors are directly put like this
>
> !Molokai terminal colours
> *foreground:#a0a0a0
> *background:#1b1d1e
>
> !molokai inspired colors
>
> !black
> *color0:#1b1d1e
> *color8:#505354
> !red
> *color1:#f92672
> *color9:#ff5995
> !green
> *color2:#82b414
> *color10:   #b6e354
> !yellow
> *color3:#fd971f
> *color11:   #feed6c
> !blue
> *color4:#56c2d6
> *color12:   #8cedff
>
> [..snipped..]
>
> 2) I edited the file /etc/lightdm/lightdm.conf and added this line:
> user-session=i3
> to make i3 as default in i3.
>
> 3) I created a file ~/.xessionrc and added the line to it
> export PATH=$HOME/bin:$PATH

Sorry pressed the send button by mistake: Here is the continuation

So I created the above file so that I could run scripts from ~/bin in dmenu.

These 3 steps I remember doing after which my .Xresources failed to
load on startup.

Now I already reverted steps 2 and 3, but even now that won't help.

These are the things I tried:

1) I changed to format of the colors from
*background to xterm*background or Xterm.VT100.background but that wont help.

2) I created a symlink .Xdefaults to .Xresources but that won't work either.

3) I also created ~/.xinitrc and added the line "xrdb -load
.Xresources" to it, but that won't help either.

Interesting thing to note is that only "xrdb .Xresources" will work
after boot. Not  "xrdb -merge .Xresources" neither "xrdb -overide
.Xresources"

Any help? And sorry for the reply to my own mail to complete my question!



-- 
Regards,
Anubhav Yadav
Imperial College of Engineering and Research,
Pune.


-- 
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+jf9agxeykw_ooedjqnqzxb-q2qecjutdnrezun0hzinbn...@mail.gmail.com