From: Sam <sah@softcardsystems.com>
To: 9fans@cse.psu.edu
Subject: [9fans] plan9ports __efgfmt bug
Date: Sat, 28 Aug 2004 13:26:03 -0500 [thread overview]
Message-ID: <Pine.LNX.4.60.0408281153080.25905@athena> (raw)
FYI -
pitchfork% seq -w 9 10
009
10
pitchfork% seq -wf %2.1f 1 2
01. 0
02. 0
pitchfork%
Tracked down to __efgfmt where we do __fmtpad alignment
directly, then call __fmtcpy which also does __fmtpad alignment.
Removing the alignment from __fmtcpy gives the desired result
for seq, but probably breaks something else.
Sam
reply other threads:[~2004-08-28 18:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.60.0408281153080.25905@athena \
--to=sah@softcardsystems.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).