[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13158 [Tor]: Did we ever document +/ semantics for config files?
#13158: Did we ever document +/ semantics for config files?
---------------------------+----------------------------
Reporter: Sebastian | Owner:
Type: defect | Status: new
Priority: normal | Milestone: Tor: 0.2.???
Component: Tor | Version:
Resolution: | Keywords: doc easy lorax
Actual Points: | Parent ID:
Points: | Sponsor:
---------------------------+----------------------------
Comment (by arma):
Saying "plus sign ("+")" would have solved the original issue for the
ticket. I had exactly this issue in the past too, and have learned to
search for "plus", but that doesn't scale to the third confused person. :)
An easy early fractional fix at least.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13158#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
- Prev by Author:
Re: [tor-bugs] #16325 [Stem]: Stem issues with bracketted IPv6 addresses in transport lines
- Next by Author:
[tor-bugs] #17195 [EFF-HTTPS Everywhere]: HTTPS Everywhere breaks the Vuze Blog
- Previous by thread:
Re: [tor-bugs] #13158 [Tor]: Did we ever document +/ semantics for config files?
- Next by thread:
[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #4580, #5460, #8106, #9476, #13966, #6773, #6836, #7193, #7478, #8195, #8625, #10186, #10812, #11151, #12898, #12900, #12901, #13987, #14137, #14999, #15233, #15235, #16943
- Index(es):