From: John Soo <jsoo1@asu.edu>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Questions about Development Environments in Emacs (Leiningen, Intero)
Date: Fri, 3 Jan 2020 08:01:42 -0800 [thread overview]
Message-ID: <BA1C112D-9E5E-41E3-AB51-A77A5A864D30@asu.edu> (raw)
In-Reply-To: <8736cxkkx7.fsf@ambrevar.xyz>
Hi Pierre!
> On Jan 3, 2020, at 12:24 AM, Pierre Neidhardt <mail@ambrevar.xyz> wrote:
>
> I'm facing a similar issue at the moment. Does anyone have a good
> answer to develop Haskell or Clojure with Emacs on Guix?
I write a fair bit of Haskell. I find that I like to use cabal-install to develop, then make a .scm file for the guix package separately.
haskell-mode works well in this workflow. There are a few tweaks to make, to get the most out of it. cabal complains if GHC_PACKAGE_PATH is set, so I use the Elisp variable haskell-process-wrapper-function to add "env -u GHC_PACKAGE_PATH" prior to the cabal commands.
The only other complaint I have is that flycheck-haskell only supports stack. haskell-mode has excellent error reporting, though. So I’ve never had a major complaint.
We could probably package stack. It is widely used in industry so it could make guix more usable. That would also start intero support. I am not sure if intero is maintained anymore, though. If they don’t find a maintainer I am not sure it will make it into guix.
Happy hacking!
John
next prev parent reply other threads:[~2020-01-03 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 3:00 Questions about Development Environments in Emacs brettg
2020-01-03 8:23 ` Questions about Development Environments in Emacs (Leiningen, Intero) Pierre Neidhardt
2020-01-03 16:01 ` John Soo [this message]
2020-01-03 16:45 ` Pierre Neidhardt
2020-02-10 21:22 ` Gary Johnson
2020-02-11 6:13 ` Pierre Neidhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BA1C112D-9E5E-41E3-AB51-A77A5A864D30@asu.edu \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).