From: Vincent Legoll <vincent.legoll@gmail.com>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: haskell importer problems?
Date: Sat, 3 Sep 2016 14:29:04 +0200 [thread overview]
Message-ID: <CAEwRq=rmqpsYMTOTQQs5KB-WJe6crKUk1iaORN7CeELm0tm6mQ@mail.gmail.com> (raw)
In-Reply-To: <87bn059s21.fsf@we.make.ritual.n0.is>
On Sat, Sep 3, 2016 at 12:49 PM, ng0 <ng0@we.make.ritual.n0.is> wrote:
> at line 6, column -1
-----------------------------^
I didn't know you could hide your haskell code off screen ;-)
--
Vincent Legoll
next prev parent reply other threads:[~2016-09-03 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 10:49 haskell importer problems? ng0
2016-09-03 12:29 ` Vincent Legoll [this message]
2016-09-03 13:41 ` ng0
2016-09-03 14:01 ` Ludovic Courtès
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='CAEwRq=rmqpsYMTOTQQs5KB-WJe6crKUk1iaORN7CeELm0tm6mQ@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).