[tor-bugs] #28300 [Core Tor/Stem]: Scrolling support for tor-prompt is needed

[Tor Bug Tracker & Wiki]

#28300: Scrolling support for tor-prompt is needed
---------------------------+------------------------------
 Reporter:  wagon          |          Owner:  atagar
     Type:  enhancement    |         Status:  closed
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:  Tor: 0.3.4.8
 Severity:  Normal         |     Resolution:  wontfix
 Keywords:  tor-prompt     |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+------------------------------

Comment (by wagon):

 > Please file a ticket with the 'Core Tor / Tor' component for this one.
 Done: [[https://trac.torproject.org/projects/tor/ticket/28358|#28358]].

 > For more information on all the commands see
 ​https://gitweb.torproject.org/torspec.git/tree/control-spec.txt
 OK, then it's core Tor's bug:

   The OptionPrefix form indicates a number of options beginning with the
 prefix. So if "config/*" is listed, other options beginning with "config/"
 will work, but "config/*" itself is not an option.

 If the format "Option/*" is used to name a group of options (each of them
 is still described separately), it must be done for everything. However,
 e.g., we have many options inside "accounting", but key "accounting/*" is
 not present:

 {{{
 accounting/bytes          - Number of bytes read/written so far in the
 accounting interval.
 accounting/bytes-left     - Number of bytes left to write/read so far in
 the accounting interval.
 accounting/enabled        - Is accounting currently enabled?
 accounting/hibernating    - Are we hibernating or awake?
 accounting/interval-end   - Time when the accounting period ends.
 accounting/interval-start - Time when the accounting period starts.
 accounting/interval-wake  - Time to wake up in this accounting period.
 }}}

 Compare it with:

 {{{
 config/*                  - Current configuration values.
 config/defaults           - List of default values for configuration
 options. See also config/names
 config/names              - List of configuration options, types, and
 documentation.
 }}}

 If grouping syntax is used, it should be used everywhere (for all groups)
 or nowhere. Otherwise, it is confusing, because for many other options
 syntax "option/*" implies that something not listed here (in list of
 options) should be substituted (e.g. fingerprint of a relay, IP address,
 etc.).

 > Nyx gets the published attribute from the consensus ('GETINFO
 ns/id/<fingerprint>' or 'GETINFO ns/name/<nickname>')
 Thank you, I found it. I was selectively blind because I though it should
 printed at separate line in the output. :)

 Could you reply also on my question about tor versions?
 > Inverse situation is with Tor version: it is shown in `/var/lib/tor
 /cached-microdesc-consensus` but Nyx does not show it in information about
 relays (connections window). Can relay's Tor version be learned from
 `ControlPort` too?

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