halibut/bk_info.c, branch master My halibut tree Silence compiler warnings on OS X 10.9. 2014-03-30T07:48:03+00:00 Simon Tatham anakin@pobox.com 2014-03-30T07:48:03+00:00 18e0f32b292316a4db3bb0bde1570a73ee60b0bd [originally from svn r10166] 
[originally from svn r10166]
Add \s for 'strong' text, i.e. bold rather than italics. I've missed 2013-03-10T16:58:01+00:00 Simon Tatham anakin@pobox.com 2013-03-10T16:58:01+00:00 dcf080aa0e011de37a154e9e8a97dd7546a4a1b1 this a couple of times in Halibut markup recently (in particular, it's handy to have a typographical distinction between 'this term is emphasised because it's new' and 'this term is emphasised because I want you to pay attention to it'), so here's an implementation, basically parallel to \e. One slight oddity is that strong text in headings will not be distinguished in some output formats, since they already use bolded text for their headings. [originally from svn r9772] 
this a couple of times in Halibut markup recently (in particular, it's
handy to have a typographical distinction between 'this term is
emphasised because it's new' and 'this term is emphasised because I
want you to pay attention to it'), so here's an implementation,
basically parallel to \e.

One slight oddity is that strong text in headings will not be
distinguished in some output formats, since they already use bolded
text for their headings.

[originally from svn r9772]
Revamp of the Halibut error handling mechanism. 2012-08-29T18:13:11+00:00 Simon Tatham anakin@pobox.com 2012-08-29T18:13:11+00:00 1489dc15967970576d08f3f2b22c6e1c939bcbcf I'm not quite sure why I ever thought it was a good idea to have a central variadic error() function taking an integer error code followed by some list of arguments that depend on that code. It now seems obvious to me that it's a much more sensible idea to have a separate function per error, so that we can check at compile time that the arguments to each error call are of the right number and type! So I've done that instead. A side effect is that the errors are no longer formatted into a fixed-size buffer before going to stderr, so I can remove all the %.200s precautions in the format strings. [originally from svn r9639] 
I'm not quite sure why I ever thought it was a good idea to have a
central variadic error() function taking an integer error code
followed by some list of arguments that depend on that code. It now
seems obvious to me that it's a much more sensible idea to have a
separate function per error, so that we can check at compile time that
the arguments to each error call are of the right number and type! So
I've done that instead.

A side effect is that the errors are no longer formatted into a
fixed-size buffer before going to stderr, so I can remove all the
%.200s precautions in the format strings.

[originally from svn r9639]
List some documentation sources, and another todo item. 2007-04-08T20:47:01+00:00 Ben Harris bjh21@bjh21.me.uk 2007-04-08T20:47:01+00:00 50a6b098c6e75b8adbe9b5778378dbd22d371617 [originally from svn r7454] 
[originally from svn r7454]
Remove heading underlines from todo list. 2007-04-08T11:23:27+00:00 Ben Harris bjh21@bjh21.me.uk 2007-04-08T11:23:27+00:00 8623135e6ec54b40763f3dc26bc8fce5a1c07306 [originally from svn r7453] 
[originally from svn r7453]
Add support for doing different underlining of different heading levels 2007-04-08T11:16:23+00:00 Ben Harris bjh21@bjh21.me.uk 2007-04-08T11:16:23+00:00 9c83f06784539ca3a4dc6661542a11592e137f60 in the Info backend, with the defaults chosen to match what Emacs recognises and renders prettily. [originally from svn r7452] 
in the Info backend, with the defaults chosen to match what Emacs
recognises and renders prettily.

[originally from svn r7452]
Another observation about indices. 2007-04-08T00:44:13+00:00 Ben Harris bjh21@bjh21.me.uk 2007-04-08T00:44:13+00:00 71316e1f505d9ebe3b59ae9dc7b4e9cca007afba [originally from svn r7451] 
[originally from svn r7451]
A few thoughts I had while actually using Halibut's Info output. 2007-04-07T23:33:50+00:00 Ben Harris bjh21@bjh21.me.uk 2007-04-07T23:33:50+00:00 f1399b6857d72ebe3a82618226ba019dcc9ce789 [originally from svn r7449] 
[originally from svn r7449]
Introduce global (cross-backend) \cfg{contents} and \cfg{index} 2006-06-02T19:19:12+00:00 Simon Tatham anakin@pobox.com 2006-06-02T19:19:12+00:00 9e8ca006788e2148154711e1e67b88f495d94e26 commands, allowing the fixed words "Contents" and "Index" generated in various output formats to be reconfigured into other languages. [originally from svn r6724] 
commands, allowing the fixed words "Contents" and "Index" generated
in various output formats to be reconfigured into other languages.

[originally from svn r6724]
Ability to specify multiple arguments to \cfg{html-template-fragment}; 2005-03-08T01:55:34+00:00 Jacob Nevins jacobn@chiark.greenend.org.uk 2005-03-08T01:55:34+00:00 f3bcc430298edf9a72becfb14ee99e924e4ff2c0 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] 
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]