summaryrefslogtreecommitdiffstats
path: root/share/man/man7 (follow)
Commit message (Collapse)AuthorAgeFilesLines
...
* 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@
* The .HP macro was deprecated by groff, and that makes senseschwarze2018-12-161-12/+20
| | | | | | because it serves no real purpose and works poorly with HTML. While here, describe the section argument of .TH, clarify the syntax display of .TP, and polish some wordings.
* minor polishing, in parts related to functional improvements in the past,schwarze2018-12-161-22/+30
| | | | and also adding some cross references for important escape sequences
* Yet another round of improvements to manual font selection.schwarze2018-12-151-40/+78
| | | | | | | | Unify handling of \f and .ft. Support \f4 (bold+italic). Support ".ft BI" and ".ft CW" for terminal output. Support the .ft request in HTML output. Reject the bogus fonts \f(C1, \f(C2, \f(C3, and \f(CP.
* Several improvements to escape sequence handling.schwarze2018-12-152-7/+52
| | | | | | | | | | | | | | | | | | | | | | | * Add the missing special character \_ (underscore). * Partial implementations of \a (leader character) and \E (uninterpreted escape character). * Parse and ignore \r (reverse line feed). * Add a WARNING message about undefined escape sequences. * Add an UNSUPP message about unsupported escape sequences. * Mark \! and \? (transparent throughput) and \O (suppress output) as unsupported. * Treat the various variants of zero-width spaces as one-byte escape sequences rather than as special characters, to avoid defining bogus forms with square brackets. * For special characters with one-byte names, do not define bogus forms with square brackets, except for \[-], which is valid. * In the form with square brackets, undefined special characters do not fall back to printing the name verbatim, not even for one-byte names. * Starting a special character name with a blank is an error. * Undefined escape sequences never abort formatting of the input string, not even in HTML output mode. * Document the newly handled escapes, and a few that were missing. * Regression tests for most of the above.
* zap trailing whitespace;jmc2018-12-121-3/+3
|
* Let cells containing nothing but \^ extend the cell above.schwarze2018-11-251-8/+14
| | | | Missing feature reported by Pali dot Rohar at gmail dot com.
* punctuation and macro can go on the same line;jmc2018-11-161-3/+2
|
* kill INDEX thoroughly, point users at portslist, sqlports, pkglocatedbespie2018-11-161-15/+16
|
* document new target genespie2018-11-051-3/+12
|
* - add an example to date(1) showing how to convert between timezonesjmc2018-10-171-3/+3
| | | | | | | | | - update the description of TZ in date(1) - mention some relevant info to avoid sending the reader to another page and, when they have to refer to another page, send them to tzset(3) rather than environ(7) - update the timezone name used in environ(7), as advised by millert ok millert
* zap extra Pp;jmc2018-10-171-3/+2
|
* document FETCH_PACKAGES as wellespie2018-10-161-5/+9
|
* update DESCRIPTION and COMPATIBILITY, mostly correcting statementsschwarze2018-10-041-19/+18
| | | | from the past that are no longer true
* Stop abusing subsections to represent the list of escape sequences;schwarze2018-10-041-97/+103
| | | | | | instead, use .Bl -tag like everywhere else. The same was already done for requests quite some time ago. Also, consistently mark up escape sequences with .Ic, just like requests.
* Make the HISTORY sections of the "intro" manuals less confusing andschwarze2018-09-301-3/+3
| | | | more uniform; potential for confusion noticed by aalm@; OK jmc@.
* Rudimentary implementation of the roff(7) .char (output glyphschwarze2018-08-251-5/+12
| | | | | | | | | definition) request, used for example by groff_hdtbl(7). This simplistic implementation may interact incorrectly with the .tr (input character translation) request. But come on, you are not only using .char *and* .tr, but you do so with respect to the same character in the same manual page?
* Rudimentary implementation of the roff(7) .while request.schwarze2018-08-241-9/+9
| | | | | | | | | | | Needed for example by groff_hdtbl(7). There are two limitations: It does not support nested .while requests yet, and each .while loop must start and end in the same scope. The roff_parseln() return codes are now more flexible and allow OR'ing options.
* Implement the roff(7) .shift and .return requests,schwarze2018-08-231-6/+9
| | | | | | | | | | | | | | for example used by groff_hdtbl(7) and groff_mom(7). Also correctly interpolate arguments during nested macro execution even after .shift and .return, implemented using a stack of argument arrays. Note that only read.c, but not roff.c can detect the end of a macro execution, and the existence of .shift implies that arguments cannot be interpolated up front, so unfortunately, this includes a partial revert of roff.c rev. 1.209, moving argument interpolation back into the function roff_res().
* Implement the \\$@ escape sequence (insert all macro arguments,schwarze2018-08-211-2/+7
| | | | | | | | | | | | quoted) in addition to the already supported \\$* (similar, but unquoted). Then use \\$@ to improve the implementation of the .als request (macro alias). Needed by groff_hdtbl(7). Gosh, it feels like the manual pages of the groff package are exercising every bloody roff(7) feature under the sun. In the manual page source code itself, not merely in the implementation of the used macro packages, that is.
* Fix some issues found looking at groff_char(7):schwarze2018-08-211-2/+4
| | | | | | * Add two missing characters, \('Y and \('y. * The Weierstrass p is not capital, see http://unicode.org/notes/tn27/. * Add a groff-compatible ASCII transliteration for U+02DC: "~".
* Mostly complete implementation of the 'c' (character available)schwarze2018-08-191-6/+19
| | | | | | | | | | | roff conditional, except that the .char request still isn't supported and that behaviour differs from groff in many edge cases. But at least valid character names and numbers are now distinguished from invalid ones. This also fixes the bug that parsing of the 'c' conditional was incomplete, which resulted in leaking the tested character to the input parser at the beginning of the body when the condition was inverted.
* support the highly surprising escape sequence \# (line continuationschwarze2018-08-181-2/+8
| | | | with comment); used for example by gropdf(1)
* Massively reduce the amount of text, cutting it down to what is neededschwarze2018-08-181-370/+73
| | | | | | | | | | | to understand existing man(7) code and deleting parts that would only be useful for writing new documents, which we strongly discourage: * Delete the MANUAL STRUCTURE section which merely duplicates mdoc(7). * Delete internal cross references only useful for writing new code. * Delete many instances of "included only for compatibility" as the whole language is only provided for compatibility. * Fix a few minor errors and omissions.
* implement the GNU man-ext .SY/.YS (synopsis block) macro in man,schwarze2018-08-181-3/+20
| | | | used in most manual pages of the groff package
* implement the GNU man-ext .TQ macro in man(7),schwarze2018-08-161-2/+8
| | | | used for example by groff_diff(7)
* Document \*(.T.schwarze2018-08-161-41/+24
| | | | | | | | While here, delete the section about predefined strings. For manual pages, the concept is not important enough to be discussed in such a prominent place, and some aspects of the text were also misleading. Add a shorter version of the relevant parts to the description of the \* escape sequence instead.
* Add /usr/include/c++ to hier.7.fcambus2018-08-151-2/+4
| | | | OK jmc@
* handle the non-portable GNU-style \[charNN], \[charNNN] characterschwarze2018-08-101-6/+8
| | | | escape sequences, used for example in the groff_char(7) manual page
* The groff man-ext macros define fonts CB, CI, and CR,schwarze2018-08-101-4/+4
| | | | | and some groff manual pages actually use them in .ft requests. It's easy enough to handle these .ft requests in mandoc, too.
* Implement the roff(7) .nop (no operation) request.schwarze2018-08-101-6/+9
| | | | | Examples of manual pages (ab)using it include groff(7), chem(1), groff_mom(7), and groff_hdtbl(7).
* Even though we strongly discourage escaping hyphens in manual pagesschwarze2018-08-081-2/+2
| | | | | in general, when introducing the *typographic* term "hyphen", actually display a real hyphen in output modes supporting it.
* Reorder the text in the "Dashes and Hyphens" subsection to keep theschwarze2018-08-081-25/+25
| | | | | | simplest and most important instructions together and at the beginning. No text change. Suggested by jmc@.
* Clarify the confusing "(text)" annotation in the character lists.schwarze2018-08-081-17/+18
| | | | | | | | | | In some cases, it meant "render as an ASCII character in output modes that have a notion of codepoints" (e.g. UTF-8, HTML); in other cases, "render in the text font in output modes that also provide a special font for mathematical symbols" (e.g. PostScript, PDF). Also explicitly annotate the escape sequences that use a special font if available. OK bentley@
* After years of deliberation, finally provide a clear recommendationschwarze2018-08-081-16/+21
| | | | | | | | for hyphens and minus signs in manual pages. Since there is consensus that a typographically perfect solution is impossible, let's KISS - just write "-", don't bother with "\-", all currently relevant manual page formatters can handle "-" reasonably. OK jmc@ bentley@
* 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.
* byebye network.conf.templateespie2018-07-161-5/+3
|
* .El should have been zapped too;jmc2018-07-141-2/+1
|
* zap network configuration section, it's a level of tinkering that'sespie2018-07-141-27/+10
| | | | | | not really supported. add another ref to PORTS_PRIVSEP here, as it is really a good idea.
* Remove the i386 specific mention for pcvtfonts, they are also installedfcambus2018-07-111-3/+3
| | | | | | | | on alpha and amd64. No objection from jmc@. OK deraadt@, sthen@
* check-problems -> pkg_check-problems;jmc2018-07-101-3/+3
|
* out-of-date -> pkg_outdated;jmc2018-07-091-3/+3
|
* resolve-lib -> port-resolve-lib-helper;jmc2018-07-091-5/+5
|
* Bytes only have eight bits, not nine.schwarze2018-05-171-3/+3
| | | | | Thus, remove the placeholder for the ninth bit. Patch from Ross L Richardson <openbsd at rlr dot id dot au>.
* Two new low-level roff(7) features:schwarze2018-04-101-5/+19
| | | | | | * .nr optional third argument (auto-increment step size) * \n+ and \n- numerical register auto-increment and -decrement bentley@ reported on Dec 9, 2013 that lang/sbcl(1) uses these.
* Stop documenting the non-portable .R man(7) macro. Neither groffschwarze2018-04-051-17/+4
| | | | | nor the heirloom-doctools support it. Adding it was a mistake in the first place.
* Soften the language discouraging special character escape sequences.schwarze2018-03-151-8/+22
| | | | | | | After i improved their ASCII renderings in groff and mandoc some time ago, mathematical symbols can now be used in specialised mathematical manual pages like libm and some X libraries. Tweaks and OK jmc@.
* Delete information about bulk builds already found in bulk(8).cheloha2017-12-281-43/+4
| | | | | | Direct the reader there instead. ok espie@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.