From f3bcc430298edf9a72becfb14ee99e924e4ff2c0 Mon Sep 17 00:00:00 2001 From: Jacob Nevins Date: Tue, 8 Mar 2005 01:55:34 +0000 Subject: Ability to specify multiple arguments to \cfg{html-template-fragment}; Halibut will output fragment names in all specified formats. (I forget now precisely why I thought this was necessary, but it seems potentially useful.) Also ensure that legal fragment names are generated even if none of the characters from the original turn out to be legal (e.g., %k with an entirely numeric keyword), and correct an untruth I inserted in the documentation of this. (This commit hits more than just the HTML backend as I've generalised an error message, and fixed a fault in the info backend's error handling while there.) [originally from svn r5457] --- error.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'error.c') diff --git a/error.c b/error.c index 0011b18..3635f0f 100644 --- a/error.c +++ b/error.c @@ -239,10 +239,12 @@ static void do_error(int code, va_list ap) { sp); flags = FILEPOS; break; - case err_infodirentry: + case err_cfginsufarg: fpos = *va_arg(ap, filepos *); - sprintf(error, "\\cfg{info-dir-entry} expects at least three" - " parameters"); + sp = va_arg(ap, char *); + i = va_arg(ap, int); + sprintf(error, "\\cfg{%s} expects at least %d parameter%s", sp, + i, (i==1)?"":"s"); flags = FILEPOS; break; case err_infonodechar: -- cgit v1.1