summaryrefslogtreecommitdiffstats
path: root/usr.bin/printf
Commit message (Collapse)AuthorAgeFilesLines
* 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
* Fixed warnx format errors in printf and csh, and snprintf format errorsbde1998-12-071-7/+11
| | | | | | in sh, by using separate macros for the 1, 2 and 3-arg calls to warnx. (The 3-arg warnx macro in sh/bltin/bltin.h used to require bogus dummy args.)
* Back out revision 1.10. It broke the build of sh, which compilesjdp1997-11-181-4/+5
| | | | this file with warnx() defined as a macro.
* Fix: too many arguments for format string in 4 calls to warnx().jdp1997-11-181-5/+4
|
* #include <unistd.h> for getopt(3) call.steve1997-08-071-0/+1
|
* Correct Synopsys section.charnier1997-08-041-3/+3
|
* compare return value from getopt against -1 rather than EOF, per the finalimp1997-03-291-1/+1
| | | | posix standard on the topic.
* -Wall cleaning.steve1996-12-141-2/+2
|
* Remove annoying -Wall warning.steve1996-10-061-1/+1
|
* When used as a shell builtin, this program decoded a subset of argumentspeter1996-10-011-4/+9
| | | | | | | | | | | known to printf(3) and then used printf() to format it... The only problem what the #define printf out1fmt. The code was behaving differently when run as a shell builtin since out1fmt() isn't printf(3). Simple hack. Print to a buffer and fputs (also #defined for sh) the result. This should fix the printf builtin problem in PR#1673, rather than leaving the call commented out. (printf.o was being statically linked in anyway, we might as well use it)
* Correctly match the format flags and their descriptions.mpp1996-04-091-1/+1
| | | | Submitted by: Dave Glowacki <dglo@ssec.wisc.edu>
* Move out some of the shell builtin bogosity from printf's source tojoerg1995-12-101-14/+1
| | | | sh's builtin/bltin.h.
* Remove trailing whitespace.rgrimes1995-05-301-2/+2
|
* Make the syntax checks for the format string more strict. The stringjoerg1995-05-071-12/+19
| | | | | | "%8*s" is no longer considered to be a valid format description. This closes PR bin/386.
* BSD 4.4 Lite Usr.bin Sourcesrgrimes1994-05-273-0/+687
OpenPOWER on IntegriCloud