Port arm's tor config utils

added component::archived/stem controller owner::atagar priority::low resolution::implemented severity::normal status::closed type::enhancement labels

Related ticket: #7654 (closed)

I'm sorry, but why does a tor controller library need to read man page contents?

I'm sorry, but why does a tor controller library need to read man page contents?

To be able to provide a description of tor's config options. See arm's editor panel for an example.

Replying to atagar:

To be able to provide a description of tor's config options. See arm's editor panel for an example.

Sounds like an arm specific use case. I don't understand where anyone would want a "controller" library to parse the man page.

Sounds like an arm specific use case. I don't understand where anyone would want a "controller" library to parse the man page.

You're focusing too much on how it works rather than what it does. 'Give me a human readable description of config option X' is a nice feature to have. And no, this isn't arm specific. Vidalia and other GUI controllers, for instance, would love to have this feature.

Replying to atagar:

Sounds like an arm specific use case. I don't understand where anyone would want a "controller" library to parse the man page.

You're focusing too much on how it works rather than what it does. 'Give me a human readable description of config option X' is a nice feature to have. And no, this isn't arm specific. Vidalia and other GUI controllers, for instance, would love to have this feature.

Exactly, the GUI's should implement this if they need it not stem. It just sounded like feature creep. Anyhow, it's your call :)

This is now implemented!

https://gitweb.torproject.org/stem.git/commit/?id=180d59c6a7fb75b49d64775ad92f0c0af9d30686

Trac:
Severity: N/A to Normal
Sponsor: N/A to N/A
Status: new to closed
Resolution: N/A to implemented

closed

Port arm's tor config utils

Child items 0

Activity