From: jbranso@dismail.de
To: "Mekeor Melire" <mekeor@posteo.de>, guix-devel@gnu.org
Subject: Re: Draft new Guix Cookbook section on Emacs
Date: Mon, 05 Jun 2023 19:08:48 +0000 [thread overview]
Message-ID: <deb090603146f7b6e8a523960cf3c618@dismail.de> (raw)
In-Reply-To: <87v8g2saju.fsf@posteo.de>
June 5, 2023 2:13 AM, "Mekeor Melire" <mekeor@posteo.de> wrote:
> Hello :)
>
> I'd like to contribute to the Guix Cookbook.
>
> The Cookbook is written in Texinfo format but as I'm not fluent in it, I decided I'd first draft my
> contribution in Org-Mode which I'd later export as Texinfo and adapt appropriately. I'm sorry that
> this also means that the hereby submitted draft does not come as a Git patch for now.
>
> Find below a first draft of a new chapter entitled "Emacs", including two subchapters, "Beginners
> Guide to the Perfect Setup" and "Mu4e".
>
> Regarding the Perfect Setup, I'm convinced that it makes sense to have a more beginner-friendly
> tutorial supplementing the instructions which are already present in the Guix manual. It's meant to
> have more background information and more, non-essential configuration tips, as well as details on
> usage, including keybindings.
>
> Regarding emails, in the long-term, I'd also like to contribute a new chapter on how to use the
> mailing-lists, elaborating on how to get local maildir copies of the mailing-lists with tools like
> isync/mbsync or public-inbox etc. But that's for the future!
>
> I'm looking forward to your feedback.
My only question is should we mention emacs-guix? I haven't tried using it in a long time. Does it
still work?
next prev parent reply other threads:[~2023-06-05 19:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 23:32 Draft new Guix Cookbook section on Emacs Mekeor Melire
2023-06-05 13:02 ` Remco
2023-06-05 19:08 ` jbranso [this message]
2023-06-06 13:48 ` Robby Zambito
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=deb090603146f7b6e8a523960cf3c618@dismail.de \
--to=jbranso@dismail.de \
--cc=guix-devel@gnu.org \
--cc=mekeor@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).