No
you aren't missing anything.
You will only have vim if you choose to install it.
It was just an example of a text editor. It could
just as well have been Scite - or even Notepad!
The point wasn't about vim per se - that just
happens to be my favourite editor - but really
about the way of working with 3 separate windows.
Really it was just to show that you don't necessarily
need to use an all-in-one IDE like Pythonwin or IDLE,
these are just conveniences for programmers and
beginners prefer to use them. But its perfectly
possible to get along with 3 windows, each running
a specific tool.
You can continue using Pythonwin or try a different
approach, it is entirely a personal choice. There
is no right or wrong way to do it.
Alan Gauld
Author of the Learn To Program website
http://www.alan-g.me.uk/
From:
Wayne Watson <sierra_mtnv...@sbcglobal.net>
To: Alan Gauld
<alan.ga...@btinternet.com>
Sent: Monday, 2
February, 2009 1:00:15 PM
Subject: Re: [Tutor]
IDLE vs PythonWin
I must be missing something here. To my knowledge I am
not using vim at all. Is it the default editor for pythonWin?
--- On Sun, 2/1/09, Alan Gauld <alan.ga...@btinternet.com>
wrote:
From:
Alan Gauld <alan.ga...@btinternet.com>
Subject: Re: [Tutor] IDLE vs PythonWin
To: tutor@python.org
Date: Sunday, February 1, 2009, 3:15 PM
"Wayne Watson" <sierra_mtnv...@sbcglobal.net> wrote
> Hi, sorry, but I have no idea what vim is,
Yes, its just a text editor that runs in its own window.
Its a very very powerful text editor, one of perhaps 3 or 4 that are
universally used by professional programmers
on any operating system they may need to work with, and specifically designed
for writing programs.
But you could substitute the name of any text editor.
> I'd still like to know why pythonwin prints almost completely blank
pages.
Me, too, I checked and it works fine for me.
One option is to try a different print driver - it could be a bad interface
between
vim and the printer. But thats unlikely...
> vim=vi(m), linux??
vim = vi improved.
vi was developed by Bill Joy(founder of Sun Microsystems) while at university
in the late 1970s or very early 80s. It was
desuigned to make it easier to edit programs and take advantage of the brand
new "glass teletypes" (ie video monitors) that weere becoming
available. It ran on Unix and fast became the standard Unix editor.
Emacs was being built at around the same time on Digital computers as a set of
macros on top of the Teco editor (The name stands for Editining Macros) and when
these became popular it was turned into a fully fledged editor. But because it
came from a bunch of Lisp programmers it was almost immediately made cross
platform and became popular across a whole bunch of programmers. And because it
had a Lisp macro lamnguage it was easy to extend. (A lot more than vi!) Both vi
and emacs are extremely
popular but work in almost diametrically opposite ways
and so polarise opinions. This regularly leads to "Editor wars"
between programmers on Usenet :-)
Personally I useed both on Unix and liked both. When I moved to Windows Emacs
couldn't perform all its tricks, whereas vi just worked as usual so
gradually I stopped using emacs.
Thebn I found vim wjhich added a whole bunch of the "missing"
features of vi plus full GUI support(mice etc) and vim is now my standard editor
for serious programming whether it be in Lisp, C, Python or HTML.
> I think you may have misunderstood Alan.
Yes, the description below is correct.
I have 3 separate windows open. I use Alt-Tab to cycle between them. In both
the Python and OS windows I use up/down arrow to cycle between previous
commands.
> Then he saves his code in vim and runs the script in the shell (in
Ipython you'd use the magic function %run,
In vim I could use the :! command to run it within vim, but I prefer to keep
the errors etc plus the previous outputs all available in a separate window.
HTH,
-- Alan Gauld
Author of the Learn to Program web site
http://www.freenetpages.co.uk/hp/alan.gauld
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
|
