[tor-bugs] #22374 [Core Tor/Stem]: tor-prompt should handle /events even after tor has died

[Tor Bug Tracker & Wiki]

#22374: tor-prompt should handle /events even after tor has died
---------------------------+-----------------------------
 Reporter:  teor           |          Owner:  atagar
     Type:  defect         |         Status:  closed
 Priority:  Medium         |      Milestone:
Component:  Core Tor/Stem  |        Version:
 Severity:  Normal         |     Resolution:  implemented
 Keywords:                 |  Actual Points:
Parent ID:                 |         Points:
 Reviewer:                 |        Sponsor:
---------------------------+-----------------------------
Changes (by atagar):

 * status:  new => closed
 * resolution:   => implemented


Comment:

 Great idea, thanks for suggesting this teor!
 [https://gitweb.torproject.org/stem.git/commit/?id=f62fc95876fa2c817b7e1aa2a57fe6bd93ef7a78
 Made this so].

 The interpreter no longer quits when the control connection is closed.
 Instead, it shows a one-time prompt if you issue a **tor command**
 afterward (other inputs like /events work normally). In the following I
 ctrl+c after calling SETEVENTS...

 [[Image(https://www.atagar.com/transfer/stem/interpreter_shutdown_prompt.png)]]

 On a side note when you snagged those events for me there's a new
 interpreter feature you might've found handy. Rather than calling
 'SETEVENTS' followed by '/events' you could've just run **tor-prompt --run
 "SETEVENTS AUTHDIR_NEWDESC"**. This would print those events to stdout
 until you ctrl+c...

 https://stem.torproject.org/tutorials/down_the_rabbit_hole.html#running-
 individual-commands

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