From: Richard Sent <richard@freakingpenguin.com>
To: samuel@thewilley.family
Cc: help-guix@gnu.org
Subject: Re: Guix Shepherd Service Help
Date: Fri, 19 Jan 2024 13:26:38 -0500 [thread overview]
Message-ID: <34ca99dc238adf888c0e1642e8b5a71e@freakingpenguin.com> (raw)
In-Reply-To: <cadd10788ea8f01b7b8e3d8710acf965@thewilley.family>
On 2024-01-19 10:23, samuel@thewilley.family wrote:
> Any help would be nice, I've been smashing my head into the wall for a
> few days as I feel this is required for my usage of Emacs. I'm not sure
> why anyone would want this, but the relevant channels.scm snippet will
> be in the readme.md of the same repository. I'm not entirely sure why
> it doesn't work, running the command by hand using sudo just works.
> Would somehow "dynamically" creating the yaml with path included work?
> I would prefer if there could be preservation of using a yaml that
> isn't statically generated.
I can't help you with the service issue, but if you're running Guix
System take a look at `keyboard-layout`. i.e. (keyboard-layout "us"
#:options '("ctrl:nocaps"))
next prev parent reply other threads:[~2024-01-19 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 15:23 Guix Shepherd Service Help samuel
2024-01-19 18:26 ` Richard Sent [this message]
2024-01-19 19:02 ` Felix Lechner via
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=34ca99dc238adf888c0e1642e8b5a71e@freakingpenguin.com \
--to=richard@freakingpenguin.com \
--cc=help-guix@gnu.org \
--cc=samuel@thewilley.family \
/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).