From: pinoaffe <pinoaffe@gmail.com>
To: guix-devel@gnu.org
Subject: Re: Some emacs stuff to activate/deactivate guix profiles
Date: Thu, 17 Dec 2020 08:31:47 +0000 [thread overview]
Message-ID: <CAN6Py=PFRJp1t53MM0mErsLrSddr+_P9AQaKec0-kh4Xv3S3Bw@mail.gmail.com> (raw)
In-Reply-To: <877dphyqn2.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Hi everybody, sorry for the repeated messages, something went wrong with
mu4e
On Thu, Dec 17, 2020 at 4:59 AM pinoaffe <pinoaffe@gmail.com> wrote:
> Hi guix!
>
> I wrote some elisp that
> * maintains a list of available guix profiles
> * maintains a list of active guix profiles
> * allows the user to modify both of those lists
> * provides interactive commands that allow the user to (de)activate
> profiles
> * sets env variables and the emacs search path based on active profiles
> I may add the ability to "update" a profile from a manifest.
>
> This allows me to have a profile with, say, reverse engineering tools,
> and to (de)activate it whenever I do(nt) need those tools.
>
> Please not that I'm fairly new to all of this emacs stuff, so it may not
> be idiomatic or good code.
>
> I've attached the reusable stuff in guix-profiles.el, and my personal
> config in init-profiles.el.
>
> Any thoughts?
>
> Blessings,
> pinoaffe
>
>
[-- Attachment #2: Type: text/html, Size: 1318 bytes --]
next prev parent reply other threads:[~2020-12-17 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 4:59 Some emacs stuff to activate/deactivate guix profiles pinoaffe
2020-12-17 8:26 ` zimoun
2020-12-17 8:36 ` pinoaffe
2020-12-17 8:52 ` zimoun
2020-12-17 8:31 ` pinoaffe [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-17 8:29 pinoaffe
2020-12-17 9:32 ` Jan Nieuwenhuizen
2020-12-17 14:28 ` pinoaffe
2020-12-17 4:57 pinoaffe
2020-12-16 19:43 pinoaffe
2020-12-16 19:43 pinoaffe
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='CAN6Py=PFRJp1t53MM0mErsLrSddr+_P9AQaKec0-kh4Xv3S3Bw@mail.gmail.com' \
--to=pinoaffe@gmail.com \
--cc=guix-devel@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.
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).