From: Tomas Volf <~@wolfsden.cz>
To: "Kristoffer Ström" <kristoffer@rymdkoloni.se>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Emacs C source
Date: Sun, 17 Dec 2023 12:27:55 +0100 [thread overview]
Message-ID: <ZX7bOwqcPb54np3s@ws> (raw)
In-Reply-To: <87r0jnv7j1.fsf@rymdkoloni.se>
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On 2023-12-15 15:56:34 +0100, Kristoffer Ström wrote:
>
> Hello! I'm running emacs in a guix shell, and wonder how/where to get
> the C source code directory for xref-find-definitions.
>
> I've grepped the /gnu/store/*emacs but cannot find the C source, is
> there some special package/output or procedure needed to get it included
> in the shell environment?
You can download source archives for any package using build --sources, like
this:
$ guix build --sources emacs
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
43.3 MB will be downloaded:
/gnu/store/c4xfnis0g5g2v1ssl3wqgk8h6s3xjfk6-emacs-29.1.tar.xz
substituting /gnu/store/c4xfnis0g5g2v1ssl3wqgk8h6s3xjfk6-emacs-29.1.tar.xz...
downloading from https://bordeaux.guix.gnu.org/nar/lzip/c4xfnis0g5g2v1ssl3wqgk8h6s3xjfk6-emacs-29.1.tar.xz ...
emacs-29.1.tar.xz 41.3MiB 16.6MiB/s 00:02 ▕██████████████████▏ 100.0%
/gnu/store/c4xfnis0g5g2v1ssl3wqgk8h6s3xjfk6-emacs-29.1.tar.xz
You can then extract the archive somewhere.
Hope this helps,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-17 11:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 14:56 Emacs C source Kristoffer Ström
2023-12-17 11:27 ` Tomas Volf [this message]
2023-12-17 13:18 ` Kristoffer Ström
2023-12-19 15:35 ` Simon Tournier
2023-12-19 16:07 ` Kristoffer Ström
2023-12-17 22:03 ` Ian Eure
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=ZX7bOwqcPb54np3s@ws \
--to=~@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=kristoffer@rymdkoloni.se \
/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.