summaryrefslogtreecommitdiffstats
path: root/share/man/man7/mdoc.7 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix a bunch of typos in various man pages.fcambus2020-08-271-3/+3
|
* Document the "powerpc64" argument to .Dt.schwarze2020-06-301-2/+3
| | | | | I intended to commit this after the arch is enabled, but jmc@ requests it right now.
* Briefly mention groff_mdoc(7) below SEE ALSO. While both authoritativeschwarze2020-06-251-5/+11
| | | | | | | manual pages document the same content, comparing can occasionally help in cases of doubt, and some people may prefer one style, some the other. While here, modernize a few .Lks from http:// to https://. OK jmc@
* Mention that the .Dd "date" argument is the date of the last change.schwarze2020-02-131-17/+4
| | | | | | Triggered by a question from Jason A. Donenfeld. While here, delete three COMPATIBILITY entries that i fixed some time ago.
* Introduce a new mdoc(7) macro .Tg ("tag") to explicitly mark a placeschwarze2020-01-191-3/+48
| | | | | | | | | | | | | | | as defining a term. Please only use it when automatic tagging does not work. Manual page authors will not be required to add the new macro; using it remains optional. HTML output is still rudimentary in this version and will be polished later. Thanks to kn@ for reminding me that i have been considering since BSDCan 2014 whether something like this might be useful. Given that possibilities of making automatic tagging better are running out and there are still several situations where automatic tagging cannot do the job, i think the time is now ripe. Feedback and no objection from millert@; OK espie@ inoguchi@ kn@.
* explain escaping of end-of-sentence characters;schwarze2019-07-151-2/+9
| | | | missing info reported by Ian <ropers at gmail dot com> on misc@
* socppc makes an extended visit to the bigbucket.deraadt2019-05-111-3/+2
| | | | ok kettenis
* clarify the difference between .Cm and .Ic;schwarze2019-04-241-10/+12
| | | | triggered by a question from Fabio Scotoni
* clarify how .%P is conventionally used;schwarze2019-04-231-3/+10
| | | | triggered by a question from Fabio Scotoni <fabio at esse dot ch>
* .Ppjmc2019-02-071-6/+4
| | | | | | | | .Bd ... -compact is better written as .Bd ...
* Remove the misleading statement ".No takes no arguments".schwarze2019-02-061-4/+4
| | | | | In facts, i works very similarly to .Em and .Sy. Triggered by a question from Kurt Mosiejczuk <kurt at cranky dot work>.
* Finally, stop abusing .Ss and .Sx to mark up macros, use .Ic insteadschwarze2018-12-231-796/+683
| | | | | | since these are clearly commands in a domain-specific language. As a nice side effect, the resulting list allows including the synopsis for each macro in the item head, reducing some repetitive verbiage.
* Simplify and clarify instructions for .Ql, and deprecate .Li.schwarze2018-12-231-35/+21
| | | | | | The macros .Ql, .Dl, and .Bd -literal leave no room for any valid use case for .Li whatsoever. General direction discussed with jmc@.
* Deprecate .Lp, use .Pp instead.schwarze2018-12-231-4/+4
| | | | | Simplicity matters, and fewer macros is simpler. OK jmc@
* Issue a STYLE message when normalizing the date format in .Dd/.TH.schwarze2018-07-281-6/+6
| | | | | | | | Leah Neukirchen pointed out that mdoclint(1) used to warn about a leading zero before the day number, so we know that both NetBSD and Void Linux want the message. It does no harm on OpenBSD because Mdocdate always does the right thing anyway. jmc@ agrees that it makes sense in contexts not using Mdocdate.
* Modernize documentation of .Ao and .Aq.schwarze2017-10-231-17/+41
| | | | | | | | | | | | I looked through our whole tree and failed to find a single use that is really convincing, except those with .Mt. Putting it around character and key names is somewhat widespread and maybe acceptable, even if hardly useful. So for now, delete the bogus examples and explain what these macros are really used for. Discourage the most common abuses. Triggered by a question from Raf Czlonka <rczlonka at gmail dot com>.
* update link to mandoc.bsd.lvschwarze2017-07-201-3/+3
|
* nits about trailing punctuation found with mandoc -Tlintschwarze2017-07-051-5/+5
|
* Clarify that .Ta as a line macro is a portability problem,schwarze2017-06-291-5/+5
| | | | | even though mandoc(1) handles it; triggered by a question from Yuri Pankov (illumos).
* Delete .St -p1003.1-2013.schwarze2017-06-241-7/+2
| | | | | | | It is an OpenBSD addition that did not get used a single time in three years, and groff did not pick it up either, so removing it does not affect any existing manuals anywhere. Cleanup suggested by jmc@, OK bentley@.
* minor markup simplificationsschwarze2017-06-101-3/+3
|
* Shorten the description of .sp and move it to roff(7).schwarze2017-05-051-18/+1
| | | | | If is not a macro but a low-level roff request and not recommended for use in manual pages.
* Clean up docs after today's .br and .ft code cleanup; simpler.schwarze2017-05-051-12/+2
|
* Surprisingly, groff does not support scaling units in .Bl -columnschwarze2017-02-161-6/+4
| | | | | | column width specifiers, so stop supporting them, too. As a side effect, this fixes an assertion failure that tb@ found with afl(1), triggered by: .Bl -column -4n
* document output spacing near delimitersschwarze2017-02-051-3/+5
|
* add "arm64" as a valid .Dt arch argument;schwarze2017-01-251-2/+3
| | | | inspired by deraadt@'s commit to usr.bin/mandoc/cgi.c
* Clarify how tabs after .It workschwarze2017-01-091-8/+20
| | | | | | | because this is a really nasty trap for the unwary. Triggered by a question from Abhinav Upadhyay <er dot abhinav dot upadhyay at gmail dot com> (NetBSD) on discuss@.
* Make the second, section number argument of .Xr mandatory.schwarze2016-12-281-6/+5
| | | | | | In fact, we have been requiring it for many years. The only reason to not warn when it was missing was excessive traditionalism - it was optional in 4.4BSD.
* link to http://mdocml.bsd.lv/mdoc/ below SEE ALSO;schwarze2016-10-111-2/+8
| | | | tweak and OK jmc@
* Retire zaurus, as it hasn't made the EABI jump and will be permanently brokenguenther2016-09-031-4/+3
| | | | shortly when we use the hardware thread register in userland
* no more sparc;jmc2016-09-011-3/+2
|
* no more armish;jmc2016-08-101-3/+2
|
* remove hppa64 port, which we never got going beyond broken single users.deraadt2016-05-111-3/+2
| | | | | | hppa reverse-stack gives us a valuable test case, but most developers don't have a 2nd one to proceed further with this. ok kettenis
* un-vax;jmc2016-03-101-3/+2
|
* sync and update the list of supported archs;jmc2015-12-011-5/+2
| | | | feedback/ok schwarze
* Specify option ordering in the DESCRIPTION sectionguenther2015-11-011-2/+7
| | | | ok and tweaks jmc@ schwarze@
* 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@
* typos.sobrado2015-09-231-3/+3
|
* Avoid .Ns right after .Pf, it's pointless.schwarze2015-09-141-3/+3
| | | | In some cases, do additional cleanup in the immediate vicinity.
* remove the first comma from constructs like ", and," and ", or,": you can usejmc2015-03-131-3/+3
| | | | | "and" and "or" to join sentence clauses, and you can use commas, but both hinders reading;
* improve NAME section diagnostics;schwarze2015-02-231-7/+5
| | | | confusing messages reported by Jan Stary <hans at stare dot cz>
* 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-291-102/+19
| | | | | | | | 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.
* change spelling of centre to center. consistent with other man pages,tedu2015-01-201-5/+5
| | | | | 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>.
* describe .Ql more precisely;schwarze2014-12-311-4/+7
| | | | defect pointed out by Steffen Nurpmeso <sdaoden at yandex dot com>
* Improve documentation of the header/footer macros .Dt, .Os, .TH:schwarze2014-12-281-27/+23
| | | | | | * State the defaults for .Os and the fourth .TH argument. * Sync the section titles, and stop advertising obscure sections that aren't actually fully supported and certainly not recommended for use.
* delete three standard abbreviations that areschwarze2014-11-301-14/+4
| | | | | | * no longer used in our tree * not used in any of NetBSD, FreeBSD, or DragonFly * not supported by groff
* Retire support for CSRG supplementary document titles. These areschwarze2014-11-281-34/+4
| | | | | long obsolete and were never written in mdoc(7) in the first place. Removes 100 lines from source files.
* Fix the obsolete .Db (toggle debug mode) macro to ignore its argumentsschwarze2014-11-271-9/+8
| | | | | and not trigger an assertion when there is more than one argument; the latter found by jsg@ with afl.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.