summaryrefslogtreecommitdiffstats
path: root/share/man/man7 (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Mention that the first argument of .Pf does not need escaping.schwarze2015-10-111-6/+10
| | | | | While here, make the first sentence regarding .Pf more concise. OK jmc@
* basic grammar fixes;jmc2015-09-271-3/+3
|
* typo, resolve_lib->resolve-lib; from Theo Buehlersthen2015-09-271-3/+3
|
* check-conflicts was replaced with check-problems; from Theo Buehlersthen2015-09-271-3/+3
|
* typos.sobrado2015-09-232-10/+10
|
* punctuation and upper case fixes; Michael Reed <m dot reed at mykolab dot com>schwarze2015-09-211-6/+6
|
* Mark up login.conf(5) variable names as .Va, not .Ar,schwarze2015-09-211-4/+4
| | | | | like in the login.conf(5) manual itself. Patch from Michael Reed <m dot reed at mykolab dot com>.
* Avoid .Ns right after .Pf, it's pointless.schwarze2015-09-141-3/+3
| | | | In some cases, do additional cleanup in the immediate vicinity.
* use .Vt for extern variables in the SYNOPSIS, not .Arschwarze2015-09-101-3/+3
|
* Recommend an unambiguous escape for minus signs instead of \-.bentley2015-09-011-7/+7
| | | | | | | | | | | | | | | | | | | | | | Historically, \- was used in troff for three cases: flags/pathnames, en dashes, and minus signs. mandoc_char(7) currently recommends it for minus signs, recommends \(en for en dashes, and doesn't mention flags/pathnames. In the old days, nroff rendered \- as ASCII '-', and troff rendered it as en dash/minus (which were visually indistinguishable). In Unicode, en dashes and minus signs are semantically distinct and encoded differently (U+2013 for en dash, U+2212 for minus), and often rendered differently too. Meanwhile ASCII '-' has been renamed "hyphen-minus" and fonts typically render it closest to a hyphen, not a minus. There is very little consistency across roff implementations and output formats for what Unicode character \- corresponds to. So at least for minus signs, change the recommendation to the unambiguous \(mi escape. ok jmc@ (after reams of discussion)
* Parse and ignore the escape sequences \, and \/ (italic corrections).schwarze2015-08-291-2/+8
| | | | | | | | Actually using these is very stupid because they are groff extensions and other roff(7) implementations typically print unintended characters at the places where they are used. Nevertheless, some manuals contain them, for example ocserv(8). Problem reported by Kurt Jaeger <pi at FreeBSD>.
* Implement the escape sequence \\$*, expanding to all argumentsschwarze2015-08-291-2/+4
| | | | | | of the current user-defined macro. This is another missing feature required for ocserv(8). Problem reported by Kurt Jaeger <pi at FreeBSD>.
* Mark up command arguments properly using Cm.bentley2015-08-241-60/+60
| | | | From Michael Reed.
* adjust list width for previous;jmc2015-08-241-2/+2
|
* /usr/share/sysmerge -> /var/sysmergeajacoutot2015-08-241-6/+6
| | | | | requested by several discussed with deraadt@
* add /var/run/rc.d/jmc2015-08-041-2/+6
| | | | help/ok schwarze
* two revisions ago i bungled the addition of radiusd -jmc2015-07-301-2/+2
| | | | | | fix that now; ok deraadt
* switch references from sudo to doas;jmc2015-07-302-8/+5
| | | | ok deraadt
* some radius bits; help/ok yasuokajmc2015-07-251-2/+5
|
* Kill trailing blank; no text change.schwarze2015-06-121-3/+3
| | | | | Issue found by Tony Sim <y2s1982 at gmail dot com> during today's BSDCan Doc Sprint.
* Implement the roff(7) `r' (register exists) conditional.schwarze2015-05-311-4/+7
| | | | | Missing feature found by Markus <Waldeck at gmx dot de> in Debian's bash(1) manual page.
* Replace the kludge for the \z escape sequence by an actualschwarze2015-04-291-6/+3
| | | | | | | | implementation. As a side effect, minus ten lines of code. As another side effect, this also fixes the assertion failure that used to be triggered by "\z\o'ab'c" at the beginning of an output line, found by jsg@ with afl (test case 022/Apr27).
* double word fix; from david vasekjmc2015-04-251-3/+3
|
* no more tip(1); ok nicmjmc2015-04-241-3/+3
|
* Escape punctuation characters that have a different meaning in -Tpdf.bentley2015-03-292-43/+43
| | | | | | | | ~, `, and ' get translated to non-ASCII characters by most troff implementations when generating PostScript/PDF output. When the original ASCII character is meant, it needs to be manually escaped. discussed with jmc@ schwarze@; ok schwarze@
* Document that certain stand-alone accents need escaping in rare cases toschwarze2015-03-271-3/+25
| | | | | prevent them from being converted to Unicode replacements in PDF output. Issue found by bentley@, OK jmc@ bentley@.
* remove the first comma from constructs like ", and," and ", or,": you can usejmc2015-03-132-6/+6
| | | | | "and" and "or" to join sentence clauses, and you can use commas, but both hinders reading;
* Reduce usage of predefined strings in manpages.bentley2015-02-281-24/+24
| | | | | | | | | | | Predefined strings are not very portable across troff implementations, and they make the source much harder to read. Usually the intended character can be written directly. No output changes, except for two instances where the incorrect escape was used in the first place. tweaks + ok schwarze@
* document the quirks cve mechanism. Better late than neverespie2015-02-231-2/+14
|
* improve NAME section diagnostics;schwarze2015-02-231-7/+5
| | | | confusing messages reported by Jan Stary <hans at stare dot cz>
* Let .it accept numerical expressions, not just numerical constants.schwarze2015-02-171-6/+11
| | | | | | | For .it, ignore scaling units in roff_getnum(). Inside parentheses, skip whitespace after a sign in roff_getnum(). Parse and ignore unary plus in roff_getnum(). As a bonus, get rid of the only call to mandoc_strntoi() in roff.c.
* Mark up email addresses semantically with Mt.bentley2015-02-171-3/+4
| | | | ok schwarze@
* Tweak the wording to avoid the possible misunderstanding that .Inschwarze2015-02-151-7/+8
| | | | | could only be used in the SYNOPSIS section. It is fine anywhere. Issue noticed by bentley@.
* Radical cleanup of COMPATIBILITY sections:schwarze2015-01-295-202/+82
| | | | | | | | Remove lots of lies, dozens of irrelevant implementation details, and all references to groff versions older than 1.17. Move relevant information to the pages where it belongs, and out of mandoc(1) in particular. Add some missing general remarks to roff(7), where it fits the character and purpose of the page much better.
* implement the tbl(7) "center" layout optionschwarze2015-01-281-3/+2
|
* Rework tbl(7) layout parsing:schwarze2015-01-261-10/+25
| | | | | | | | | | | * Continue parsing even if part of the input is invalid. * Do not require whitespace between cell specifications. * Allow tabs as well as blanks between modifiers. * Mark the 'm' modifier as unsupported. * Parse and ignore the 'p' and 'v' modifiers. * Better warning and error messages. * Get rid of a static buffer. Improved functionality but minus 50 lines of code.
* More improvements regarding tbl(7) options.schwarze2015-01-261-40/+42
| | | | | | | | | * Treat "allbox" as an alias for "box" for now. * Parse and ignore the GNU tbl "nowarn" option. * For separation, allow spaces, tabs, and commas only. * Mark eqn(7) within tbl(7) as unsupported. * Simplify the option table. * Improve and sort documentation.
* Strangely, ignoring the roff(7) .na request was implemented in the man(7)schwarze2015-01-241-7/+3
| | | | | parser. Simplify the code by moving it into the roff(7) parser, also making it work for mdoc(7).
* change .Cm to .Ar for macro argumentsschwarze2015-01-241-19/+19
|
* Support .RE with an argument; needed for audio/pms(1).schwarze2015-01-241-4/+24
|
* While ignoring the .ta (set tab stops) and .ti (temp indent) requestsschwarze2015-01-231-4/+4
| | | | | | is sometimes harmless, it often causes seriously ugly output, so flag these requests as unsupported rather than ignoring them. Discussed with naddy@.
* zap trailing whitespace;jmc2015-01-231-2/+2
|
* Wonders of roff(7): Integer numbers in numerical expressions can carryschwarze2015-01-231-2/+10
| | | | | scaling units, and some manuals (e.g. in devel/grcs) actually use that, so let's support it. Missing feature reported by naddy@.
* tweak previous; ok schwarzejmc2015-01-211-2/+2
|
* Rudimentary implementation of the roff(7) \o escape sequence (overstrike).schwarze2015-01-211-6/+7
| | | | | | This is of some relevance because the pod2man(1) preamble abuses it for the icelandic letter Thorn, instead of simply using \(TP and \(Tp. Missing feature found by sthen@ in DateTime::Locale::is_IS(3p).
* tweak previous; ok schwarzejmc2015-01-201-4/+4
|
* Split the -Werror message level into -Werror (broken manual, probablyschwarze2015-01-201-54/+724
| | | | | | | | | | | | | using mandoc is better than using groff) and -Wunsupp (manual using unsupported low-level roff(7) feature, probably using groff is better than using mandoc). Once this feature is complete, it is intended to help porting, making the decision whether to USE_GROFF easier. As a first step, distinguish four classes of roff(7) requests: 1. Supported (currently 24 requests) 2. Currently ignored because unimportant (120) -> no message 3. Ignored for good because insecure (14) -> -Werror 4. Currently unsupported (68) -> these trigger the new -Wunsupp messages
* one more "center"; tedu forgot to use -i, i think...jmc2015-01-201-2/+2
|
* change spelling of centre to center. consistent with other man pages,tedu2015-01-205-18/+18
| | | | | the name of the macro being described, and look(1). ok jmc
* Given the excessively technical description in the old mdoc_samples(7)schwarze2015-01-031-8/+17
| | | | | | | | | | manual and its successor groff_mdoc(7), i always considered .Ql as purely physical markup, but it turns out describing it better allows to give it a semantic meaning (in-line literal display) that doesn't contradict existing usage. One less physical, one more semantic macro, yay! Found in a discussion with Steffen Nurpmeso <sdaoden at yandex dot com>.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.