summaryrefslogtreecommitdiffstats
path: root/lib/libc/sys/stack_protector.c
diff options
context:
space:
mode:
authorschwarze <schwarze@openbsd.org>2013-12-26 17:23:31 +0000
committerschwarze <schwarze@openbsd.org>2013-12-26 17:23:31 +0000
commit6bef2f02e736f6ad83d7e731a1a2d74060e99984 (patch)
tree1e9377091ed949b3aeae73102168dcd6750160c7 /lib/libc/sys/stack_protector.c
parentspacing (diff)
downloadwireguard-openbsd-6bef2f02e736f6ad83d7e731a1a2d74060e99984.tar.xz
wireguard-openbsd-6bef2f02e736f6ad83d7e731a1a2d74060e99984.zip
Rework the documentation of Spaces, using the Ossanna/Kernighan/Ritter
Heirloom Nroff/Troff User's Manual at the authoritative reference. Part of our text was outright wrong. Also, refrain from advertising the paddable non-breaking space `\~' in the DESCRIPTION, for three reasons: For nroff mode, -Tascii, and fixed width fonts in general, it makes no difference, so keep the discussion simple. Compared to `\ ', '\~' is of questionable portability. And if you want to keep words together, it is also more usual that you don't want padding to intervene either. Finally, drop the `\c' escape sequence (interrupt text processing) which is not a special character but an input processing instruction akin to the \<newline> escape sequence.
Diffstat (limited to 'lib/libc/sys/stack_protector.c')
0 files changed, 0 insertions, 0 deletions