From: Chris Marusich <cmmarusich@gmail.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: "Perfect Setup" for hacking on Nix?
Date: Sun, 07 May 2017 14:06:09 -0700 [thread overview]
Message-ID: <87h90we5ry.fsf@gmail.com> (raw)
In-Reply-To: <20170403.083656.44673764432930551.post@thomasdanckaert.be> (Thomas Danckaert's message of "Mon, 03 Apr 2017 08:36:56 +0200 (CEST)")
[-- Attachment #1: Type: text/plain, Size: 2151 bytes --]
Thomas Danckaert <post@thomasdanckaert.be> writes:
> From: ludo@gnu.org (Ludovic Courtès)
> Subject: Re: "Perfect Setup" for hacking on Nix?
> Date: Sun, 02 Apr 2017 11:33:16 +0200
>
>>> I have sometimes found myself looking at the Nix source code that
>>> is
>>> embedded in the Guix repository. However, I don't have a lot of
>>> experience with C++, so I don't really know how I should set up my
>>> development environment for hacking on (or just browsing) that
>>> code.
>>>
>>> So, what's the "Perfect Setup" for hacking on Nix?
>>
>> Good question! :-) I use Emacs without any of the fancy things.
>> M-x
>> compile, M-x grep, M-x rgrep, xgtags.el (for GNU GLOBAL tags) are
>> good
>> enough for me.
>>
>> That said, I’d be happy to hear about new tricks! Does Semantic
>> work
>> well these days?
>
> I'm quite happy with it (have been, for a number of years already!).
> It's code analysis is not perfect (e.g. it doesn't always distinguish
> different symbols with the same name), but helps a lot. It can take
> you to function definitions and declarations, show all uses of a
> function or variable, display function signatures etc.
>
> I did have to disable Semantic for Scheme buffers, like this:
>
> (add-to-list 'semantic-inhibit-functions
> (lambda () (member major-mode '(scheme-mode))))
>
> Otherwise, I get constant debugger prompts from the semantic parser
> when working with (Guile) Scheme files. I didn't submit a bug report
> so far, because I'm not sure if it's purely a bug in Semantic, or if
> there's some interference with Geiser.
>
> For really excellent code analysis of even very messy C and C++ code,
> I recommend KDevelop (I tend to use it just to explore and find my way
> around a code base, and then use Emacs for actual editing).
>
> Thomas
>
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++.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-05-07 21:06 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 [this message]
2017-05-08 14:22 ` Ludovic Courtès
2017-05-10 7:31 ` Chris Marusich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h90we5ry.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.