From: zimoun <zimon.toutoune@gmail.com>
To: Michael Rohleder <mike@rohleder.de>
Cc: 41252@debbugs.gnu.org
Subject: [bug#41252] [PATCH] gnu: emacs-org-re-reveal: Update to 2.12.2.
Date: Thu, 14 May 2020 12:02:49 +0200 [thread overview]
Message-ID: <CAJ3okZ2m7VN_OX5yGF+dDTYkGOY+zh2Y6iOLKRAduNcpJ4vQ6g@mail.gmail.com> (raw)
In-Reply-To: <87k11eho6u.fsf@rohleder.de>
Dear Michael,
On Thu, 14 May 2020 at 11:17, Michael Rohleder <mike@rohleder.de> wrote:
> To test this, I made a presentation about guix git workflow in emacs:
> https://www.rohleder.de/~mike/guix-workflow/
Nice!
Just one minor comment, instead of this long '--ad-hoc' line, you
should use a manifest file.
#+BEGIN_SRC shell
guix environment -C -N -E TERM guix --expose=/var/guix=/var/guix \
--ad-hoc emacs-no-x emacs-magit git git:send-email emacs-yasnippet
help2man pkg-config guile \
-- emacs --execute "(load-theme 'wombat)"
#+END_SRC
#+BEGIN_SRC shell
guix environment -C -N -E TERM guix --expose=/var/guix=/var/guix \
-m my-manifest.scm \
-- emacs --execute "(load-theme 'wombat)"
#+END_SRC
--8<---------------cut here---------------start------------->8---
(specifications->manifest
'("emacs-no-x" "emacs-magit"
"git" "git:send-email"
"emacs-yasnippet"
"help2man" "pkg-config guile"))
--8<---------------cut here---------------end--------------->8---
The main advantages are:
- version control the file
- reuse elsewhere, for example "guix install"
- easy to locally extend:
guix environment -m my-manifest --ad-hoc emacs-evil
Well, thank you for sharing and for the update.
All the best,
simon
next prev parent reply other threads:[~2020-05-14 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 9:15 [bug#41252] [PATCH] gnu: emacs-org-re-reveal: Update to 2.12.2 Michael Rohleder
2020-05-14 9:22 ` bug#41252: " Nicolas Goaziou
2020-05-14 10:02 ` zimoun [this message]
2020-05-14 10:45 ` [bug#41252] " Michael Rohleder
2020-05-14 16:41 ` zimoun
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=CAJ3okZ2m7VN_OX5yGF+dDTYkGOY+zh2Y6iOLKRAduNcpJ4vQ6g@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=41252@debbugs.gnu.org \
--cc=mike@rohleder.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).