From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum apop protocol is incorrect
Date: Mon, 15 Dec 2003 09:26:07 -0500 [thread overview]
Message-ID: <c232ddfa6f3495455c058e033f4d27c7@plan9.bell-labs.com> (raw)
In-Reply-To: <2a6430817769660bb980e1e946263c2c@plan9.escet.urjc.es>
[-- Attachment #1: Type: text/plain, Size: 82 bytes --]
grep varargck.*" /sys/include/*.h
Some are overloaded, H, D, and M for example.
[-- Attachment #2: Type: message/rfc822, Size: 4502 bytes --]
[-- Attachment #2.1.1: Type: text/plain, Size: 194 bytes --]
There are so many uses of %<blah>, that I miss something like
/sys/lib/%master, or some convetion to aid programs to choose
flags that won't be later used by other libraries.
Is it just me?
[-- Attachment #2.1.2: Type: message/rfc822, Size: 2228 bytes --]
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum apop protocol is incorrect
Date: Fri, 12 Dec 2003 22:55:30 -0500
Message-ID: <6786cb2c3839f91e170e726ac4ac0805@plan9.bell-labs.com>
From: Dan Cross <cross@math.psu.edu>
David Presotto <presotto@closedmind.org> writes:
> I really dinna want to change %H. The logical thing there would be to
> have a %h and a %H but little 'h' is already taken as a flag.
>
> I'll just fix apop with your suggestion.
Many of the format specifiers in print(2) already can already be
modified by flags; case in point: what 'h' does to %d. How about
adding a flag to %H that forces it to use a lowercase map, instead of
an undercase map?
- Dan C.
OK, %lH now means lower case hexdump.
%luhs means print out correct spelling of the string pointed
to by the argument.
next prev parent reply other threads:[~2003-12-15 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 3:55 David Presotto
2003-12-14 21:59 ` Dan Cross
2003-12-15 8:49 ` Fco.J.Ballesteros
2003-12-15 14:26 ` David Presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-12 19:59 David Presotto
2003-12-13 2:42 ` Dan Cross
2003-12-13 2:47 ` Dan Cross
2003-12-12 19:47 Richard Miller
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=c232ddfa6f3495455c058e033f4d27c7@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).