Docs: remove 'noconnect' option #10085
Conversation
|
-no* is the same as -*=0 |
|
@luke-jr can you point out where the logic is that translates a "no*" parameter into a "*=0" parameter? |
|
… On Sun, Mar 26, 2017 at 7:38 PM, Jameson Lopp ***@***.***> wrote:
@luke-jr <https://github.com/luke-jr> can you point out where the logic
is that translates a "no*" parameter into a "*=0" parameter?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10085 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AGGmvzH6lDVKoYxIbrA6xW3hdV-B9Chdks5rpqKNgaJpZM4MpbHR>
.
|
|
Aha; thanks for the clarification. |
|
@jlopp If it wasn't clear that -noX is an alias for -X=0, perhaps that should be documented more clearly in the |
|
@sipa Yes, possibly - I'll think about it. I'm currently working on a project involving Bitcoin Core's configuration options, which is why I'm currently exploring this area of the codebase. |
|
@jlopp, regardless, I agree with @MarcoFalke that this PR probably improves things, despite not fixing anything technically incorrect. I suggest reopening. |
|
Sure, done. |
|
|
d5690f1 remove 'noconnect' option from documentation (Jameson Lopp) Tree-SHA512: 9c61df5ee7b2b9a8188cbf44fced05c41ded3454758dbc1b1ae641cea0301a65169381f20c045027e571ebe211a42e680a66daed47090f91766403cc60147e89
d5690f1 remove 'noconnect' option from documentation (Jameson Lopp) Tree-SHA512: 9c61df5ee7b2b9a8188cbf44fced05c41ded3454758dbc1b1ae641cea0301a65169381f20c045027e571ebe211a42e680a66daed47090f91766403cc60147e89
6 participants
As far as I can tell, "noconnect" is never actually parsed as an argument in the codebase.