From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] factotum & invalid entries
Date: Tue, 8 Feb 2005 11:42:20 -0500 [thread overview]
Message-ID: <ee9e417a0502080842237778c1@mail.gmail.com> (raw)
In-Reply-To: <4b12bf2586840d19f90100f81874ac0c@vitanuova.com>
> > - When you add a new key with the ctl file, here is what happens.
> > If there is already a key in factotum with exactly the same set
> > of public attr=val pairs, that key is replaced with the new one
> > and stays at the same place in the list. Otherwise, the new key
> > is appended to the list.
>
> does that mean it's now not possible to add a new key to the beginning
> of the list (the old default)?
Yes, that functionality is gone. No one ever seemed to need it,
and I don't know the right way to express it. I left the machinery
that made it possible. In general I think it's better not to use
ambiguous key patterns.
Russ
next prev parent reply other threads:[~2005-02-08 16:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 2:45 YAMANASHI Takeshi
2005-02-06 16:12 ` Russ Cox
2005-02-06 20:00 ` Tiit Lankots
2005-02-07 5:25 ` Lucio De Re
2005-02-07 5:42 ` arisawa
2005-02-07 6:03 ` Lucio De Re
2005-02-07 6:47 ` arisawa
2005-02-07 7:26 ` Lucio De Re
2005-02-07 8:09 ` arisawa
2005-02-07 8:55 ` Lucio De Re
2005-02-07 9:15 ` arisawa
2005-02-07 10:05 ` Lucio De Re
2005-02-08 5:12 ` Russ Cox
2005-02-08 16:36 ` rog
2005-02-08 16:42 ` Russ Cox [this message]
2005-02-08 16:55 ` Lucio De Re
2005-02-08 16:51 ` rog
2005-02-08 16:52 ` Devon H. O'Dell
2005-02-08 17:08 ` Lucio De Re
2005-02-08 17:10 ` rog
2005-02-13 20:03 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 2:35 YAMANASHI Takeshi
2005-02-14 3:42 ` Russ Cox
2005-02-04 9:31 [9fans] netpbm C H Forsyth
2005-02-05 18:26 ` [9fans] factotum & invalid entries Tiit Lankots
2005-02-05 20:12 ` Russ Cox
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=ee9e417a0502080842237778c1@mail.gmail.com \
--to=russcox@gmail.com \
--cc=9fans@cse.psu.edu \
/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).