From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: emacs byte-compiled packages incompatibilities (was Re: emacs-guix invalid byte opcode: op=183 ptr=25)
Date: Thu, 28 Feb 2019 16:11:53 +0100 [thread overview]
Message-ID: <874l8ogd6u.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87o96w2cmm.fsf@roquette.mug.biscuolo.net>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
> as I sayd above, I still don't know how to skip loading packages from
> ~/.emacs.d/elpa when in "guix emacs"
To test if Emacs is from Guix, you can
--8<---------------cut here---------------start------------->8---
(if (require 'guix-emacs nil 'noerror)
; Code for Guix Emacs
; Code for non-Guix Emacs
)
--8<---------------cut here---------------end--------------->8---
In particular, you can set `package-user-dir' and call (package-initialize) for
non-Guix Emacs.
> when using the "native" one, emacs could be started using a different
> user-emacs-directory: this way emacs installed packages (from
> ELPA/MELPA or manually) will be available only in that environment
>
> but this solution is not good for me, since I should maintain two
> different config trees: one for each emacs... no no no :-O
Indeed, just set different `package-user-dir' and keep the same config :)
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-02-28 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 10:28 emacs-guix invalid byte opcode: op=183 ptr=25 Yoshinori Arai
2019-02-28 10:37 ` Pierre Neidhardt
2019-02-28 12:26 ` zimoun
2019-02-28 13:28 ` Pierre Neidhardt
2019-02-28 14:47 ` emacs byte-compiled packages incompatibilities (was Re: emacs-guix invalid byte opcode: op=183 ptr=25) Giovanni Biscuolo
2019-02-28 15:11 ` Pierre Neidhardt [this message]
2019-02-28 19:03 ` emacs-guix invalid byte opcode: op=183 ptr=25 Ricardo Wurmus
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=874l8ogd6u.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=g@xelera.eu \
--cc=help-guix@gnu.org \
/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.
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).