Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: printf builtin
- X-seq: zsh-workers 15852
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: PATCH: printf builtin
- Date: Fri, 21 Sep 2001 14:42:51 +0000
- In-reply-to: <3BAB1D55.8258B237@xxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <3BAA3F2A.86D73181@xxxxxxxxxxx> <1010920203312.ZM16858@xxxxxxxxxxxxxxxxxxxxxxx> <3BAB1D55.8258B237@xxxxxxxxxxx>
On Sep 21, 11:58am, Oliver Kiddle wrote:
}
} I'll put the ksh print -f functionality on my todo list though. It makes
} sense to combine the -b, -m, -s, -o, -O, -i, -u, -p, -z, -D and -P
} options with -f. -r, -R, -n, -l, -N and -c would make no sense to
} combine. -l and -N would be fairly redundant because it would be better
} to use a format of "%s\n" or "%s\0" so they should perhaps then be
} declared obsolete. -P (and maybe -D) is also perhaps slightly
} unfortunate because a %P format specification might be better.
This all sounds fine except that I don't see any reason to declare any of
the existing options obsolete.
There is a bit of an issue with respect to combining with -s and -z, as
those at present imply -n, and -z also implies -r; the question is what
to do with trailing newlines if they appear in the format string.
(This'll be my last message until late Sunday, as I'm off to a wedding in
Yosemite National Park.)
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
Messages sorted by:
Reverse Date,
Date,
Thread,
Author