| Trolltech Home | Qt-interest Home | Recent Threads | All Threads | Author | Date | |
| All threads index page 4 | |
<<< text/html: EXCLUDED >>>
You might find it easier to just fork and call emacs/vi with a temp file that you can suck data out of after the user edits it. just the way i'd do it -James -------------------------------------------- "Never trust a man who can count to 1024 on his fingers" -------------------------------------------- On Jul 13, 2004, at 10:00 AM, Scott Bloom wrote: > Does anyone know of (or any consultant available to work on) a VI QT > widget and a Emacs QT widget? > I do NOT mean/want emacs the environment (ie client/server tie ins, > full os calls etc) just the editor portion to replace out > QTextEdit. > > > > Scott
>Does anyone know of (or any consultant available to work on) a VI QT >widget and a Emacs QT widget? >I do NOT mean/want emacs the environment (ie client/server tie ins, full >os calls etc) just the editor portion to replace out >QTextEdit. KDE sports a VIM KPart you can choose to use as your editor of choice. Maybe you can look at that one? André -- [ signature omitted ]
I need it to look/feel integrated into the tool. I already have the ability to fork the programs out. However, in our current QTextEdit derived editor, we do a lot of interaction That they want to be able to do in emacs/vi Scott -----Original Message----- From: James Sarrett [mailto:jsarrett-co@appliedminds.com] Sent: Tuesday, July 13, 2004 10:06 AM To: Scott Bloom Cc: qt-interest@trolltech.com Subject: Re: VI/Emacs QT widget You might find it easier to just fork and call emacs/vi with a temp file that you can suck data out of after the user edits it. just the way i'd do it -James -------------------------------------------- "Never trust a man who can count to 1024 on his fingers" -------------------------------------------- On Jul 13, 2004, at 10:00 AM, Scott Bloom wrote: > Does anyone know of (or any consultant available to work on) a VI QT > widget and a Emacs QT widget? > I do NOT mean/want emacs the environment (ie client/server tie ins, > full os calls etc) just the editor portion to replace out > QTextEdit. > > > > Scott
Scott Bloom wrote: > I need it to look/feel integrated into the tool. I already have the ability to fork the programs out. > > However, in our current QTextEdit derived editor, we do a lot of interaction > That they want to be able to do in emacs/vi Well, the way that this is done with Sun Studio is to have the choice between a) builtin editor b) xemacs c) gvim. A+ Paul