From: Leo Prikler <leo.prikler@student.tugraz.at>
To: Joshua Branson <jbranso@dismail.de>
Cc: 48974@debbugs.gnu.org
Subject: bug#48974: A possible shepherd bug (it's very minor)
Date: Fri, 25 Jun 2021 11:56:40 +0200 [thread overview]
Message-ID: <6254e4d32697986bd61986e10399f341930c5c2e.camel@student.tugraz.at> (raw)
In-Reply-To: <87mtre5lzy.fsf@dismail.de>
Hi,
Am Freitag, den 25.06.2021, 05:31 -0400 schrieb Joshua Branson:
> Leo Prikler <leo.prikler@student.tugraz.at> writes:
>
> > Hi,
> >
> > Am Samstag, den 12.06.2021, 20:09 +0000 schrieb jbranso@dismail.de:
> > > June 12, 2021 3:39 PM, "Leo Prikler" <
> > > leo.prikler@student.tugraz.at>
> > > wrote:
> > >
> > > > Am Samstag, den 12.06.2021, 09:26 -0400 schrieb Joshua Branson:
> > > >
> > > > > Hello!
> > > > >
> > > I'll tell you what, why don't we leave this "bug" open for a
> > > week...I'll try to write
> > > the code that does what I want, and I'll email the answer.
> > >
> > > Then I'll edit the manual to provide an example!
> > I'm pretty sure that the actual bug also exists, just not sure
> > whether
> > that's on your config or on shepherd. Using TTY1 for graphical
> > stuff
> > is also somewhat rare in Guix land, I presume. (Or rather, I can't
> > think of it as anything but a container for debug output spam :D)
> >
> > As for getting this to work only on TTY1, you do get the config
> > object,
> > so you can do stuff like
> > (if (is-tty1? config) (inherit+autologin config) config)
> > Note of course, that is-tty1? is not a procedure that's ready-made,
> > but
> > one that you'd need to build from primitives such as record
> > accessors.
> >
>
> Well, it's been about a week. Here is my current code that doesn't
> work.
> haha.
>
> #+BEGIN_SRC scheme
> (define %my-desktop-services
> (modify-services %desktop-services ;;end of remove services
> (mingetty-service-type config =>
> (mingetty-configuration
> (inherit config)
> ;; ERROR at the NEXT LINE
> (auto-login-to-tty-3 config)
> ))))
>
> (define (auto-login-to-tty-3 config)
> (if (string=? "3" (mingetty-configuration-tty config))
> '(auto-login "joshua")
> '(auto-login #f)))
> #+END_SRC
>
> It obviously doesn't work because I am treating modify-services as if
> it were a procedure. In fact, it is a macro. :)
That's not the issue here, the issue is that you're treating mingetty-
configuration as… I'm not really sure what exactly, when it is in fact
a record constructor.
Try the following:
#+BEGIN_SRC scheme
(define (auto-login-to-tty tty user)
;; TODO: you might want to implement this as match-lambda instead
(lambda (config)
(if (string=? tty (mingetty-configuration-tty mingetty-config))
(mingetty-configuration
(inherit config)
(auto-login user))
config)))
(define %my-desktop-services
(modify-services %desktop-services
(mingetty-service-type config =>
(auto-login-
to-tty "3" "joshua"))))
#+END_SRC
> #+BEGIN_SRC scheme
> (define (auto-login-to-tty-3 mingetty-service)
> (if (string=? "3" (mingetty-configuration-tty config))
> '(mingetty-configuration
> (auto-login "joshua")
> (tty "3"))
> mingetty-service))
Don't quote mingetty-configuration et al. They're first-class syntax,
not just weird lists.
> (define (my-modify-%desktop-services-to-auto-login-on-tty-3 %desktop-
> services)
> ;; to be written
> ;; though I think fold, or map, may be useful functions here.
>
> ;;somehow I will use this function...
> (auto-login-to-tty-3 mingetty-service)
> )
>
> (define %my-desktop-services
> (my-modify-%desktop-services-to-auto-login-on-tty-3 %desktop-
> services))
I don't think you need to implement modify-services on your own, rather
just use the existing thing in the "correct" way – i.e. adhering to the
expectations given by the already existing procedure (or macro).
> #+END_SRC
Regards,
Leo
next prev parent reply other threads:[~2021-06-25 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 13:26 bug#48974: A possible shepherd bug (it's very minor) Joshua Branson via Bug reports for GNU Guix
2021-06-12 19:39 ` Leo Prikler
2021-06-12 20:09 ` jbranso--- via Bug reports for GNU Guix
2021-06-12 21:13 ` Leo Prikler
2021-06-25 9:31 ` Joshua Branson via Bug reports for GNU Guix
2021-06-25 9:56 ` Leo Prikler [this message]
2021-06-25 18:06 ` Joshua Branson via Bug reports for GNU Guix
2021-06-25 18:28 ` Leo Prikler
2021-07-02 22:57 ` Joshua Branson via Bug reports for GNU Guix
2021-07-03 6:41 ` Leo Prikler
2021-07-03 7:37 ` pelzflorian (Florian Pelz)
2021-07-05 23:59 ` Joshua Branson via Bug reports for GNU Guix
2021-06-12 23:34 ` jbranso--- via Bug reports for GNU Guix
2021-06-13 7:48 ` Leo 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=6254e4d32697986bd61986e10399f341930c5c2e.camel@student.tugraz.at \
--to=leo.prikler@student.tugraz.at \
--cc=48974@debbugs.gnu.org \
--cc=jbranso@dismail.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).