From 0b2e512d3648993ce24717d02be000862fc996c6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 14 Jun 2009 17:34:05 -0400 Subject: [PATCH] response --- doc/plugins/highlight/discussion.mdwn | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/doc/plugins/highlight/discussion.mdwn b/doc/plugins/highlight/discussion.mdwn index 612fb0fda..7d3cabea9 100644 --- a/doc/plugins/highlight/discussion.mdwn +++ b/doc/plugins/highlight/discussion.mdwn @@ -1,3 +1,12 @@ -It would be nice to be able to set a few options for the highlighter object. In particular, today I noticed my tabs were not being expanded correctly, which could -be fixed the command line with --replace-tabs but programmatically needs a call to setPreformatting. I could probably play with this, but what is your preferred way to support -options? something like 'highlight_options=>{replace_tabs=>8,line_numbers=>0}' ? Of course, if you want to implement it I won't complain :-). [[DavidBremner]] +It would be nice to be able to set a few options for the highlighter +object. In particular, today I noticed my tabs were not being expanded +correctly, which could be fixed the command line with --replace-tabs but +programmatically needs a call to setPreformatting. I could probably play +with this, but what is your preferred way to support options? something +like 'highlight_options=>{replace_tabs=>8,line_numbers=>0}' ? Of course, +if you want to implement it I won't complain :-). [[DavidBremner]] + +> I don't know about tab replacement, which I can't really see the point +> of, but if there are multiple options, giving each its own nane would +> word better for websetup than would putting all the options in a +> sub-hash. --[[Joey]]