unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Thomas Danckaert <post@thomasdanckaert.be>
Subject: Re: "Perfect Setup" for hacking on Nix?
Date: Wed, 10 May 2017 00:31:34 -0700	[thread overview]
Message-ID: <8760h9p3qh.fsf@gmail.com> (raw)
In-Reply-To: <87fugfmnr5.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 08 May 2017 16:22:54 +0200")

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

ludo@gnu.org (Ludovic Courtès) writes:

> Hi,
>
> Chris Marusich <cmmarusich@gmail.com> skribis:
>
>> I asked on nix-dev, and the (limited) response was basically that you
>> should use whatever works best for you:
>>
>> https://mailman.science.uu.nl/pipermail/nix-dev/2017-April/023416.html
>>
>> I guess that means I should look into a C++ IDE (Eclipse?) or the emacs
>> ecosystem for C/C++.
>
> Yeah.  As Thomas wrote, Semantic (part of Emacs) or KDEvelop are your
> best bets.
>
> But fundamentally, C++ doesn’t lend itself to live coding the way Lisp
> does, so you’ll probably never have an environment close to the
> Emacs/Geiser combo.

Oh yeah, thank you for reminding me about Semantic and KDEvelop.  I'll
check those out.

Thank you for the recommendations!

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-05-10  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-02  1:13 "Perfect Setup" for hacking on Nix? Chris Marusich
2017-04-02  9:33 ` Ludovic Courtès
2017-04-03  6:36   ` Thomas Danckaert
2017-05-07 21:06     ` Chris Marusich
2017-05-08 14:22       ` Ludovic Courtès
2017-05-10  7:31         ` Chris Marusich [this message]

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=8760h9p3qh.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=post@thomasdanckaert.be \
    /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).