Erik Cederstrand

Ok. Thanks for the clarification. I'll probably have other priorities for now, but contributions are always welcome. Until someone goes about implementing this, you can still make a poor-man's filter...

It's not implemented yet, and I have no immediate plans to do so. Contributions are most welcome, of course.

A first step is to implement the [GetInboxRues](https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/getinboxrules-operation?redirectedfrom=MSDN) and [UpdateInboxRules](https://docs.microsoft.com/en-us/exchange/client-developer/web-service-reference/updateinboxrules-operation?redirectedfrom=MSDN) services. There are multiple examples in https://github.com/ecederstrand/exchangelib/tree/master/exchangelib/services that you can use as a template. While implementing these services, you'll need...

It's not something I'm planning to work on anytime soon. Contributions are welcome, of course :-)

This MR can be closed since the issue was solved in #86

I'm also hitting this. I think #77 fixes the issue cleanly by adding to `setup_requires` and creating a custom `build_ext` step (I think `cython` can be removed from `install_requires`, though)....

I'm not sure I like this. We're essentially lifting environment variables that should be applied in the subprocess into the parent process. If you want to resolve commands differently in...

It's not clear to me what you mean by "sh instance". When you import the `sh` package in your script, it will be the package installed in the package collection...

From the perspective of aligning with behavior in the shell, I agree that it's reasonable to take PATH into account when resolving the path to the executable: ```bash % PATH=/Users/erik/venv1/bin...

I quite like the `LazyCommand` approach because it could work regardless of whether we call `sh.python()` directly or via a wrapped `sh`. It also better matches what happens in the...