diff options
| author | Joey Hess <joey@kodama.kitenet.net> | 2008-03-15 13:58:08 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kodama.kitenet.net> | 2008-03-15 13:58:08 -0400 |
| commit | 5a7a89ffc59d008a6dd6586d26ff1a1fbb3bc51f (patch) | |
| tree | 9226e96dd5883da1024db7c7a2290e9a9f37ede7 /doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn | |
| parent | e7ce86db11174606d06a6cfabfa9c41aa3cbd50e (diff) | |
| download | ikiwiki-5a7a89ffc59d008a6dd6586d26ff1a1fbb3bc51f.tar ikiwiki-5a7a89ffc59d008a6dd6586d26ff1a1fbb3bc51f.tar.gz | |
* htmltidy: Pass --markup yes, in case tidy's config file disabled it.
Diffstat (limited to 'doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn')
| -rw-r--r-- | doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn b/doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn index d1eaffe55..ec02ddb89 100644 --- a/doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn +++ b/doc/bugs/htmltidy_has_no_possibilty_to_use_an_alternative_config_file_which_may_break_other_usages.mdwn @@ -17,3 +17,10 @@ I see two possibilities how to fix this: >> Hmmm, ok. Well, it didn't work. Empty pages, Perl Warnings. I moved my $HOME/.tidyrc away and it worked again. Had a short look into it and the only obvious non-default setting I found was write-back. I'll check what exactly caused the breakage and let you know. --[[XTaran]] >>> Ok, found it. It indeed wasn't `write-back`, but `markup: no`. (I usually only want to see warnings and errors, not the fixed markup.) I now've corrected this in the bug report above. --[[XTaran]] + +> Ok, so should I pass --markup yes, or should I force it not to use +> ~/.tidyrc? I can do that (by setting HOME to /dev/null), but there seems +> to be no way to override it reading /etc/tidy.conf, so options there can +> still screw things up. I guess I'll pass --markup yes and deal with +> overriding other problem settings from config files if they're found +> later. --[[Joey]] [[tag done]] |