[SlugLUG] running vi

[Thomas Leavitt]

Here's the difference between pico and nano:

nano  is  a small, free and friendly editor which aims to replace Pico,
       the default editor included in the non-free Pine package.
Rather  than
       just  copying  Pico's  look and feel, nano also implements some
missing
       (or disabled by default) features in Pico, such as "search and
replace"
       and "go to line number".


And, of course, there's joe ...

 JOE  is a powerful ASCII-text screen editor.  It has a "mode-less" user
       interface which is similar to many user-friendly PC editors.
Users  of
       Micro-Pro's  WordStar or Borland's "Turbo" languages will feel at
home.
       JOE is a full featured UNIX screen-editor though, and has many
features
       for editing programs and text.

       JOE also emulates several other editors.  JSTAR is a close
imitation of
       WordStar with many "JOE" extensions.  JPICO is a close imitation
of the
       Pine  mailing  system's  PICO  editor,  but  with  many
extensions and
       improvements.  JMACS is a GNU-EMACS imitation.  RJOE  is  a
restricted
       version  of  JOE,  which allows you to edit only the files
specified on
       the command line.

       Although JOE is actually five different editors, it still
requires only
       one  executable,  but  one  with five different names.  The name
of the
       editor with an "rc" appended gives the  name  of  JOE's
initialization
       file, which determines the personality of the editor.


Eric Carter wrote:
> I had to run them both to remember which was which.... apparently neither
> because pico is just a symlink to nano. I was rather unimpressed with
> my 23
> second nano experiance. I noted that spell checking (atleast that's
> what I
> think it was) didn't work. Convinently the quit hotkey is always
> displayed
> on screen. My vote is for nano... since that's the only one I've seen. :)
>
> EC
>
> On 9/30/06, Thomas Leavitt <thomas at thomasleavitt.org> wrote:
>>
>> pico vs. nano wars, anyone? :)
>>
>> thomas
>>
>> Eric Carter wrote:
>> > So far this thread is shockingly short on emacs users. Although
>> that's a
>> > great story Thomas. :)
>> >
>> > EC
>> >
>> > P.S. The true target of editor wars is those poor saps who still use
>> > pico.
>> >
>> > On 9/30/06, Thomas Leavitt <thomas at thomasleavitt.org> wrote:
>> >>
>> >> vi made me a million dollars (although it didn't help me keep it)
>> >>
>> >> i took a unix class at Cabrillo in the early 90s - the prof gave me a
>> >> free pass after a few weeks, because I soaked it all up like a sponge
>> >> (already having been exposed to a unix-like command line via the
>> Amiga
>> >> and a PrimeOS miniframe at a prior school helped)... so I spent the
>> rest
>> >> of the semester hanging out in the psych lab with a buddy, working
>> >> through the vilearn tutorial (all the way through cutting and pasting
>> >> with multiple buffers) on this gigantic creaky VAX running BSD... the
>> >> tutorial's extensive training in how to use regular expressions
>> via use
>> >> of "ex", etc., put me in good stead when I started my web hosting
>> >> service and found out about this new programming language called
>> >> Perl. :)
>> >>
>> >> thomas
>> >>
>> >> Eric Carter wrote:
>> >> > lol. Thanks Peter. I probably should have done that myself. ;)
>> >> >
>> >> > *equips his +5 Ruby Armor of Flame Resistance*
>> >> >
>> >> > Ok, I'm ready now. :)
>> >> >
>> >> > EC
>> >> >
>> >> > On 9/30/06, Peter Belew <abcruzww at gmail.com> wrote:
>> >> >>
>> >> >> Hehe -
>> >> >>
>> >> >> Discussing editors, as you know, is like discussing religion or
>> >> politics
>> >> >> in the 'wrong' place!
>> >> >>
>> >> >>
>> >> >> (I made this the start of a new thread).
>> >> >>
>> >> >> :)
>> >> >>
>> >> >> Peter
>> >> >>
>> >> >> On 9/30/06, Eric Carter <Ecnassianer at greenstorm.net> wrote:
>> >> >> > Incase you run into vi again:
>> >> >> >
>> >> >> > $vim /etc/apt/sources.list
>> >> >> > 1) Use the up and down arrows (or j and k) to scroll to the line
>> >> you
>> >> >> want to
>> >> >> > edit
>> >> >> > 2) Press i to <i>nsert text (or your choice of a, A, I, o, O,and
>> >> >> perhaps
>> >> >> > others)
>> >> >> > 3) Type what you want as you would anywhere else
>> >> >> > 4) Esc to stop editing text
>> >> >> > 5) :wq <enter> to save and quit.
>> >> >> >
>> >> >> > vi gets a lot clearer once you realize it has 3 modes. ( Hotkey
>> >> mode
>> >> >> (which
>> >> >> > you start in), editing mode (you get in with i out with ESC) and
>> >> >> command
>> >> >> > mode (open that with : from hotkey mode).
>> >> >> >
>> >> >> > (I wonder if I just started an entirely different interesting
>> >> debate.)
>> >> >> >
>> >> >> > EC
>> >> >> >
>> >> >> > On 9/29/06, Sean Kellogg <skellogg at gmail.com> wrote:
>> >> >> > >
>> >> >> > > On Friday 29 September 2006 15:52, Ignacio Solis wrote:
>> >> >> > > > Choose the "Edit sources manually".  You'll be given an
>> editor
>> >> >> (nano?)
>> >> >> > > with
>> >> >> > > > the sources file open.  Just type in the sluglug address.
>> >> >> > >
>> >> >> > > That sounds familiar.  But I seem to remember the reason I
>> never
>> >> >> used
>> >> >> this
>> >> >> > > route is that the default editor is vi, which I find about as
>> >> >> > > incomprehensible as emacs.  If they are using nano now as a
>> >> default
>> >> >> than
>> >> >> > > thank goodness.
>> >> >> > >
>> >> >> > > -Sean
>> >> >> > >
>> >> >> > > --
>> >> >> > > Sean Kellogg
>> >> >> > > c: 831.818.6940 e: skellogg at gmail.com
>> >> >> > > w: http://blog.probonogeek.org/
>> >> >> > >
>> >> >> > > So, let go
>> >> >> > > ...Jump in
>> >> >> > > ...Oh well, what you waiting for?
>> >> >> > > ...it's all right
>> >> >> > >   ...'Cause there's beauty in the breakdown
>> >> >> > > _______________________________________________
>> >> >> > > Sluglug mailing list
>> >> >> > > Sluglug at sluglug.ucsc.edu
>> >> >> > > http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>> >> >> > >
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > Sluglug mailing list
>> >> >> > Sluglug at sluglug.ucsc.edu
>> >> >> > http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >>
>> >> >
>> >> >
>> >>
>> ------------------------------------------------------------------------
>> >> >
>> >> > _______________________________________________
>> >> > Sluglug mailing list
>> >> > Sluglug at sluglug.ucsc.edu
>> >> > http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>> >> >
>> >>
>> >> _______________________________________________
>> >> Sluglug mailing list
>> >> Sluglug at sluglug.ucsc.edu
>> >> http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>> >>
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Sluglug mailing list
>> > Sluglug at sluglug.ucsc.edu
>> > http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>> >
>>
>> _______________________________________________
>> Sluglug mailing list
>> Sluglug at sluglug.ucsc.edu
>> http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sluglug mailing list
> Sluglug at sluglug.ucsc.edu
> http://sluglug.ucsc.edu/cgi-bin/mailman/listinfo/sluglug
>