Sorry, James M., about not including you with Eric - and all who have fantastically made contributions to the beauty that is OO.Regardless of which editor one invokes - whether it be pico, nano, or vi - the PDF manual does not be a little flexible. Dwight A. Tkatschow's post of Mon, 4 Sept. 2006 seemed to indicate that, at the time, he may or may not have known what a nano was, and the PDF installation manual for the Mac port version tended to be rather inflexible on that point.Or, it would best to try to use an editor that may be native to one particular flavor of an OS - knowing that nano may have been with Mac OS 10.4, while pico may still have been a part of Mac OS 10.3.9. Or one can use vi, which I just downloaded just now.But telling someone to type in "sudo nano..." without telling them WHY was the unnerving part for me, until I realized that I could substitute "pico."So when the manual does get updated, I would suggest it be re-worded for flexibility's sake - for the uninitiated newbies like me.Having learned to make the changes to the xinitrc file by whatever method, I got rid of the unwelcome window. Now, it is even easier to use OO, because I can use the "command-O" sequence rather using "control-O" to open files.I have another computer in my network that runs Win2K, but having to use "control-O" on a Mac is just plain unsettling, especially after switching from my Windows PC.Thanks for setting me straight, James, on the interchangeability of the various editors one can use on files like /etc/X11/xinit/xinitrc.Thanks to Uwe Altmann as well.Original Message:Date: Sun, 25 Mar 2007 13:12:26 -0700 (GMT-07:00)From: James McKenzie <[EMAIL PROTECTED]>Content-Type: text/plain; charset=UTF-8Subject: [mac] 1.6 How to get rid of the Xterm that starts without asking ?There is more than Eric here.Second, pico is just another name for nano. I use vi toedit my files and always will.As to updating the PDF, I don't know who created it but it can be updated.James McKenzie--Sincerely,Chris Skurkey
