xterm & startx fail to start after failed yeahconsole configuring
 

all i was trying to do was to get the terminal in yeahconsole to use the configuration for yeahconsole, and use either my .Xdefaults (so the background was black instead of glare) or use mrxvt, and fiddled with a few bits n bobs, but now....

i get this from trying to start xterm:

and this trying to start mrxvt
running ". /etc/X11/xdm/Xresources" and ". /usr/bin/startx" when signed in with "su -l" seems to be the culprit. (maybe... it was a blind stab in the dark in the first place, and equally blind trouble shooting the results of the blind stab)

hrmm... re-sourcing with a "." on components of X, while running X, is probably not savvy i'm thinking in hindsight. mighta been what i'd done that caused it. it certainly seems that something is thinking a different user owns or is trying to run something here. :/

atempting to re-re-source as user hasnt sorted it, :/ so, er.

... i'm wondering if telling su to re-source it again with -c (iirc) to execute the command as normal user, will (i) fix it, (ii) make things worse, or if i'm (iii) barking up completely the wrong tree.

i dont want to proceed any further without knowing what i'm doing. ...too much blind gung-ho hav-a-go already.

for what it's worth, "echo $DISPLAY" output is restarted x to see what that does and as suspected, no joy.

startx now shpeals "No protocol specified" at me over and over, in clusters of three, punctuated by two dots, and eventually (likely after me having pressed Ctrl-C a few dozen times), it then says:
can anyone see what i've done wrong to get that result?

and how to resolve it?

#|