summaryrefslogtreecommitdiffstats
path: root/dbm_map.c
diff options
context:
space:
mode:
authorIngo Schwarze <schwarze@openbsd.org>2022-08-15 10:22:14 +0000
committerIngo Schwarze <schwarze@openbsd.org>2022-08-15 10:22:14 +0000
commitb8c2ddec80f36a42b137370c233bb4a858567168 (patch)
treec6363b9498575b5f80fdf26949bd5a61ca705f1b /dbm_map.c
parentd1209cefa23aa348425c687c38c5820947fd050c (diff)
downloadmandoc-b8c2ddec80f36a42b137370c233bb4a858567168.tar.gz
In GNU, Heirloom, and Plan 9 roff, literal tab characters are
non-breakable in exactly the same way as "\ ". That is, the preceding word, the tab character, and the following word are always kept together on the same output line. If filling is enabled and an output line break is required before the end of the following word, the break occurs before the beginning of the preceding word. Make mandoc behave in the same way. Of course, using literal tab characters in filled text remains a bad idea, and the "WARNING: tab in filled text" remains unchanged.
Diffstat (limited to 'dbm_map.c')
0 files changed, 0 insertions, 0 deletions