summaryrefslogtreecommitdiff
path: root/doc/forum/parsing_a_config_file
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/parsing_a_config_file')
-rw-r--r--doc/forum/parsing_a_config_file/comment_1_8e97fb2e39c1a91bcab75e57ddc8b519._comment12
-rw-r--r--doc/forum/parsing_a_config_file/comment_2_9b364647b1da4c8db0116115e5c67b18._comment13
2 files changed, 25 insertions, 0 deletions
diff --git a/doc/forum/parsing_a_config_file/comment_1_8e97fb2e39c1a91bcab75e57ddc8b519._comment b/doc/forum/parsing_a_config_file/comment_1_8e97fb2e39c1a91bcab75e57ddc8b519._comment
new file mode 100644
index 00000000..fa9d74ff
--- /dev/null
+++ b/doc/forum/parsing_a_config_file/comment_1_8e97fb2e39c1a91bcab75e57ddc8b519._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-08-03T19:14:00Z"
+ content="""
+This probably needs a smarter parser for torrc files that understands
+the method that tor uses to decide which config lines go together.
+
+Or, perhaps, a way to add additional torrc files that are included into the
+main one or that tor is otherwise configured to use, which would avoid the
+parsing complexity.
+"""]]
diff --git a/doc/forum/parsing_a_config_file/comment_2_9b364647b1da4c8db0116115e5c67b18._comment b/doc/forum/parsing_a_config_file/comment_2_9b364647b1da4c8db0116115e5c67b18._comment
new file mode 100644
index 00000000..4ceec2f4
--- /dev/null
+++ b/doc/forum/parsing_a_config_file/comment_2_9b364647b1da4c8db0116115e5c67b18._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2015-08-20T14:43:02Z"
+ content="""
+Sean and I have implemented a somewhat generic support for files with some
+kinds of sections, in Propellor.Property.ConfFile.
+
+I think it could be used for this tor case, by making the SectionStart
+match the HiddenServiceDir line, and the SectionPast match any line that's
+not HiddenServicePort (or perhaps match the next HiddenServiceDir
+line?)
+"""]]