From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] rio
Date: Sun, 30 Jul 2000 10:53:31 -0400 [thread overview]
Message-ID: <200007301453.KAA25535@cse.psu.edu> (raw)
Stupid bug introduced in rio, caused by our attempts to clean up
uses of %.*s. /sys/src/cmd/rio/xfid.c:508 is missing an argument.
diff /n/dump/2000/0730/sys/src/cmd/rio/xfid.c xfid.c
508c508
< sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt));
---
> sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt), x->data);
The distributed binary is OK, but if you build from the unfixed
source all hell will break loose.
Mea culpa. The compiler warns you and in all the furious building
I missed the warning.
-rob
next reply other threads:[~2000-07-30 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 14:53 rob pike [this message]
2000-11-22 6:01 rob pike
2006-04-28 16:36 [9fans] troff in plan9port with a problem in tr2post Russ Cox
2006-04-28 16:46 ` [9fans] rio Sha0lin
2006-04-29 13:26 ` Sergey Zhilkin
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=200007301453.KAA25535@cse.psu.edu \
--to=rob@plan9.bell-labs.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).