Jerry Cheung

Thanks for opening this PR. It was helpful

After reading through the original issue (https://github.com/sstephenson/bats/issues/10#issuecomment-26627687), I decided to avoid using `run` altogether. It just sets the special variables `$output` and `$status`, both of which are easily available. Here's...

Read my mind, I would like this feature as well.

Can I programmatically close the original separate window then? The point is to only have the tabs I defined and no extra launch window or tab. On Jun 22, 2011,...

@digglife I'm not familiar with Bluepage, but would you be interested in submitting a pull request detailing your changes against the latest master? There are new maintainers on the project,...

@digglife :sparkles: great research! I think you're right that this would be fixed if paging wasn't enabled by default. https://github.com/ruby-ldap/ruby-net-ldap/issues/12 documents this as well. Would you be interesting in contributing...

I like the idea of non-blocking I/O, and I agree this PR is a good small step for us to move in that direction. I'm less interested in exposing public...

This was discussed previously in https://github.com/ruby-ldap/ruby-net-ldap/issues/127. At the time, I decided to not include the change, but I think we should make one of two decisions here: 1. Deprecate and...

I agree with not defaulting to paging. It's an extension to the LDAP spec, not a core requirement. It should not be assumed.

@satoryu thanks for triaging. I've opened https://github.com/ruby-ldap/ruby-net-ldap/pull/248 to prepare the next release.