#Best haskell ide how to
I still haven’t learned how to use Haskell’s debugger so I really can’t tell how this works. Nevertheless EclipseFP still has the advantage of HLint integration.ĭebugging. UPDATE: Leksah can also underline errors directly in the code. Nevertheless, another point goes to EclipseFP since it is able to mark the errors directly in the source code and it can also display HLint warnings. There is an error pane that shows current compilation errors. Definitely a point for EclipseFP.Īutomatic compilation and error detection. It will insert hundreds of unused sections and completely rearrange an layout you’ve made. While EclipseFP offers a nice, non-intrusive editor, Leksah will demolish your hand-crafted cabal file. Anyway, I still think that Emacs wins as far as syntax highlighting is concerned.Ĭabal file editor. Aside from that the capabilities of Leksah in syntax highlighting are similar to EclipseFP, but the latter gives you customization options and doesn’t have glitches. I also noticed that for some of available settings spaces are not the same width as other characters, which breaks the layout of haddock comments - see the screenshot above. These colour themes are nice but I don’t see why the user can’t customize them. You can’t define your own colours for the editor and you’re limited to a few predefined settings. After drinking your cup of tea (possibly a few) or coming back from the walk - depending which option you chose - you’re finally ready to work with Leksah.
The latter doesn’t happen very often, but we’ll get to that later. Be prepared to rebuild this database after installing any new packages or upgrading Leksah.
This, again, takes Very Long Time, so you can get yourself a cup of tea or possibly take a walk. When Leksah starts for the first time it needs to collect information about packages available in the system. Before we go into details about using Leksah I have to add that upgrading Leksah to newer version was much easier and faster since the dependencies were already present. I recall having some problems with gtksourceview, but #haskell channel came to the rescue and after about 2 hours of struggling with installation (and 3 hours of installing GHC…) I was ready to finally start the IDE. Unfortunately not everything went as smoothly as it should. Since my GHC package repository was bare and Leksah needs a lot of additional dependencies (and I really mean a lot), the whole installation process took Very Long Time. Luckily cabal is a smart tool and can manage the installation process quite well by automatically downloading, compiling and installing required dependencies.
#Best haskell ide manual
There is a page on Haskell wiki and a user’s manual but both are outdated, manual by about 2 years, wiki even more. First of all, it’s not easy to find any sort of installation instructions for Leksah. Previously I said that installation of EclipseFP can be tedious, but I should have reserved that word for Leksah.
#Best haskell ide full
I described the full story in one of the previous posts, but long story short I removed GHC packages installed from the repo, downloaded pre-compiled GHC binaries and then installed Leksah using cabal.
#Best haskell ide install
This meant that I had to install it using cabal and I wasn’t very keen on idea of having GHC installation managed both by zypper 1 and cabal. I had all the GHC packages installed from openSUSE repositories, but it turned out that Leksah is not in the repo.
I was a total newbie back then (not that I know much more now) and the installation process was very tough going for me. Leksah was the first Haskell IDE I tried when I started learning the language. It’s time to finish presentation of IDEs with the last one, Leksah - a Haskell IDE written in Haskell. In the previous parts of this series I presented two development environments for Haskell: Emacs and EclipseFP. Jan Stolarek Projects Publications Personal Blog