I totally agree , My choice is nano (still use it even if a gui is running )...mainly due to being a newb when starting with Gentoo (and it being the only option at the time on the 1.2 install disk) it is IMHO the closest in use to your common gui based text editors ...
Cheers Dale. Quoting Brad Beveridge <[EMAIL PROTECTED]>: > For text config files I always use VIM. Everyone should be familiar with > a console based plain text editor (vim, nano, emacs, joe, etc, etc) so > that if you need to edit config files by hand when you have no X server > you won't be totally lost. By familiar I mean, able to edit & save files > :) > Also, I suggest that you are familiar with a common editor, so that in a > reduced environment (rescue disk) you can still be effective. > > Brad > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, 18 June 2003 4:23 p.m. > > To: [EMAIL PROTECTED] > > Subject: Re: Parse error in /etc/make.conf ? > > > > > > mmm didnt word that to well ...basically a raw txt file uses > > a different "character" to define these ,where AFAIK the > > likes of Kate and MSWord which save in a "document" format > > define these different ....resulting in an app trying to pull > > strings from what is supposed to be a raw text file having > > issues enterpruting the likes of spaces and returns on the > > code or text. > > > > Cheers > > Dale. > > > > Quoting "[EMAIL PROTECTED]" > > <[EMAIL PROTECTED]>: > > > > > Yeah 2 good ones are Kate and MS Word ....apparently > > something to do > > > with the encoding when the likes of page breaks and "returns" are > > > saved to file ... > > > > > > Cheers > > > Dale. > > > > > > Quoting Nick Rout <[EMAIL PROTECTED]>: > > > > > > > I saw something in the forums.gentoo.org about illegal > > characters in > > > > make.conf giving this error, something about character encodeing, > > > which > > > > I do NOT understand. > > > > > > > > So, it may have been your editor? > > > > > > > > On Wed, 18 Jun 2003 15:16:27 +1200 (NZST) > > > > [EMAIL PROTECTED] wrote: > > > > > > > > > If you want a "clean" make.conf let me know and I can send you > a > > > copy, > > > > youll > > > > > just have to alter the use varibles and c flags etc ...or > > > > alternatively a > > > > > remerge of baselayout will give you a clean one ;-) ...... > > > > > > > > > > Cheers > > > > > Dale. > > > > > > > > > > > > > > > Quoting Steve Brorens <[EMAIL PROTECTED]>: > > > > > > > > > > > Well, things are working again (whew!) > > > > > > > > > > > > I'm not sure what the ultimate cause of this 'bad' make.conf > > > > > > was, > > > > but > > > > > > here's the lines (scattered throughout the file) that > > I needed > > > > > > to > > > > rem > > > > > > out to get things working again. > > > > > > > > > > > > (a) What's wrong with these, and (b) How could they have got > > > > cobbled? > > > > > > > > > > > > # PS1=\[\033[01;31m\]\h \[\033[01;34m\]\W \$ \[\033[00m\] # > > > > > > LESSOPEN=|lesspipe.sh %s # > > > > > > KONSOLE_DCOP_SESSION=DCOPRef(konsole-6502,session-1) > > > > > > # KONSOLE_DCOP=DCOPRef(konsole-6502,konsole) > > > > > > > > > > > > - steve > > > > > > > > > > > > I'd not been fiddling with any of these lines, and in > > retrospect > > > I > > > > > > doubt > > > > > > that the ALSA stuff was related - it was just that I > > ran emerge > > > > > > directly after that. > > > > > > > > > > > > > > > > > > ========================================================= > > > > > > http://www.commarc.co.nz > > > > > > > > > > > > (This e-mail has been scanned by MailMarshal) > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > >
