[Tutor] IDLE Usage - was Interpreter Restarts

[jim stockford]

change "small" to "large" and you're right.
Vim is Vi improved.
Any tutorial or reference on Vi ought to work
for Vim.

On Jul 17, 2007, at 10:09 AM, Sara Johnson wrote:

> I initially thought Vim was sort of the same as Vi, just a few small 
> differences or upgrades.  Or have I got that confused?
>  
> Sara
>
> ----- Original Message ----
> From: Tiger12506 <keridee at jayco.net>
> To: tutor at python.org
> Sent: Tuesday, July 17, 2007 12:33:54 PM
> Subject: Re: [Tutor] IDLE Usage - was Interpreter Restarts
>
> Yeah. But she's running Windows.
> Perhaps vim is scary to some Windows users.
> (I thought it was scary and annoying. Are all those ~ characters 
> really in
> the file or not?
> I kept second guessing the editor.)
>
> --Sara, could you give an example of how it doesn't work?
>   Just what happens? Just what doesn't happen?
>
> You say you have Python 2.3 installed...
>
>
> > Greetings,
> >
> > I use an editor called 'vim' on GNU/Linux.
> > I invoke vim on the command-line by typing: vi
> > (vi is a link to /usr/bin/vim)
> > In my home directory I have a vim config file
> > named .vimrc (that is: dot_vimrc [the dot makes it hidden]).
> > The .vimrc file has some things in it that do some nice stuff
> > for editing Python files; such as syntax highlighting, line numbers,
> > indenting, and also runs Python when I press the F2 function key.
> > I run vim in an X ternminal called Konsole. I can also run  it
> > from the command-line in any tty.
> >
> > Okay, here it is. Just copy/paste this into an editor, and save it 
> as:
> > .vimrc
> >
> > -------------8<------Cut Here-------->8---------------
> > " .vimrc
> > "
> > " Created by Jeff Elkner 23 January 2006
> > " Last modified 2 February 2006
> > "
> > " Turn on syntax highlighting and autoindenting
> > syntax enable
> > filetype indent on
> > " set autoindent width to 4 spaces (see
> > " http://www.vim.org/tips/tip.php?tip_id=83)
> > set nu
> > set et
> > set sw=4
> > set smarttab
> > " Bind <f2> key to running the python interpreter on the currently 
> active
> > " file.  (curtesy of Steve Howell from email dated 1 Feb 2006).
> > map <f2> :w\|!python %<cr>
> > -------------8<------Cut  Here-------->8---------------
> >
> > To use it, just type: vi myCode.py
> > (If you don't have a link named vi that points to /usr/bin/vim,
> > you'll have to type vim or /usr/bin/vim to get it going...
> > since I don't have any idea what you're working at, I can't say.)
> >
> > Once you're in vim, looking at your code, press F2 to run it.
> >
> > I understand that Emacs also does Python! =)
> > But I won't go there... I don't do Emacs.
> > --
> > bhaaluu at gmail dot com
> >
> > On 7/17/07, Luke Paireepinart <rabidpoobear at gmail.com> wrote:
> >> A lot of Python programmers
> >> use Vi for writing their code.  do you have access to that through 
> SSH?
> >> I'm not quite sure what you mean by "SSH editor."
> >> -Luke
> >> _______________________________________________
> >> Tutor maillist  -  Tutor at python.org
> >> http://mail.python.org/mailman/listinfo/tutor
> >>
> > _______________________________________________
> > Tutor maillist  -  Tutor at python.org
> > http://mail.python.org/mailman/listinfo/tutor
> >
>
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> http://mail.python.org/mailman/listinfo/tutor
>
>
> Got a little couch potato?
>  Check out fun summer activities for 
> kids._______________________________________________
> Tutor maillist  -  Tutor at python.org
> http://mail.python.org/mailman/listinfo/tutor