[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdevelop (Re: Proposal to plan for "Milestone Releases" on the
From:       Alexander Dymo <adymo () mksat ! net>
Date:       2006-01-26 0:27:55
Message-ID: 200601260227.55699.adymo () mksat ! net
[Download RAW message or body]

On Thursday 26 January 2006 01:44, David Faure wrote:
> I would need kdevelop to have support for emacs-lisp, or to have at least
> all the features implemented in kdesdk/scripts/kde-emacs/ (good luck!),
> but the latter would be less flexible for future extensibility...
Ok, is it essential for you to have support for lisp. Will other languages
(lua, python, whatever...) fit you? The question is whether it is important
to have emacs-lisp or to have powerful scriptability for an IDE.

> For the emacs-lisp support, I know that it's a huge amount of work - Kalle
> and I started on that one day, extracting the lisp engine and basic
> functions out of xemacs, and we got to the point where a katepart could run
> a few simple scripts, but the code was painful, mainly because kate (and
> the KTextEditor interface) is line+character oriented, whereas emacs works
> with linear positions in one buffer... interestingly enough, Scribe also
> works that way, so maybe someone could update that interfacing based on
> Qt4's QTextEdit...
I must admit I've never looked carefully at emacs-lisp stuff. Could you please
describe in few words what tasks do you accomplish using lisp?

> Anyway - many ideas, but little time for them.
Yes, but it's high time for KDevelop to adopt new ideas. Old ones do
not attract people anymore ;)
[prev in list] [next in list] [prev in thread] [next in thread]