summaryrefslogtreecommitdiff
path: root/error.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2006-12-07 18:09:37 +0000
committerSimon Tatham <anakin@pobox.com>2006-12-07 18:09:37 +0000
commit92242aeaf21903a4c5a12a7c74eb77fcd7158a52 (patch)
tree4882b2abe106923ca2842300bf2d90c20922fa5a /error.c
parent10e38f34f5fc9710cca402b23cbf39d0fb79739a (diff)
downloadhalibut-92242aeaf21903a4c5a12a7c74eb77fcd7158a52.zip
halibut-92242aeaf21903a4c5a12a7c74eb77fcd7158a52.tar.gz
halibut-92242aeaf21903a4c5a12a7c74eb77fcd7158a52.tar.bz2
halibut-92242aeaf21903a4c5a12a7c74eb77fcd7158a52.tar.xz
I've just noticed some unacceptably long lines in code paragraphs in
the Halibut manual. They turn out to be \cfg directives with multiple braced sections after them. The obvious thing to do for legibility would be to wrap those sections by putting newlines between } and {, but that isn't legal in the Halibut syntax. Therefore, it is now :-) For paragraph types which don't have any body text (such as \cfg), we are now lenient about whitespace between multiple keywords. So I can fix the docs so they don't go over the limit, and be confident that the fixed version is still technically accurate. [originally from svn r6970]
Diffstat (limited to 'error.c')
0 files changed, 0 insertions, 0 deletions