diff options
author | http://joeyh.name/ <http://joeyh.name/@web> | 2014-10-12 23:26:27 +0000 |
---|---|---|
committer | admin <admin@branchable.com> | 2014-10-12 23:26:27 +0000 |
commit | 91894b405df3f637e5307482e93251b92fe6ea0d (patch) | |
tree | e56d24af8e93a69ebc89ceaf5959cb5d502005c6 | |
parent | e6d3ffb9417f5a646ebd4f84db34726b0e3aae9d (diff) |
Added a comment
-rw-r--r-- | doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_3_9da6ca0250ab0dcfc9a012df75e2e711._comment | 12 |
1 files changed, 12 insertions, 0 deletions
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 0000000000..375ee1254b --- /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. +"""]] |