Well that is definitely an interesting approach. If we had a new project that
used much of the Kate Kpart as possible for things like network transparency
and could somehow get Emacs like Guile/whatever support in it as well we
could mimick Emacs to a good degree.
It would never truly be emacs though and may end up being a "red headed
stepchild" project. Some may scoff at the bastardization of their favorite
editor.:)
Sorry but I don't think the religious ones would stand for it. :)
I'd be willing to try if I can clear some time up off my plate. KDE isn't my
only Open Source Project but its a big chunk of what I do. :)
Dave
On Tuesday 07 May 2002 07:52 am, Simon Josefsson wrote:
These, and the Qt widgets to achieve anti-aliasing etc, are rather
far-fetching goals. Rewriting XEmacs to support Qt widgets to display
data and KIO slaves to retrieve data is a big modification with lots of
interaction with the multibyte support in XEmacs. IMHO it is probably
easier to rewrite XEmacs from scratch supporting these things natively
than to extend XEmacs with this functionality.
The latter might actually be an easier approach. Adding GUILE or Common
Lisp script support to VIM or KATE could be the way forward.
On Tue, 7 May 2002, David Leimbach wrote:
> Will Qt Xemacs be able to exploit things like KIO_xxx? Network
> transparency in your editor kicks butt IMO. Kate will still be more
> flexible in this respect. Yes I know emacs can edit files via ftp. But
> what about SSH [KIO_FISH] and others? Maybe someday I will write that
> KIO_CVS stuff [experimentally at least] and then you can make little
> changes in CVS by "poking" instead of updating and recommitting. [Slow
> net connection people would like this???]
>
> Anyway its just a thought. I know lots of people would like Emacs to be
> as integrated as Kvim is.
>
> On Monday 06 May 2002 06:53 pm, Rodolfo Conde Martinez wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On Monday 06 May 2002 03:47, David Faure wrote:
> > > On Friday 03 May 2002 01:51, Rodolfo Conde Martinez wrote:
> > > > But as you said, XParts is still not fully operational and i would
> > > > like more a KPart xemacs that a xpart....
> > >
> > > Read a bit about XPart.
> > > And XPart components "looks" like a KParts component to the
hosting
> > > application, that's the whole point of it - no change required in the
> > > application, if it already supports embedding KParts components.
> >
> > i see, thats ok but i think having a native qt xemacs would be the
> > best, in that way xemacs can take full advantage of all the Qt stuff,
> > antialising, Xft extensions, themes, etc. and i guess having a native
> > Qt xemacs, from there it would be easy to do a Kpart for kde.....of
> > course i didnt mean XParts was bad, i just would prefer a native xemacs
> > Qt (i dont have TTF fonts inside xemacs, i had to install the xfstt
> > server to have'em
> >
> > :(, but lately that doesnt work, so im stuck with ugly fonts.....) and
> > : im
> >
> > really dying to see xemacs inside KDevelop :):)....
> >
> > Cheers...
> >
> >
> > - --
> > rcm.
> > rcm(a)gmx.co.uk
> > GPG Public Key:
http://ada.fciencias.unam.mx/~rconde/rodolfo_gpg.txt
> > ICQ 118193727
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.0.6 (GNU/Linux)
> > Comment: For info see
http://www.gnupg.org
> >
> > iD8DBQE81xd2x2Sktruwba0RAuz0AKDO39hoHxnlME6F2zyXNEjxX/f9yACeK2Gq
> > mz4CnWEc9nRvZ0Ch8kqppBQ=
> > =DZbP
> > -----END PGP SIGNATURE-----
> >
> > >> Visit
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> > >> unsubscribe <<
>>
>> Visit
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
>> unsubscribe <<