midfavila
/
sbase
1
0
Fork 0
Code Issues Pull Requests Projects Releases 1 Wiki Activity
sbase/printf.1

35 lines
795 B
Groff
Raw Normal View History

Use ISO-date-format in manpages The one specified by mdoc is hard to read for non-native speakers from countries which read the date day-first (like Germany, Greece, North-Korea, Swamp,...). This is also consistent with how we generally specify dates at suckless.org.
2015-10-08 11:15:08 -04:00
.Dd 2015-10-08
Add printf.1
2014-09-29 09:35:35 -04:00
.Dt PRINTF 1
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
.Os sbase
Add printf.1
2014-09-29 09:35:35 -04:00
.Sh NAME
.Nm printf
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
.Nd print formatted data
Add printf.1
2014-09-29 09:35:35 -04:00
.Sh SYNOPSIS
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff.
2015-01-30 15:17:58 -05:00
.Nm
Add printf.1
2014-09-29 09:35:35 -04:00
.Ar format
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
.Op Ar arg ...
Add printf.1
2014-09-29 09:35:35 -04:00
.Sh DESCRIPTION
add some mandoc pages and fix some warnings - add .Os, it is mandatory. - don't redeclare .Nm when it's not needed. - fix some warnings (checked with mandoc -Tlint). - remove some leftover old stuff.
2015-01-30 15:17:58 -05:00
.Nm
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
writes formatted data according to
Add printf.1
2014-09-29 09:35:35 -04:00
.Ar format
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
using each
.Ar arg
until drained.
Add printf.1
2014-09-29 09:35:35 -04:00
.Pp
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
.Nm
interprets the standard escape sequences \e\e, \e', \e", \ea, \eb, \ee,
Change the note in printf.1 on octal escapes
2016-02-20 15:51:05 -05:00
\ef, \en, \er, \et, \ev, \exH[H], \eO[OOO], the sequence \ec, which
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
terminates further output if it's found inside
.Ar format
or a %b format string, the format specification %b for an unescaped string and all C
Add printf.1
2014-09-29 09:35:35 -04:00
.Xr printf 3
Add printf(1) This is a particularly interesting program. I managed to implement everything according to POSIX except how octal escapes are specified in the standard, which is yet another format compared to the one demanded for tr(1). This not only confuses people, it also adds unnecessary cruft for no real gain. So in order to be able to use unescape() easily and for consistency, I used our initial format \o[oo] instead of \0[ooo]. Marked as optional is UTF-8 support for %c in the POSIX specification. Given how well-developed libutf has become, doing this here was more or less trivial, putting us yet again ahead of the competition.
2015-02-15 08:46:58 -05:00
format specifications ending with csdiouxXaAeEfFgG, including variable width and precision.
Add printf.1
2014-09-29 09:35:35 -04:00
.Sh STANDARDS
The
.Nm
utility is compliant with the
POSIX 2013 audit Mostly manpage-shuffling according to the changes in the corrigendum, wording changes and more idiomatic expressions. All this is finished up by marking the POSIX 2013 conformant tools with .St -p1003.1-2013 which is not available in older mandoc builds or nroff, but which reflects what we actually did, so who cares? This is a huge step and it's not far until we can release sbase 0.1.
2015-03-27 12:22:48 -04:00
.St -p1003.1-2013
Remove the octal note in printf.1
2016-02-20 15:46:52 -05:00
specification.
Change the note in printf.1 on octal escapes
2016-02-20 15:51:05 -05:00
.Pp
The possibility of specifying 4-digit octals is an extension to that specification.