Which terminal

[pawRoot]

Code: Select all

debian@debian:~$ xrdb ~/.Xdefaults
/home/debian/.Xdefaults:47:37: warning: backslash-newline at end of file
 XTerm*VT100.Translations: #override \
                                      
/home/debian/.Xdefaults:48:49: warning: backslash and newline separated by space
 Shift Ctrl<Key>V: insert-selection(CLIPBOARD) \n\
                                                  
/home/debian/.Xdefaults:49:47: warning: backslash and newline separated by space
 Shift Ctrl<Key>V: insert-selection(PRIMARY) \n\
                                                
/home/debian/.Xdefaults:50:35: warning: backslash and newline separated by space
 Shift<Btn1Down>: select-start() \n\
                                    
/home/debian/.Xdefaults:51:38: warning: backslash and newline separated by space
 Shift<Btn1Motion>: select-extend() \n\

Code: Select all

! special
*.foreground:   #e7dfca
*.background:   #020202
*.cursorColor:  #e7dfca

! black
*.color0:       #040403
*.color8:       #a4d2d1

! red
*.color1:       #141310
*.color9:       #b6a87d

! green
*.color2:       #272520
*.color10:      #dbbdbd

! yellow
*.color3:       #403d36
*.color11:      #7eab83

! blue
*.color4:       #615d52
*.color12:      #e1b3dd

! magenta
*.color5:       #888374
*.color13:      #8ccd93

! cyan
*.color6:       #b6af9c
*.color14:      #64b86e

! white
*.color7:       #e9e2d0
*.color15:      #ccb871

xterm*loginshell: true

xterm*charClass: 33:48,36-47:48,58-59:48,61:48,63-64:48,95:48,126:48

xterm*faceName: Noto Mono Regular
xterm*faceSize: 11

xterm*selectToClipboard: true

XTerm*VT100.Translations: #override \
Shift Ctrl<Key>V: insert-selection(CLIPBOARD) \n\ 
Shift Ctrl<Key>V: insert-selection(PRIMARY) \n\ 
Shift<Btn1Down>: select-start() \n\ 
Shift<Btn1Motion>: select-extend() \n\ 
Shift<Btn1Up>: select-end(CLIPBOARD) \n\

[Head_on_a_Stick]

Code: Select all

debian@debian:~$ xrdb ~/.Xdefaults
/home/debian/.Xdefaults:47:37: warning: backslash-newline at end of file

The error is on line 47, column 37 in ~/.Xdefaults

[bw123]

I wanted to post full error, but i don't know how to copy text from Xterm

select the text with the mouse, then move the cursor to where you want it to go and shift-ins or click the middle mouse button.

It's not funny to waste people's time, this thread could help oters in the future if you can get it back on track.

I don't understand what colors you need to set, xterm by itself supports color? All I use is a very simple ~.Xresources for a couple of things. This file is read by default by debian when X starts. (see /etc/X11/Xsession.options)

Code: Select all

!xrdb -merge ~/.Xresources ----------------------------------------
!xterm settings ---------------------------------------------------

xterm*font: -misc-fixed-bold-r-normal--18-120-100-100-c-90-iso8859-1
xterm*background:               black
xterm*foreground:               white
xterm*VT100.geometry:     80x25

[pawRoot]

Code: Select all

debian@debian:~$ xrdb ~/.Xdefaults
/home/debian/.Xdefaults:47:37: warning: backslash-newline at end of file

The error is on line 47, column 37 in ~/.Xdefaults

Line 47:

XTerm*VT100.Translations: #override \

But it tells me nothing

[Head_on_a_Stick]

All I use is a very simple ~.Xresources for a couple of things. This file is read by default by debian when X starts

Not if there is a file at ~/.xinitrc

@pawRoot, remove the line, perhaps?

[pawRoot]

Code: Select all

debian@debian:~$ xrdb ~/.Xdefaults
/home/debian/.Xdefaults:48:49: warning: backslash and newline separated by space
 Shift Ctrl<Key>V: insert-selection(CLIPBOARD) \n\
                                                  
/home/debian/.Xdefaults:48:49: warning: backslash-newline at end of file
/home/debian/.Xdefaults:49:47: warning: backslash and newline separated by space
 Shift Ctrl<Key>V: insert-selection(PRIMARY) \n\
                                                
/home/debian/.Xdefaults:50:35: warning: backslash and newline separated by space
 Shift<Btn1Down>: select-start() \n\
                                    
/home/debian/.Xdefaults:51:38: warning: backslash and newline separated by space
 Shift<Btn1Motion>: select-extend() \n\

[Head_on_a_Stick]

Code: Select all

XTerm*VT100.Translations: #override \
Shift Ctrl<Key>V: insert-selection(CLIPBOARD) \n\ 
Shift Ctrl<Key>V: insert-selection(PRIMARY) \n\ 
Shift<Btn1Down>: select-start() \n\ 
Shift<Btn1Motion>: select-extend() \n\ 
Shift<Btn1Up>: select-end(CLIPBOARD) \n\

Remove _all_ of those lines, that will shut it up.

No idea what they are supposed to do but you've clearly got it wrong.

[pawRoot]

Yeah i will just get used to the other method

Thanks anyway

[bw123]

All I use is a very simple ~.Xresources for a couple of things. This file is read by default by debian when X starts

Not if there is a file at ~/.xinitrc

Are you telling me that pawroot figured out how to roll an xinitrc, or that i3 left out a simple xrdb -merge from it?

[Head_on_a_Stick]

Are you telling me that pawroot figured out how to roll an xinitrc, or that i3 left out a simple xrdb -merge from it?

Nope

I'm just telling you that if ~/.xinitrc exists then the `startx` command will _not_ read ~/.Xresources unless an xrdb -merge line is added to ~/.xinitrc

It's a subtle point but an important one.

[bw123]

Are you telling me that pawroot figured out how to roll an xinitrc, or that i3 left out a simple xrdb -merge from it?

Nope

I'm just telling you that if ~/.xinitrc exists then the `startx` command will _not_ read ~/.Xresources unless an xrdb -merge line is added to ~/.xinitrc

It's a subtle point but an important one.

Since you don't say for sure there is a ~.xinitrc I really don't see how it is an important point? Debian by default sets X up to use ~/.Xresources if found, so if a wm or other pkg didn't include it as a default setup I would consider that a bug.

Sorry to get off-topic, but telling the user to switch to Xdefaults instead of the default just seemed a silly suggestion to me.

[pawRoot]

Made a restart and all settings gone.
Could it be because i tried to make a .xinitrc file which execs openbox?

[Head_on_a_Stick]

Debian by default sets X up to use ~/.Xresources if found

Not if ~/.xinitrc exists.

If ~/.xinitrc exists then no files in /etc/X11/Xsession.d/ are read at all and the only configuration carried out is that specified in ~/.xinitrc

Detailed breakdown here: https://forums.bunsenlabs.org/viewtopic.php?id=3774

This is distinct from the situation is which ~/.xsession is used to specify the startup programs, as is the recommendation in startx(1):

Note that in the Debian system, what many people traditionally put in the .xinitrc file should go in .xsession instead; this permits the same X environment to be presented whether startx, xdm, or xinit is used to start the X session. All discussion of the .xinitrc file in the xinit(1) manual page applies equally well to .xsession. Keep in mind that .xinitrc is used only by xinit(1) and completely ignored by xdm(1).

This is by design — if the user wants "total control" then ~/.xinitrc should be used, otherwise ~/.xsession offers a degree of automation and consistency that some users prefer.

telling the user to switch to Xdefaults instead of the default just seemed a silly suggestion to me

Perhaps but it makes no practical difference to the problem in hand, either can be used.

I prefer ~/.Xdefaults because with ~/.Xresources `xrdb` must be used to effect any changes.

because i tried to make a .xinitrc file which execs openbox?

Ha!

Please post the ****ing file

[pawRoot]

It was just a .xinitrc file in ~/ with this inside:

exec openbox-session

But openbox didn't auto start anyway.

Oh and my f*** sound is suddenly gone aswell, now only HDMI works and the sound is choppy as hell.

[Head_on_a_Stick]

Try

Code: Select all

rm ~/.xinitrc
startx

Does everything work now?

[bw123]

telling the user to switch to Xdefaults instead of the default just seemed a silly suggestion to me

Perhaps but it makes no practical difference to the problem in hand, either can be used.

It's an interesting off-topic and i love to how how things work.
have you run into anything like this on debian specifically? Or can you report that it is not an issue?
https://wiki.archlinux.org/index.php/X_resources

* The older ~/.Xdefaults file is read when an X11 program starts, but only if xrdb has not been used in the current session. [1]

[pawRoot]

Try

Code: Select all

rm ~/.xinitrc
startx

Does everything work now?

I already did that, restarted and no sound, and the xterm settings gone aswell.

just wtf...

[Head_on_a_Stick]

have you run into anything like this on debian specifically? Or can you report that it is not an issue?
https://wiki.archlinux.org/index.php/X_resources

* The older ~/.Xdefaults file is read when an X11 program starts, but only if xrdb has not been used in the current session. [1]

As I mentioned before, if ~/.Xdefaults is used then ~/.Xresources must be deleted to prevent X resources being pre-loaded and stopping xterm from reading ~/.Xdefaults automatically.

Once ~/.Xdefaults is in place then `xrdb` should never be needed and `xrdb` is only run at startup if ~/.Xresources exists.

[pawRoot]

have you run into anything like this on debian specifically? Or can you report that it is not an issue?
https://wiki.archlinux.org/index.php/X_resources

* The older ~/.Xdefaults file is read when an X11 program starts, but only if xrdb has not been used in the current session. [1]

As I mentioned before, if ~/.Xdefaults is used then ~/.Xresources must be deleted to prevent X resources being pre-loaded and stopping xterm from reading ~/.Xdefaults automatically.

Once ~/.Xdefaults is in place then `xrdb` should never be needed and `xrdb` is only run at startup if ~/.Xresources exists.

But this is exactly what i did...

Removed Xresources, created Xdefaults
"Notified" xrdb.
And i didn't use any xrdb command since then.

[bw123]

As I mentioned before, if ~/.Xdefaults is used then ~/.Xresources must be deleted to prevent X resources being pre-loaded and stopping xterm from reading ~/.Xdefaults automatically.

Once ~/.Xdefaults is in place then `xrdb` should never be needed and `xrdb` is only run at startup if ~/.Xresources exists.

So changing to Xdefaults after running xrdb will not work without restarting the xserver? That would be a subtle point to mention in the advice.