From: Ricardo Wurmus <rekado@elephly.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: guix-devel@gnu.org, Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Subject: Re: Missing dependency for emacs-magit
Date: Thu, 17 Feb 2022 20:26:35 +0100 [thread overview]
Message-ID: <87h78xguoj.fsf@elephly.net> (raw)
In-Reply-To: <809ccde21f551136c3632ab6c13c27e08e8684ce.camel@gmail.com>
Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> Hi,
>
> Am Mittwoch, dem 16.02.2022 um 22:23 +0000 schrieb Zelphir Kaltstahl:
>> [...]
>> It is t. That is after loading `init.el` and all it contains, but
>> there is no magit configuration happening inside this `init.el` yet.
> Now I'm at the end of words. Using my own machine as source of truth,
> git-commit is a part of magit, so if it exists in EMACSLOADPATH and is
> autoloaded, then it should be available. You might want to check your
> store using `guix gc --verify=contents`.
This is a mixed environment, isn’t it? Where some parts are loaded from
Emacs-managed stuff in .emacs.d/ and others from Guix?
Could you try again without the Emacs-managed packages?
--
Ricardo
next prev parent reply other threads:[~2022-02-17 19:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-13 23:51 Missing dependency for emacs-magit Zelphir Kaltstahl
2022-02-14 2:50 ` Michael Rohleder
2022-02-14 18:41 ` Zelphir Kaltstahl
2022-02-14 19:33 ` Liliana Marie Prikler
2022-02-15 9:45 ` Zelphir Kaltstahl
2022-02-15 19:54 ` Liliana Marie Prikler
2022-02-16 22:23 ` Zelphir Kaltstahl
2022-02-17 17:49 ` Liliana Marie Prikler
2022-02-17 19:26 ` Ricardo Wurmus [this message]
2022-02-18 1:10 ` Zelphir Kaltstahl
2022-02-18 4:51 ` Liliana Marie Prikler
2022-02-19 2:34 ` Zelphir Kaltstahl
2022-02-19 7:30 ` Liliana Marie Prikler
2022-02-19 15:43 ` Zelphir Kaltstahl
2022-02-19 16:04 ` Liliana Marie Prikler
2022-02-22 9:34 ` Zelphir Kaltstahl
2022-02-22 10:39 ` Liliana Marie Prikler
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=87h78xguoj.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=zelphirkaltstahl@posteo.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 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).