summaryrefslogtreecommitdiff
path: root/inputs/test.but
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2005-09-29 13:04:26 +0000
committerSimon Tatham <anakin@pobox.com>2005-09-29 13:04:26 +0000
commit4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f (patch)
treebd35d0b7ede0517d9e223ddcaf66b0984ba684fa /inputs/test.but
parente1a1d840b82db8a3b93e112e94e55f761c2b6dba (diff)
downloadhalibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.zip
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.gz
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.bz2
halibut-4a4d009cbba73b06e8b16fdf8f8f59e712a4bc6f.tar.xz
Remove the error message `no text found in paragraph'. Aaron Brown
points out that it's perfectly possible to generate an empty paragraph using legal Halibut syntax: a paragraph containing nothing but a \#{...} comment will do the job, and is quite likely to happen if you've commented out a load of Halibut code. Therefore, an empty paragraph is now silently ignored rather than being an error condition in itself; if you create an empty paragraph due to it containing an unrecognised directive, then you'll get an error for _that_ and only that. [originally from svn r6361]
Diffstat (limited to 'inputs/test.but')
-rw-r--r--inputs/test.but2
1 files changed, 2 insertions, 0 deletions
diff --git a/inputs/test.but b/inputs/test.but
index 4682d5f..2088de4 100644
--- a/inputs/test.but
+++ b/inputs/test.but
@@ -43,6 +43,8 @@ has line\#{yet another one} breaks in between words, multiple
spaces (ignored), and \e{emphasised text} as well as \c{code
fragments}.
+\#{This is an inline comment alone in a paragraph.}
+
\cw{This} is weak code; \cq{this} is quoted code. And \k{head}
contains some other stuff. \K{subhead} does too.