summaryrefslogtreecommitdiff
path: root/halibut.h
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 /halibut.h
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 'halibut.h')
-rw-r--r--halibut.h1
1 files changed, 0 insertions, 1 deletions
diff --git a/halibut.h b/halibut.h
index 99b9a0e..ed2a0da 100644
--- a/halibut.h
+++ b/halibut.h
@@ -244,7 +244,6 @@ enum {
err_text_codeline, /* \c line too long in text backend */
err_htmlver, /* unrecognised HTML version keyword */
err_charset, /* unrecognised character set name */
- err_emptypara, /* paragraph contains no actual text */
err_whatever /* random error of another type */
};