From: Robert Bihlmeyer <robbe@orcus.priv.at>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug#261181: udev: doesn't notice parentheses in rules file
Date: Tue, 26 Apr 2005 05:51:43 +0000 [thread overview]
Message-ID: <87sm1ekrv4.fsf@orcus.priv.at> (raw)
In-Reply-To: <20040913121844.GA6208@wonderland.linux.it>
Marco:
> There is nothing udev can do about this, because %c(1) is a valid device
> name.
Which shows an ambiguity in the syntax:
'%c{1}' is taken to mean the first word returned from a program. It
could also be taken for the complete string returned from a program,
followed by a literal '{1}'. If I want the second alternative, how do
I write that?
A more regular syntax would be (for example):
%c whole string returned from program
%3c third word returned from program
Anything after the c is taken literally (except for another %-escape).
--
Robbe
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-04-26 5:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 12:18 Bug#261181: udev: doesn't notice parentheses in rules files Marco d'Itri
2005-04-26 5:51 ` Robert Bihlmeyer [this message]
2005-04-26 11:30 ` Bug#261181: udev: doesn't notice parentheses in rules file Kay Sievers
2005-04-28 5:21 ` Robert Bihlmeyer
2005-04-28 6:06 ` Greg KH
2005-04-28 17:26 ` Robert Bihlmeyer
2005-04-28 18:30 ` Kay Sievers
2005-04-29 5:28 ` Robert Bihlmeyer
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=87sm1ekrv4.fsf@orcus.priv.at \
--to=robbe@orcus.priv.at \
--cc=linux-hotplug@vger.kernel.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 NNTP newsgroup(s).