Lowell Tackett wrote: > The environment [OS} of choice can do a lot to expand/enhance the > capabilities of an editor. I fell upon Vim from the beginning, and > stayed with it for its' rich palate of features and adaptability (and > of course, the often...and exhilarating "oh, Vim can do that!"). But > beyond that, the Linux platform I work within offers its own dimension. > > Generally, I will split a [terminal] screen into two (or even 3) > virtual screens with bash's 'screen' workhorse, and from there I have > in front of me [perhaps] a; 1) script edit screen, 2) interactive > screen, and 3) script-launching screen...all on the same physical monitor. > > For me, that combination creates an awfully rich & deep working > canvas. The whole...is at least as great as the sum of its' parts. >
LOL Any modern editor can do that! In SPE I'm just now working in 7 scripts at a time (a few of them just for checking stuff) each in it's own tab, a python shell, locals window, output window, to do window, procedure index, object index, notes window, directory explorer window, each in its own tab. And on top of that I can execute a program and debug it through winpdb, test regular expressions, check code with pyChecker, run in a terminal the current script with or without arguments, design a GUI with wxGlade or XRC, and many other actions all a menu choice away. And nobody would claim this is extraordinary. Vim has other advantages for an expert user (but you have a steep learning curve) but what you mention are hardly outstanding issues nowadays.
_______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
