From: "Marek Paśnikowski" <marek@marekpasnikowski.pl>
To: help-guix@gnu.org
Subject: Re: Auto-Login with Elogin, Greetd and wlgreet
Date: Sat, 10 Aug 2024 07:13:34 +0200 [thread overview]
Message-ID: <878qx5q7sx.fsf@marekpasnikowski.pl> (raw)
In-Reply-To: <172324832670.7.10181535524203055421.402105637@tatd.dev> (guix@tatd.dev's message of "Sat, 10 Aug 2024 00:05:21 +0000")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
guix@tatd.dev writes:
> I did found a method in the arch linux wiki to auto-login with greetd
> config, But guix auto generates the greetd config file.
>
> I am wondering if I can add on to the generate config file or use a
> manual config file instead of the auto generated one.
>
I will teach how I would start to approach this problem: Identify the
source code that defines the current greetd configuration file —
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/services/base.scm#n3597
Follow that code and understand it. The simplest way to hack it is to
copy the entire greetd-service-type procedure, replace the
greetd-etc-service with your own and use the changed definition in your
system configuration.
> I am new to the mailing list. If I make a mistake on replying to the
> mailing list, I apologize. I don't know if I need to simple reply or
> reply to all.
The best option is to "reply to mailing list". It may not exist in your
mail software, I am not sure about the next best thing.
And do the bottom posting technique when replying.
https://git-send-email.io/top-posting.html
-----BEGIN PGP SIGNATURE-----
iQJOBAEBCAA4FiEEWQ5QD+OdJrPmC3Q7bYGxIHcRiZ8FAma29v4aHG1hcmVrQG1h
cmVrcGFzbmlrb3dza2kucGwACgkQbYGxIHcRiZ/naQ/+Inc73JlQg8FCHwZzKbFd
QE+C2VZ7saYOAxQscwcwJjhlCQKxt6900NKdC21tae4d6jfkdXTf7G7aB8Qw+wQT
CXM0yFvsB37Jtheobx3iXQL8NIgX6K7Ehn1W4XEydMEmUjFzKwP/P4kPTR5QZfS1
bCq+ZEvllkgKgAqNRDGqvDbPKxhAFCv4wXkFNHUkrn1GgbPXuDsg5MHoVh6iT/uV
Sl0ov8+g80Rwo/3N+42LB0V1atwnUoolNOSw5LQbqQyW7rrg7GMWNtSYVqNQDkOd
zkU0zxghQp57FbPZX5LZrxDJjkoOVXBSxtFDX4+rEqV+KmYdD2qAGTpPbtvIXnYS
cTidM7coNODOhHWGOO1gbGxZ5eDHtg3dHvVcpAZuPO5nBL/zVZoqQQncDWjVQiqJ
jdyC48f1m431/aACqBnG9Oswv2se+33AXBowNe/YUhosKQDdazf5oJPumN14ruH4
Pt0hFPNNiTcDLzKXdnqnalTgTaQBRga63U6YGg0QT/gqstgPiK2p04XeSUkkiKMb
2ZrhgBsFR4+rV30OewYfmoUEtDqCeFihlYn//Byhy3NvhhAXcHk6nIiK1z+Iwnzd
yi/h+rzEFub9qCtsnM2hcr0PxQkCzC+fOfAEVr/V7aGmYa2c15uu87/y4duqT7d2
TPng2afzVvkhk0CM3yduhbA=
=H59R
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2024-08-10 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-04 1:15 Auto-Login with Elogin, Greetd and wlgreet guix
2024-08-06 21:56 ` jbranso
2024-08-10 0:05 ` guix
2024-08-10 5:13 ` Marek Paśnikowski [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878qx5q7sx.fsf@marekpasnikowski.pl \
--to=marek@marekpasnikowski.pl \
--cc=help-guix@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.