summaryrefslogtreecommitdiffstats
path: root/usr.bin/mandoc/mandoc.1 (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* Delete the arbitrary range restriction for -Owidth.schwarze2017-06-131-4/+3
| | | | | | | We provide users with tools. We don't attempt to prevent them from using them in stupid ways: depending on the context, not every stupid-looking use is necessarily actually stupid, and not every stupidity can be automatically detected anyway, so don't even try.
* style message about missing .Fn markup; inspired by mdoclintschwarze2017-06-111-2/+11
|
* style message about missing blank before trailing delimiter;schwarze2017-06-101-2/+7
| | | | inspired by mdoclint(1), and jmc@ considers it useful
* Portable mandoc just got a warning about unknown .Lb namesschwarze2017-06-081-2/+8
| | | | | which we don't want in OpenBSD, but let's keep the message table and the manual page in sync.
* style checks related to .Er; inspired by mdoclint(1)schwarze2017-06-071-2/+32
|
* Minimal implementation of the roff(7) .ce request (center a numberschwarze2017-06-061-2/+7
| | | | | of input lines without filling). Contrary to groff, high-level macros abort .ce mode for now.
* enable -Wstyle by default in -Tlint; OK jmc@schwarze2017-06-031-4/+4
|
* STYLE message about full stop at the end of .Nd; inspired by mdoclint(1)schwarze2017-06-011-2/+7
|
* STYLE message about missing use of Ox/Nx/Fx/Dx; OK jmc@ wiz@schwarze2017-05-311-2/+12
|
* tweak previous;jmc2017-05-301-3/+3
|
* STYLE message about useless macros we don't want (Bt Tn Ud);schwarze2017-05-301-2/+14
| | | | not a WARNING because they don't endanger portability
* Delete the -T xhtml command line option.schwarze2017-05-171-4/+1
| | | | | It has been obsolete for more than two years. Use -T html.
* Modernize an example showing antiquated syntax,schwarze2017-05-171-4/+3
| | | | and delete an example showing the arcane -W stop option.
* missing space between macro arg and punctuation;jmc2017-05-161-2/+2
|
* Introduce a new mandoc(1) message level, -W style, below -W warning.schwarze2017-05-161-13/+32
| | | | | | | | | | | | | Switch -W all from meaning -W warning to meaning -W style. The meaning of -T lint does *not* change, it still implies -W warning. No messages on the new level yet, but they will come. Usually, i do not lightly make the user interface larger. But this has been planned for years, and EXIT STATUS 1 was reserved for it all the time. The message system is now stable enough to finally implement it. jmc@ regarding the concept: "really good idea"
* simplify the SYNOPSIS as well, just like the option lists;schwarze2017-03-271-4/+4
| | | | suggested by and OK jmc@
* For some options that are rarely needed in mandoc(1),schwarze2017-03-271-15/+5
| | | | | delete the descriptions and point to man(1) instead. Inspired by apropos.1 rev. 1.35.
* Simplify: mention at one place that -fkl override each other,schwarze2017-03-271-17/+5
| | | | | rather than stating it separately for each option. Suggested, OKed, and tweaked by jmc@.
* simplify .Nd; to display manuals, use man(1) instead;schwarze2017-03-211-3/+3
| | | | OK jmc@
* Silently ignore invalid -m input formats rather than erroring out.schwarze2017-03-201-61/+31
| | | | | | As observed by Jan Stary <hans at stare dot cz>, this is useful such that after 'alias man="man -m $HOME/man"', 'man -l foo.1' still works. Simplify and shorten the description of -m, and use .Ic for macros.
* Correct description of MANPATH, and a few more improvementsschwarze2017-03-181-5/+18
| | | | to the ENVIRONMENT section; OK jmc@
* Document that -T markdown produces ASCII output, and the impliedschwarze2017-03-081-2/+12
| | | | | | | | limitations. Of course, we could write UTF-8 output instead, but even the CommonMark specification doesn't require parsers to support that, so portability would be doubtful. While here, provide a link to the CommonMark specification.
* Using .Nd only makes sense in the NAME section.schwarze2017-03-061-2/+10
| | | | | Warn if that macro occurs elsewhere. Triggered by a question from Dag-Erling Smoergrav <des @ FreeBSD>.
* Make the description of -K autodetection easer to understand.schwarze2017-03-041-13/+21
| | | | Basic idea suggested by jmc@, OK jmc@.
* new -mdoc -Tmarkdown output mode; OK millert@ reyk@ tb@;schwarze2017-03-031-3/+33
| | | | thanks to reyk@ and to Vsevolod at FreeBSD for suggesting it
* In -Ttree output mode, show the BROKEN node flag andschwarze2017-02-101-2/+15
| | | | provide a -Onoval output option to show the unvalidated tree.
* add missing HISTORY informationschwarze2017-01-311-2/+15
|
* Add a warning "new sentence, new line".schwarze2017-01-281-2/+6
| | | | | | | | | This does not attempt to pinpoint each and every offender, but instead tries very hard to avoid false positives: Currently, there are only two false positives in the whole OpenBSD base system. Only do this in mdoc(7), not in man(7), because manuals written in man(7) typically have much worse problems than this. OK jmc@ on a previous version of the patch
* bug was fixed, delete the BUGS sectionschwarze2017-01-211-11/+2
|
* show meta data for -Ttree outputschwarze2017-01-121-3/+11
|
* Introduce flags NODE_NOSRC and NODE_NOPRT for AST nodes.schwarze2017-01-101-2/+8
| | | | | | | | | Use them to mark generated nodes and nodes that shall not produce output. Let -Ttree output mode display these new flags. Use NODE_NOSRC for .Ar, .Mt, and .Pa default arguments. Use NODE_NOPRT for .Dd, .Dt, and .Os. These will help to make handling of text production macros more rigorous.
* Stricter validation of the NAME section, in particular:schwarze2017-01-081-7/+14
| | | | | | | - require a comma between names - reject all other text nodes - reject all empty Nm below NAME, not only in the leading position - reject Nm after Nd
* sort options list; the same as jmc@ did in man.1 rev. 1.18schwarze2017-01-061-6/+6
|
* spelling fix;jmc2016-12-281-2/+2
|
* Make the second, section number argument of .Xr mandatory.schwarze2016-12-281-2/+9
| | | | | | 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.
* simplify: use one stylesheet rather than two; from bentley@schwarze2015-11-051-5/+5
|
* If a .Bd block has no arguments at all, drop the block and only keepschwarze2015-10-301-2/+9
| | | | | its contents. Removing a gratuitious difference to groff output found after a related bug report from krw@.
* tweak previous;jmc2015-09-261-3/+4
|
* briefly document -T tree outputschwarze2015-09-261-2/+42
|
* Remove the warning about children of .Vt blocks because actually,schwarze2015-09-141-9/+2
| | | | | | | .Vt type global_variable No = Dv defined_constant ; is the best way to specify in the SYNOPSIS how a global variable is initialized in the rare case where that matters. Issue noticed by jmc@.
* No need to hardcode /usr/bin/ as the path to more(1); helps portability.schwarze2015-04-031-3/+4
| | | | | We don't hardcode the paths to gunzip(1) and cmp(1) either. Discussed with ajacoutot@.
* Escape punctuation characters that have a different meaning in -Tpdf.bentley2015-03-291-3/+3
| | | | | | | | ~, `, 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@
* refering -> referring;jmc2015-03-271-2/+2
|
* Modernize documentation by inserting blanks between option lettersschwarze2015-03-271-58/+55
| | | | | | and option arguments, except for -m because "-m an" and "-m andoc" look just too weird. Of course, the traditional form without the blank will continue to work.
* improve NAME section diagnostics;schwarze2015-02-231-10/+20
| | | | confusing messages reported by Jan Stary <hans at stare dot cz>
* clean up post_dt() validation function;schwarze2015-02-161-1/+4
| | | | improved diagnostics, minus six lines of code
* Delete the -V option. It serves no purpose but keeps confusing people.schwarze2015-02-161-5/+3
|
* Explain all WARNING, ERROR, and UNSUPP messages in the DIAGNOSTICS section.schwarze2015-02-101-2/+1093
| | | | | | Feedback provided by jmc@ some time ago helped me to get this much more concise than my initial attempt. "i'm fine with it going in" jmc@
* Radical cleanup of COMPATIBILITY sections:schwarze2015-01-291-109/+10
| | | | | | | | 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.
* tweak previous;jmc2015-01-201-2/+2
|
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.