Discussion in 'OT Technology' started by jDMJeRk, Jun 19, 2008.
.... How do I edit it in command line
I know its in there but don't you have to use something to edit it in command line?
sudo nano -w /etc/X11/xorg.conf
All I did was delete the lines that I added...
Same problem... I tink I fucked it up good this time lol
you made a backup of the file before editing, right? restore it.
what error is it giving you?
I didn't make a back up.. I found possibly problem....
it just booted up
yay I fixed it
I was trying to fix the mouse cursor on my PowerBook, its super gh3y.
He was having probs with X11 (it wouldn't run) and gedit requires X11 to be working.
Duh, but the thread title said "I fucked up xorg.conf", so I thought he fucked up something in that file
yes and xorg.conf is the config file for the X server.... so if he fucked that file up, there's a 99.999% change he's in a command line. And to add insult to injury, he even specified that he WAS in a CLI:
vi > nano
no. someone that has to ask how to edit a text file in a CLI is not going to want the learning curve of vi. but at least vi is a cli editor, so the suggestion, although mildly inappropriate, would have at least been technically correct.
The learning curve isn't very steep for the basics. i to type, escape to stop typing. ':wq' when you're done. Think "insert" and "write-quit" and it's easy to remember. Write down the three letters if it's difficult.
The more advanced features are what make vi much more productive than nano, and yes there is a slightly stronger learning curve involved there, but everyone needs to start somewhere. Begin with the basics and learn the rest as you need them.
Wirelessly posted via wap.offtopic.com (Mozilla/2.0 (compatible; MSIE 3.02; Windows CE; PPC; 240x320) BlackBerry8703e/4.1.0 Profile/MIDP-2.0 Configuration/CLDC-1.1 VendorID/105)
Hehe, I started to post a recommendation for vi and decided the OP would probably get himself in more trouble with it.
While normally I would agree I don't here. The last thing you want when trying to fix a borked config is a frustrating learning curve. Now that its fixed I encourage expirimentation with VI
Yeah P07r0457 thanks for the help again .. you fixed my problem and couldn't have explained it better. I'm new to linux command line and didnt know where to turn. Although I could have searched on the forums and I know the difficulty of this matter doesn't even rank its self on a scale from 1-10, being clueless to this situation I figured I'd ask OT...
And lets not forget, the OP was who again? Oh you meant TS, I forgot jk
anyway, now that you've gotten your shit working, you should learn vi. it is a very powerful text editing tool that is available in all flavors of *NIX. so, if you want to actually start to understand Linux beyond the GUI, then you should get into some of these command line tools.