From: edk@beaver-labs.com
To: jgart <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: Using emacs library with guix environment
Date: Wed, 06 Oct 2021 21:15:54 +0200 [thread overview]
Message-ID: <87k0iq2c7o.fsf@rdklein.fr> (raw)
In-Reply-To: <20211006150428.GC9839@gac.attlocal.net>
Hello !
I'm not sure what the problem is with this particular package, but:
guix environment emacs-commander
will create an env with all you need to BUILD emacs-commander
while
guix environment --ad-hoc emacs-commander
will create an env in which emacs-commander is installed.
Now, if guix environment --ad-hoc emacs-commander doesnt work, it may
mean that one of the native-input of emacs-commander should be an input
or a propagated-input instead. That would explain why
guix environment emacs-commander --ad-hoc emacs-commander
works: because it installs this native-input in the env as well.
I hope this makes sense, if not please ask away.
Cheers,
Edouard.
jgart <jgart@dismail.de> writes:
> Hi,
>
> I'm trying to use emacs-commander with guix environment on a foreign distro.
>
> I'm only able to properly source the library into the environment if I run
> the following:
>
> `guix environment emacs-commander --ad-hoc emacs-commander`
>
> Why do I have to provide emacs-commander twice to the environment command?
>
> I tested only using --ad-hoc or without and none of those work.
>
> I'm only able to properly source emacs-commander when I include it twice as in
> the above command.
>
> Could someone explain the reason for this to me?
>
> Any help is much appreciated.
>
> all best,
>
> jgart
>
> https://github.com/rejeep/commander.el
>
> 3B1D 7F19 E36B B60C 0F5B 2CA9 A52A A2B4 77B6 DD35
next prev parent reply other threads:[~2021-10-06 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 19:04 Using emacs library with guix environment jgart
2021-10-06 19:15 ` edk [this message]
2021-10-07 0:18 ` Kyle Meyer
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=87k0iq2c7o.fsf@rdklein.fr \
--to=edk@beaver-labs.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.