From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] buglet in 9load
Date: Wed, 8 Jan 2003 00:02:54 -0800 [thread overview]
Message-ID: <200301080802.h0882snd095308@ducky.net> (raw)
I just accidently created a plan9.ini file like this:
menuitem=foo
menuitem=bar
menuitem=baz
menudefault=foo
...
[foo]
...
[bar]
...
(I forgot to provide a [baz] configuration block.)
When I tried to boot up, 9load correctly complained that I had
provided no [baz] configuration block.
But then, without giving me a chance to choose between either of
the two valid configurations foo and bar, it went ahead and booted
up. And it turned out that, rather than having booted with the
specified default foo configuration, it had tried to boot baz
(that is, $menuitem in the environment after boot was baz).
next reply other threads:[~2003-01-08 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 8:02 Mike Haertel [this message]
2003-01-09 3:09 ` jmk
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=200301080802.h0882snd095308@ducky.net \
--to=mike@ducky.net \
--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).