From 3e8f3a2b1feb102505ada7bbcb6c7e9820e62ce3 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 12 Oct 2014 23:26:27 +0000 Subject: Added a comment --- .../comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment diff --git a/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment new file mode 100644 index 000000000..375ee1254 --- /dev/null +++ b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 3" + date="2014-10-12T23:26:27Z" + content=""" +vicfg won't accept invalid input, if you make a type in the syntax it'll land you back in the editor with the problem line marked. + +But right, commenting out a line does not reset it to the default. Basically, once one of these settings is changed, there is no longer a default to go back to. You have to leave the line uncommented and change the value to what you want it to be. Ie, \"= semitrusted\" for the trust levels, and \"= \" for the wanted expressions. + +I think that vicfg should avoid this [[todo/vicfg_comment_gotcha]] and have filed that as a todo item. +"""]] -- cgit v1.2.3