[PyKDE] Editor survey

Greg Fortune lists at gregfortune.com
Thu Oct 3 22:26:01 BST 2002


On Thursday 03 October 2002 12:27 pm, Boudewijn Rempt wrote:
> On Thursday 03 October 2002 21:05, Frederick Polgardy Jr wrote:
> > On Thursday 03 October 2002 10:40 am, Greg Fortune wrote:
> > > It's pretty slick and I used it as my primary editor for several weeks
> > > but ended up going back to Nedit.
> >
> > Yeah, I keep doing the same. :-)  I'm not *extremely* concerned about it
> > starting up as fast as Nedit -- Nedit starts up *reeeeally* fast.  I've
> > tried to use kwrite for awhile, and the startup time doesn't bother me
> > nearly as much as other stuff about it (e.g. complete lack of features). 
> > I like the Nedit scripting capability, but I'm trying to keep the number
> > of scripting languages I know to a minimum.  Too little free space in my
> > head as it is. :-)  (Same reason I won't learn elisp for Emacs.)  That's
> > why a Python-scriptable editor would be perfect.  But you're right that
> > it has no hope of starting as fast as Nedit does.
>
> Nedit has one big disadvantage -- one that made me switch to XEmacs
> completely. Motif applications can't handle a utf-8 locale. The file
> dialogs simply don't work anymore. Anyway, since I practically live in
> my editor, it doesn't matter much to me how fast it starts.

I live in my editor too, but I never have a window up long enough for it to 
fully initialize into memory ;o)  I tend to pull a file up, make a bug fix, 
close it out and go kill off another bug.  Of course, I do keep new files up 
for quite a while usually.  Maybe I need to have a regular editor and a bug 
hunting editor...

Oh, right, and the other reason I never switched fully over...  I couldn't 
make my fingers stop typing nedit :)

>
> I'd be using Kate if it included a macro language, I've begin writing an
> editor in pure PyQt -- down to the bit that puts the glyphs on screen,
> but I wound up doing other things. And the example application in my
> book on PyQt is an editor, but that's simply a wrapper for QMultiLineEdit.
>
> If I can get Qt-Scintilla working from Python, I'd probably wind up writing
> my own anyway... It's fun.

he he, I can't say I'm really too surprised ;o)




More information about the PyQt mailing list