From: Gottfried <gottfried@posteo.de>
To: SeerLite <seerlite@nixnet.email>,
Gary Johnson <lambdatronic@disroot.org>
Cc: help-guix@gnu.org
Subject: scanner
Date: Mon, 21 Feb 2022 17:13:29 +0000 [thread overview]
Message-ID: <a5ef00b9-70b0-f71f-f5d9-7e14a56508af@posteo.de> (raw)
In-Reply-To: <b82e1829-0ed1-0fb0-f25e-76373e23d7fc@nixnet.email>
Am 20.02.22 um 20:57 schrieb SeerLite:
> On 2/20/22 13:25, Gottfried wrote:
>> Hi,
>>
>> Below is my config.scm: it has 60 lines (if the 61:1 refers to a line???)
>>
>> after: sudo guix system reconfigure /etc/config.scm
>>
>> this message:
>>
>> /etc/config.scm:61:1: schließende Klammer fehlt (in English closing
>> bracket is missing)
>>
>> I don`t know where is the missing bracket?
>
> You're missing 2 closing parentheses here:
>
>> (services
>> (append
>> (list (service mate-desktop-service-type)
>> (service enlightenment-desktop-service-type)
>> (service cups-service-type
>> (cups-configuration
>> (web-interface? #t)
>> (extensions (list cups-filters hplip))))
>> (service openssh-service-type)
>> (service tor-service-type)
>> (set-xorg-configuration
>> (xorg-configuration
>> (keyboard-layout keyboard-layout))))
>> (modify-services %desktop-services
>> (sane-service-type _ => sane-backends))
>
> One to close the "(append" and another one to close the "(services". We
> need these because otherwise Guile doesn't know where your _append_
> stops and where your _services_ stop. It will continue reading
> everything as if it's part of the "append", when it actually has to
> close inside of services.
>
> Does that make sense?
>
> I hope you're able to get it working this time! :)
>
> SeerLite
Hi,
does it mean that I have to add to the last words "sane-backends"
instead of 2 brackets 4 brackets?
This is, what I understood.
gottfried
next prev parent reply other threads:[~2022-02-21 17:25 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 16:45 install a Printer Gottfried
2022-02-15 16:54 ` Julien Lepiller
2022-02-15 17:31 ` Gottfried
2022-02-15 17:44 ` Julien Lepiller
2022-02-15 18:29 ` Gottfried
2022-02-15 18:34 ` Julien Lepiller
2022-02-15 18:59 ` Gottfried
2022-02-15 19:02 ` Julien Lepiller
2022-02-15 19:17 ` Julien Lepiller
2022-02-15 19:39 ` Gottfried
2022-02-15 19:51 ` Julien Lepiller
2022-02-16 16:04 ` Gottfried
2022-02-16 17:01 ` Julien Lepiller
2022-02-16 19:40 ` Gottfried
2022-02-16 20:06 ` Julien Lepiller
2022-02-16 21:09 ` Gottfried
2022-02-18 1:39 ` Gary Johnson
2022-02-18 13:52 ` Gottfried
2022-02-18 15:11 ` Gary Johnson
2022-02-18 17:51 ` printer installed, now scanner ? Gottfried
2022-02-19 22:34 ` Gary Johnson
2022-02-20 15:13 ` Gottfried
2022-02-20 15:45 ` SeerLite
2022-02-20 16:20 ` Gottfried
2022-02-20 17:25 ` Gottfried
2022-02-20 19:57 ` SeerLite
2022-02-21 17:13 ` Gottfried [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-21 20:34 scanner Jay Sulzberger
2022-02-22 18:03 scanner Gottfried
2022-02-23 19:19 scanner Gottfried
2022-02-25 13:51 Scanner Gottfried
2022-04-10 13:19 Scanner Gottfried
2022-04-12 0:23 ` Scanner raingloom
2022-10-01 13:17 Scanner Gottfried
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=a5ef00b9-70b0-f71f-f5d9-7e14a56508af@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=lambdatronic@disroot.org \
--cc=seerlite@nixnet.email \
/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).