Emacs can be configured to look great, see the following quora answer for example. You can just try to get used to it and
add your configuration incremently. After a few time, it will be of beautiful appearance.
http://www.quora.com/How-can-I-go-from-good-to-great-in-Emacs
--m00nlight
在2015年04月10 08时18分, "Dimitri DeFigueiredo"写道:
I did try to use Leksah, but did not like the interface. I don't think it helped with debugging, but may be mistaken. I'm now using sublime 3 and hoping that someday I will be able to use Atom. Emacs appears to be the standard, but it is just too ugly for me.
Dimitri
On 09/04/15 02:03, emacstheviking wrote:
That's interesting.
I must confess that I find the need to debug in Haskell greatly reduced because I tend to design stuff in small incremental steps in ghci / emac in a Lisp like way which means that I am reasoning out my code as I write it which usually means there are no logical bugs at least.
However I can see the need on occasion to maybe debug into issues relating to threads / STM and behaviours between processes in general.
Have you tried using Leksah, the Haskell IDE?
On 9 April 2015 at 02:21, Dimitri DeFigueiredo wrote:
I need to improve my Haskell debugging skills. I know of quickcheck, but that's for testing. It seems that:
- Debug.Trace and
- dynamic breakpoints in GHCi
Are the two easy ways to check the state of your program at a specific point in execution.
Is there another simple tool that I should know about? Any tips?
Thank you,
Dimitri
_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
_______________________________________________
Beginners mailing listBeginners@haskell.orghttp://mail.haskell.org/cgi-bin/mailman/listinfo/beginners
