[Haskell-cafe] Re: Best Editor In Windows
gcross at phys.washington.edu
Tue Nov 3 15:47:40 EST 2009
The problem with Leo is that although there are rarely performance
problems when navigating and editing the outline, the text pane can be
very slow at times when using the Tk-based GUI --- even on modern
hardware --- because the syntax highlighter is written in Python.
(Incidentally, as much as I love Leo, I also hold it up as an example
of how slow scripting languages aren't always "fast enough" as their
proponents claim. :-) )
There are two solutions to this: First, you can use the Qt-based Leo
GUI, which uses the native C++ colorizer built into QtScintilla, which
I have never had any performance problems with. Since you
(reasonably) really like haskell-mode in Emacs, though, you can
alternatively use the Emacs plugin so that you end up using Leo to
navigate through your code to the chunk that you want to edit, and
then using Emacs to do the actual editing. This might sound like an
awkward setup, but I actually find that navigating in this way
requires much less mental energy than scanning through multiple flat
files to pick out the code that you want to edit next, and the plugin
makes this type of workflow fairly painless.
Viewing Leo as a "meta-editor" is a good way to think about it.
On Nov 3, 2009, at 12:26 PM, Gour wrote:
> On Tue, 3 Nov 2009 03:15:03 -0800 (PST)
>>>>>>> "Philippos" == <phi500ac at yahoo.ca> wrote:
> Philippos> I tryed it, and noticed that it is very slow, compared both
> Philippos> with Emacs, TextPad, and Emerald.
> Is it usable (btw, what hardware?) or just slow?
> Philippos> I tryed also leksah, but it is always complaining about
> Philippos> something missing in Pango, although it works fine.
> I'd prefer to stay with Emacs and its haskell-mode as editor-tool, but
> Leo might come handy as meta-editor.
> Gour | Hlapicina, Croatia | GPG key: F96FF5F6
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
More information about the Haskell-Cafe