From: Zain Jabbar <zaijab2000@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Creating an Emacs Home Configuration Service
Date: Wed, 19 Oct 2022 10:53:52 -1000 [thread overview]
Message-ID: <CAH+UbWR18fg8=ZAvK+A4ccR2HSB5NME-8Qru+=ms4vo570nnfw@mail.gmail.com> (raw)
In-Reply-To: <878rlbj05b.fsf@gnu.org>
Aloha All,
Super awesome to hear from you! I'm quite star stuck.
Thank you for showcasing Andrew Tropin's rde project. I believe the
=features= abstraction have potential and make more intuitive sense
for the design of configurable programs. There is a lot for me to
learn from this design choice.
As it stands, =features= are not in Guix proper, are there plans to
merge them? How will they end up relating to the existing home
services feature set?
On Wed, Oct 19, 2022 at 5:36 AM Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi Zain, and welcome!
>
> Zain Jabbar <zaijab2000@gmail.com> skribis:
>
> > Running =guix home search emacs= returns nothing. I also could not find an
> > email using =C-u M-x debbugs-gnu= about an Emacs configuration service.
> >
> > This is my first email to this mailing address. Please give me pointers on
> > formatting and further improvements.
> >
> > I have attempted to make an =emacs-home-service-type= so that it is
> > possible to configure Emacs using Guix home. This code is extremely
> > preliminary hence I don't even think it is worth sending as a patch. Also I
> > have never worked on a multi person Git project before and do not know how
> > to solve the keyring error I get when using guix pull. I will outline what
> > my code does and what features I would like to add.
>
> I am all for something like you describe, and the code you sent may be
> good starting point!
>
> The rde project¹ by Andrew Tropin et al. may be a good source of
> inspiration. The “features” abstraction in particular seems to be
> well-suited for Emacs. But overall it’s reasonable to start small, with
> a low-level approach to combine and configure Emacs packages.
>
> Thanks,
> Ludo’.
>
> ¹ https://trop.in/rde/manual
--
Thank you,
Zain Jabbar
next prev parent reply other threads:[~2022-10-19 20:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH+UbWQ1JZCZf0BEOzT1zcTeW5sDekOsxbGYgKn8rjdQ5e0kUw@mail.gmail.com>
2022-10-17 2:34 ` Creating an Emacs Home Configuration Service Zain Jabbar
2022-10-17 22:09 ` jbranso
2022-10-17 23:12 ` Zain Jabbar
2022-10-18 15:41 ` jbranso
[not found] ` <CAH+UbWR8xWoCK9wouhsizEzTAO3CksNpkebu5we_75yQq++yUg@mail.gmail.com>
[not found] ` <a8142b002799224845f8efdddb28e518@dismail.de>
2022-10-19 18:18 ` jbranso
2022-10-19 20:25 ` Zain Jabbar
2022-10-19 20:56 ` jbranso
2022-10-19 21:09 ` Zain Jabbar
2022-10-19 15:36 ` Ludovic Courtès
2022-10-19 20:53 ` Zain Jabbar [this message]
2022-10-20 7:22 ` Andrew Tropin
2022-10-20 13:17 ` Ludovic Courtès
2022-10-20 18:35 ` Liliana Marie Prikler
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='CAH+UbWR18fg8=ZAvK+A4ccR2HSB5NME-8Qru+=ms4vo570nnfw@mail.gmail.com' \
--to=zaijab2000@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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).