From: jgart <jgart@dismail.de>
To: indieterminacy <indieterminacy@libre.brussels>
Cc: Guix Help <help-guix@gnu.org>
Subject: Re: How do I verify my hashes?
Date: Sun, 10 Jul 2022 11:59:41 -0500 [thread overview]
Message-ID: <20220710115941.GB15738@gac> (raw)
In-Reply-To: <aaef1d732224fd534010bb70d1b10dc9@libre.brussels>
On Sun, 10 Jul 2022 15:25:36 +0200 indieterminacy <indieterminacy@libre.brussels> wrote:
> On 10-07-2022 04:12, jgart wrote:
> Bonface gives very cogent demonstrations of workflow, encourage him to
> do a screencast!
Bonface gave us a great demo screencast on using call-with-prompt and abort-to-prompt yesterday at the nairobilug meetup.
See #nairobilug on libera
> IMHO, the ultimate experience would be for everything operating from
> Magit's interface - for the beneficence of Guix.
I've started using emacs' built-in vc modules for git.
See in lisp/vc/* for what's available in the emacs source repository.
I've been using it with evil-collection bindings. It's not too bad:
https://github.com/emacs-evil/evil-collection/tree/master/modes/vc-git
https://github.com/emacs-evil/evil-collection/tree/master/modes/vc-annotate
https://github.com/emacs-evil/evil-collection/tree/master/modes/vc-dir
Maybe someday I'll learn magit properly.
`vc-region-history` is not a bad `git blame` wrapper.
next prev parent reply other threads:[~2022-07-10 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 2:12 How do I verify my hashes? jgart
2022-07-10 4:13 ` Vagrant Cascadian
2022-07-10 10:09 ` Csepp
2022-07-10 13:25 ` indieterminacy
2022-07-10 16:59 ` jgart [this message]
2022-07-14 8:52 ` Munyoki Kilyungi
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=20220710115941.GB15738@gac \
--to=jgart@dismail.de \
--cc=help-guix@gnu.org \
--cc=indieterminacy@libre.brussels \
/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).