summaryrefslogtreecommitdiffstats
path: root/share/man/man7 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* correct paper titlejsg2021-03-081-3/+3
|
* Delete a sentence pointing to "the Predefined Strings subsectionschwarze2020-10-311-7/+2
| | | | | | of the roff(7) manual." Such a subsection does not exist, and i do not see why it should. Predefined strings are an obsolete feature of macro packages, not a feature of the roff language.
* Correct an embarrassing spelling mistake:schwarze2020-10-281-3/+3
| | | | The last name of the author of groff is "Clark".
* Improve the HISTORY and AUTHORS sections, using informationschwarze2020-10-281-12/+23
| | | | | received from Douglas McIlroy in private mail: https://manpages.bsd.lv/history/mcilroy_26_10_2020.txt
* add missing mention of Werner Lemberg,schwarze2020-10-141-4/+9
| | | | | noticed by Werner himself on <groff at gnu dot org>; while here, add missing .An macros
* Fix a bunch of typos in various man pages.fcambus2020-08-272-6/+6
|
* some more information about invalid codepoints, bytes, and byte pairs;schwarze2020-07-301-2/+36
| | | | OK stsp@
* 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@
* document FETCH_PACKAGES betterespie2020-04-281-4/+16
| | | | feedback and okay schwarze@
* ce examples of "Ar arg Ar arg" with "Ar arg arg" and stop the spread;jmc2020-04-231-3/+3
|
* Add support for "alpha" suffixes in package versionsjca2020-03-261-3/+8
| | | | | | | | | | | | | We already supported "beta" releases but not "alpha", probably to discourage people from pushing "alpha-quality" software in the ports tree. We have 30 ports with distfiles matching "alpha", and people just work around the lack of explicit support for "alpha" releases with mixes of crafted PKGNAME and REVISION/EPOCH. This looks needlessly complicated and a bit unfair when compared to GH_COMMIT support. Pointers from landry@ and sthen@, lgtm landry@, no objection from espie@
* Clarify the use of EPOCH in ports Makefiles.paco2020-03-261-5/+10
| | | | | | Whith lots of help from sthen@, espie@ and jca@ ok espie@ jca@
* Mention that .AT, .P, .SB, and .UC are extensions; it really mattersschwarze2020-02-181-5/+16
| | | | | | | | | | | | | because we only retain the language for backward compatibility in the first place. Part of the research done by <G dot Branden dot Robinson at gmail dot com>, see the list <groff at gnu dot org> for details. No change to the following conventions: Consider portable whatever made it into GNU troff no later than 4.4BSD. For portable extensions, mention their origin at the end of the description. For non-portable extensions, for example from man-ext, usually warn earlier, near the beginning of the description.
* 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.
* Digit-width and narrow spaces are non-breaking.schwarze2020-02-131-8/+8
| | | | Noticed because Branden Robinson worked on related documentation in groff.
* environ(5) was in v7jsg2020-02-091-4/+4
| | | | ok schwarze@
* mention cbor fido llvm and llvm-c top level include directoriesjsg2020-02-061-2/+11
|
* /usr/local/sbin was added in at least 2014 to login.conf's 'path' entry in theokan2020-01-231-3/+4
| | | | | | 'default' class; also added to _PATH_DEFPATH in 2019. Update PATH accordingly. OK millert@
* 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@.
* Usually, -width Fl (which is 10n) is too wide and hence ugly.schwarze2020-01-161-6/+6
| | | | Change several instances, most of them to the usual -width Ds.
* Document the "delim" syntax and its usage.schwarze2020-01-101-24/+31
| | | | | | | Closing a gap reported by bentley@, who also sent a patch, but i'm explaining it somewhat differently. While here, remove duplicate information from the text. OK bentley@
* document special names that exist in the package systemespie2019-12-041-2/+19
|
* add STANDARDS section;schwarze2019-09-211-2/+9
| | | | | | similar to a diff sent in by <Masanori dot Ogino at gmail dot com>, but using the up-to-date reference rather than one from 30 years ago; OK jmc@
* sysctl(2): add kern.utc_offset: successor to the DST/TIMEZONE options(4)cheloha2019-08-211-2/+3
| | | | | | | | | | | | | | | | | | | | | The DST and TIMEZONE options(4) are incompatible with KARL, so we need some other way to compensate for an RTC running with a known offset. Enter kern.utc_offset, an offset in minutes East of UTC. TIMEZONE has always been minutes West, but this is inconsistent with how everyone else talks about timezones, hence the flip. TIMEZONE has the advantage of being compiled into the binary. Our new sysctl(2) has no such luck, so it needs to be set as early as possible in boot, from sysctl.conf(5), so we can correct the kernel clock from the RTC's local time to UTC before daemons like ntpd(8) and cron(8) start. To encourage this, kern.utc_offset is made immutable after the securelevel(7) is raised to 1. Prompted by yasuoka@. Discussed with deraadt@, kettenis@, yasuoka@. Additional testing by yasuoka@. ok deraadt@, yasuoka@
* No specific called "exec(3)", so move primary manpage to a name whichderaadt2019-08-111-7/+4
| | | | | | | | does exist -- execv(3). Still call this a family but without "Nm". Adjust Xr in various pages to refer to the precise function used rather than the family, in most cases the semantics of execve(2) are being referenced, so change the Xr. ok jmc
* remove groff leftover. from micah muertb2019-08-101-4/+2
|
* explain escaping of end-of-sentence characters;schwarze2019-07-152-4/+17
| | | | missing info reported by Ian <ropers at gmail dot com> on misc@
* The non-standard .EX/.EE macro pair was invented for Version 9 AT&T UNIXschwarze2019-07-091-6/+10
| | | | | | and only got adopted by GNU two decades later. Thanks to Doug McIlroy <doug at cs dot dartmouth dot edu> for pointing out the error.
* use the standard spelling of the word "idiosyncrasy";schwarze2019-07-011-3/+3
| | | | suggested by Michal Nowak <mnowak at startmail dot com>
* Don't try to fake a horizontal rule with a bunch of hyphens.bentley2019-06-211-3/+2
| | | | ok jmc@ schwarze@
* finish killing PLIST_DB as noticed by some anonymous guyespie2019-06-161-3/+3
|
* php5 -> php, php5 has left the ports tree.jca2019-05-301-3/+3
| | | | from Jesper Wallin
* Delete documentation of the former HOSTALIASES featuresschwarze2019-05-121-15/+2
| | | | | | | which was removed in libc/asr/asr.c rev. 1.50 in 2015. Smaller version of a patch posted by Hiltjo Posthuma <hiltjo at codemadness dot org>. No objection was raised when shown on tech@.
* socppc makes an extended visit to the bigbucket.deraadt2019-05-111-3/+2
| | | | ok kettenis
* sysupgrade(8) uses /home/_sysupgradeflorian2019-04-261-2/+8
| | | | suggested by deraadt; OK jmc
* 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>
* add some missing "pp." to .%P macros;schwarze2019-04-231-3/+3
| | | | Fabio Scotoni <fabio at esse dot ch> reported it was missing in eqn(7)
* Implement the roff .break request (break out of a .while loop).schwarze2019-04-211-4/+3
| | | | | | | Jan Stary <hans at stare dot cz> found it in an ancient groffer(1) manual page (version 1.19) on MacOS X Mojave. Having .break not implemented wasn't a particularly bright idea because obviously, it tended to cause infinite loops.
* While we do encourage simplicity in the sense of writing plain '-'schwarze2019-03-311-4/+4
| | | | | | | | for hyphen-minus, soften the language a bit: writing \- for it is not wrong, and people started sending us patches to replace \- with '-' in existing manual pages, which is not a worthwhile change unless the \- is used at a place where it doesn't belong. OK jmc@
* fix some cases of spaces before full stops, where none were neccessary;jmc2019-03-101-3/+3
|
* Do not open a subsection for each and every macro.schwarze2019-03-021-178/+165
| | | | | | Instead, use a tagged list and the canonical .Ic macro as it is natural for such purposes. While here, also delete heaps of needless escaping.
* remove a few words to improve flow. ok schwarzetedu2019-02-111-4/+4
|
* add a BUGS section explaining the situation with box and line drawingschwarze2019-02-091-3/+17
| | | | in UTF-8 output; suggested by bentley@
* Fix typo: "a data cells" -> "a data cell".bentley2019-02-081-3/+3
| | | | ok schwarze@
* .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>.
* I am retiring my old email address; replace it with my OpenBSD one.millert2019-01-251-3/+3
|
* Now that .nf and .fi are implemented in the roff(7) parser and formattersschwarze2019-01-012-35/+47
| | | | | | | rather than in the man(7) parser and formatters, document them in the roff(7) manual, where they belong, rather than in the man(7) manual. Mention that they imply an output line break, and mention which macros imply these requests.