unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Antwane Mason <ad.mason1413@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Udev Rule Not Triggered
Date: Sun, 29 Aug 2021 16:42:00 +0200	[thread overview]
Message-ID: <20210829144200.3rzxztcm7q4z2hkq@pelzflorian.localdomain> (raw)
In-Reply-To: <20210829142808.7wsitnwrmsxudynn@pelzflorian.localdomain>

On Sun, Aug 29, 2021 at 04:28:08PM +0200, pelzflorian (Florian Pelz) wrote:
> >     (string-append
> > "ACTION==\"add\", SUBSYSTEM==\"usb\", "
> >                    "ATTR{product}==\"Example\", "
> >                    "RUN+=\"/path/to/script\"")))
> 
> The difference is that the manual uses spaces at the end of each
> string except the last.
> 
> You can use string-append instead of string-join, but then you need a
> space at the end of the strings.

P.S. Or for testing just use one big one-line string instead:

(define %onlykey-udev-rule
  (udev-rule
   "49-onlykey.rules"
   "ATTRS{idVendor}==\"1d50\", ATTRS{idProduct}==\"60fc\", ENV{ID_MM_DEVICE_IGNORE}=\"1\" ATTRS{idVendor}==\"1d50\", ATTRS{idProduct}==\"60fc\", […]"
   ))

You can also use newlines in the string if syntax requires it.

Regards,
Florian


  reply	other threads:[~2021-08-29 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29 13:39 Udev Rule Not Triggered Antwane Mason
2021-08-29 13:53 ` pelzflorian (Florian Pelz)
2021-08-29 14:01   ` Antwane Mason
2021-08-29 14:28     ` pelzflorian (Florian Pelz)
2021-08-29 14:42       ` pelzflorian (Florian Pelz) [this message]
2021-08-29 15:22         ` Antwane Mason
2021-08-29 15:44           ` Antwane Mason
2021-08-29 17:23             ` pelzflorian (Florian Pelz)
2021-08-29 18:54               ` Antwane Mason
2021-08-29 21:39                 ` Antwane Mason
2021-08-29 22:12                   ` pelzflorian (Florian Pelz)
2021-08-29 22:17     ` Tobias Geerinckx-Rice
2021-08-31 21:59       ` Antwane Mason

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=20210829144200.3rzxztcm7q4z2hkq@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=ad.mason1413@gmail.com \
    --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.
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).