[tor-bugs] #4971 [Tor Client]: Provide initvalue in GETINFO config/names

[Tor Bug Tracker & Wiki]

#4971: Provide initvalue in GETINFO config/names
-------------------------+--------------------------------------------------
 Reporter:  chiiph       |          Owner:                    
     Type:  enhancement  |         Status:  needs_revision    
 Priority:  normal       |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client   |        Version:                    
 Keywords:               |         Parent:                    
   Points:               |   Actualpoints:                    
-------------------------+--------------------------------------------------

Comment(by atagar):

 > Does anything else parse the output of GETINFO config/names?

 Yup, arm does.
 https://gitweb.torproject.org/arm.git/blob/HEAD:/src/cli/configPanel.py#l213
 https://gitweb.torproject.org/arm.git/blob/HEAD:/src/util/torConfig.py#l182
 https://gitweb.torproject.org/arm.git/blob/HEAD:/src/util/torConfig.py#l359
 https://gitweb.torproject.org/arm.git/blob/HEAD:/src/util/torInterpretor.py#l317

 I don't mind changing it, so please reassign this ticket to me after a tor
 patch is merged.

 > Does control-spec.txt specify its output format?

 Yes it does.
 https://gitweb.torproject.org/torspec.git/blob/HEAD:/control-spec.txt#l610

 I don't like the idea of the initial value being at the end since it would
 then make this...

 OptionName SP OptionType [ SP Documentation ][ SP InitialValue ] CRLF

 Multiple optional arguments, especially when the first is defined as
 'Text', means that controllers can't differentiate Documentation from the
 InitialValue. We could redefine the Documentation's Text type as not
 having quotes but from a parsing perspective... ewww.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4971#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online