summaryrefslogtreecommitdiffstats
path: root/usr.bin/printf/printf.1
Commit message (Collapse)AuthorAgeFilesLines
* Added the EXIT STATUS section where appropriate.ru2005-01-171-1/+1
|
* Fix a markup nit and a misplaced full stop in previous.tjr2004-07-031-2/+2
| | | | Noticed by: ru
* Document missing multibyte character support in utilities specifiedtjr2004-07-031-1/+6
| | | | by POSIX.
* Deal with double whitespace.ru2004-07-031-4/+4
|
* Mechanically kill hard sentence breaks.ru2004-07-021-7/+14
|
* s/latter/former/das2004-06-051-1/+1
|
* - Document the %a, %A, and %F format specifiers.das2004-06-051-3/+31
| | | | | - Document the way infinity and NaN are printed. - Un-document the non-existent %w specifier.
* Kill excessive whitespace between macro arguments.keramida2002-07-151-5/+5
|
* Typo: characer -> characterkeramida2002-05-311-1/+1
|
* mdoc(7) police: lint.ru2002-05-301-10/+8
|
* - printf shouldn't bail out if a conversion fails, it should just keepjmallett2002-04-231-5/+27
| | | | | | | | | | | | | | | processing them. - \c escape to immediately stop output (similar to echo's \c) - \0NNN should be allowed for octal character escapes (instead of just \NNN) - %b conversion, which is like %s but interprets \n \t etc. inside the string is missing. And I may not be any poet, but in lieu of an in-tree regression test: ref5% ./printf '%s%b%b%c%s%d\n' 'PR' '\0072' '\t' '3' '56' 0x10 PR: 35616 Submitted by: tjr MFC after: 1 week
* Use `The .Nm utility'charnier2002-04-201-2/+3
|
* Replace reference to ANSI C draft with standard.ru2002-01-161-4/+1
| | | | PR: docs/30731
* The RETURN VALUES section is not appropriate for section 1 manualdd2001-11-231-3/+2
| | | | | pages; rename it to DIAGNOSTICS. Also use the .Ex macro while I'm here.
* Remove the printf builtin command from sh(1), which command is notknu2001-11-201-10/+0
| | | | | | | | | | | | used so often that it's worth keeping it as a builtin. Now that all the printf invocations from within the system startup scripts, we can safely remove it. Urged by: sheldonh :) No MFC is planned so far because it may break compatibility and violate POLA.
* Remove whitespace at EOL.dd2001-07-151-3/+3
|
* mdoc(7) police: sort SEE ALSO xrefs (sort -b -f +2 -3 +1 -2).ru2001-07-061-2/+2
|
* mdoc(7) police: mark LC_NUMERIC with .Dv.ru2001-02-101-1/+2
|
* Localize it (LC_NUMERIC)ache2001-02-101-0/+3
|
* Prepare for mdoc(7)NG.ru2000-12-191-2/+5
|
* Revert to 1.8. I misread the sentence and its context.chris2000-07-211-2/+1
|
* Properly document %.0f behavior.chris2000-07-211-1/+2
|
* Document truncation of strings when a NUL character is reached in a formatchris2000-01-191-0/+6
| | | | | | | string. PR: 15929 Submitted by: Daniel Hagan <dhagan@cs.vt.edu>
* Correct some hard sentence breaks. Only those surrounding the previoussheldonh1999-09-141-2/+2
| | | | | | | | commit and those which cause ugly nroff output have been fixed, since the purpose of the style guideline which they contravene is to reduce the sizes of deltas. Reported by: bde
* Improve shell documentation:sheldonh1999-09-081-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | * Consistently misspell built-in as builtin. * Add a builtin(1) manpage and create builtin(1) MLINKS for all shell builtin commands for which no standalone utility exists. These MLINKS replace those that were created for csh(1). * Add appropriate xrefs for builtin(1) to the csh(1) and sh(1) manpages, as well as to the manpages of standalone utilities which are supported as shell builtin commands in at least one of the shells. In such manpages, explain that similar functionality may be provided as a shell builtin command. * Improve sh(1)'s description of the cd builtin command. Csh(1) already describes it adequately. Replace the cd(1) manpage with a builtin(1) MLINKS link. * Clean up some mdoc problems: use Xr instead of literal "foo(n)"; use Ic instead of Xr for shell builtin commands. * Undo English contractions. Reviewed by: mpp, rgrimes
* $Id$ -> $FreeBSD$peter1999-08-281-1/+1
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | track. The $Id$ line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* Correct Synopsys section.charnier1997-08-041-3/+3
|
* Correctly match the format flags and their descriptions.mpp1996-04-091-1/+1
| | | | Submitted by: Dave Glowacki <dglo@ssec.wisc.edu>
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-271-0/+272
OpenPOWER on IntegriCloud