On Sat, Nov 04, 2023 at 09:30:53AM +0000, RVP wrote:
> On Sat, 4 Nov 2023, tlaro...@kergis.com wrote:
>
> > > > No...: this is a break of existing. Trailing `*' selects STARred devices
> > > > (I'm not the inventor of this). So `*' can not be used as a joker ;-)
> > > >
> > >
> > > You can allow escapes for those:
> > >
> > > uc> disable i915drmkms\* # exact match STARred
> > > uc> disable *kms\* # only STARed `*kms'
> > >
> >
> > But this breaks existing...
> >
>
> Fine. You can introduce the notion of flags.
> For example `-p' for pattern:
>
> uc> disable i915drmkms* # std. starred device
> uc> disable -p *drm* # disable using pattern
>
> You can also add, let's say, a `-g' group flag:
>
> uc> list -g # list all "groups"
> uc> list -g drmkms # list devices in group drmkms
> uc> disable -g drmkms # disable group drmkms
>
Yep, but know you see what became of the simplifications ;-)
I covered the same ground as you to end up with my first proposal, in
order, by the '=' to allow the keep the present syntax alone and to
have a new differing, and imposing double quoting of strings in order
to be able, if needed, later, to have variable names unquoted,
precisely for use in boot.cfg.
I think that my second proposal is the simplest, allowing not breaking
existing and introducing extensions without much typing.
--
Thierry Laronde <tlaronde +AT+ kergis +dot+ com>
http://www.kergis.com/
http://kertex.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
