summaryrefslogtreecommitdiffstatshomepage
path: root/term.c
diff options
context:
space:
mode:
authorKristaps Dzonsons <kristaps@bsd.lv>2009-07-19 21:26:27 +0000
committerKristaps Dzonsons <kristaps@bsd.lv>2009-07-19 21:26:27 +0000
commit9954ffcf73634d2ae338d61164daa96a0e60235b (patch)
treedc34b7581dc3ef70c32d9dff80eb100d282b8055 /term.c
parent83b4aa04039660d0f4e9d18e868999f54dc74589 (diff)
downloadmandoc-9954ffcf73634d2ae338d61164daa96a0e60235b.tar.gz
mandoc-9954ffcf73634d2ae338d61164daa96a0e60235b.tar.zst
mandoc-9954ffcf73634d2ae338d61164daa96a0e60235b.zip
Fixed and cleaned up "phrase" handling (`Bl -column' columns).
Found strange newline bug in -diag handling (and others?).
Diffstat (limited to 'term.c')
-rw-r--r--term.c7
1 files changed, 5 insertions, 2 deletions
diff --git a/term.c b/term.c
index 908c5854..4d33ce8d 100644
--- a/term.c
+++ b/term.c
@@ -1,4 +1,4 @@
-/* $Id: term.c,v 1.89 2009/07/16 13:17:51 kristaps Exp $ */
+/* $Id: term.c,v 1.90 2009/07/19 21:26:27 kristaps Exp $ */
/*
* Copyright (c) 2008, 2009 Kristaps Dzonsons <kristaps@kth.se>
*
@@ -204,7 +204,10 @@ term_isopendelim(const char *p)
* possible).
*
* FIXME: newline breaks occur (in groff) also occur when a single
- * space follows a NOBREAK!
+ * space follows a NOBREAK (try `Bl -tag')
+ *
+ * FIXME: there's a newline error where a `Bl -diag' will have a
+ * trailing newline if the line is exactly 73 chars long.
*/
void
term_flushln(struct termp *p)