Zulip client should detect the presence of a zuliprc in $PWD.

[rht]

Reading from ~/.zuliprc forces the number of account to be 1. The other alternative, i.e. having to type the API key in a command line is not secure (this leaves trails in the history). Additionally, having a local and global config has been practiced by npm for a while.

If this is to be implemented, another consideration is whether to make the zuliprc visible or not.

note: zulip-terminal has already implemented this local config detection. See also bridge_with_matrix.

[timabbott]

We already support just having users pass the path to a .zuliprc file, right?

[rht]

Huh, yeah, I could have used that instead of passing the API key, but again, it is more convenient if the client anticipates that .zuliprc is in the current directory. So the remaining argument is for convenience and that npm does it.

[orientor]

@zulipbot claim

[zulipbot]

Welcome to Zulip, @orientor! We just sent you an invite to collaborate on this repository at https://github.com/zulip/python-zulip-api/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

• Join me on the Zulip developers' server, to get help, chat about this issue, and meet the other developers.
• Unwatch this repository, so that you don't get 100 emails a day.

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

[orientor]

PR added. Please review. Also how should we change the docs in this case?

[zulipbot]

Hello @orientor, you have been unassigned from this issue because you have not updated this issue or any referenced pull requests for over 14 days.

You can reclaim this issue or claim any other issue by commenting @zulipbot claim on that issue.

Thanks for your contributions, and hope to see you again soon!