Alexey Zapparov

There are `--wrapper-open` and `--wrapper-close` params, which, I believe, should be respected in this case (they are not ATM).

IMHO it should be a plugin. And, it needs some options (how it will generate IDs). I propose to support 3 variants of IDs generation. Assume we have markdown text:...

was struggling same issue today. And here's what I have figured out: - `hist --replay X..Y` works with what you can see with `hist` command in other words current REPL...

Here's how it looks on my end: ``` [1] pry(main)> puts "tada" tada => nil [2] pry(main)> hist 1: puts "tada" [3] pry(main)> hist --replay 1 tada => nil [5]...

Probably it worth to "explain" that in readme/wiki somehow. :D

gruvbox was added btw :D

@feliperaul can you point me out where *Sidekiq guarantees that jobs are going to be fetched in order*? Because if it is so - we need to think on how...

It's hard for me to tell or debug what's wrong when commercial sidekiq (sidekiq-pro or sidekiq-enterprise) is enabled. `sidekiq-throttled` implements throttling via having its own fetcher, and if you use...

@csalvato compatibility depends on whenever you're using custom fetcher, and it's not limited by pro/enterprise. Gem heavily depends on using its own fetcher, yes.

Hi. You're right, current version rotates the queue. Throttling happens on per-worker class, not queue. There's no way to overcome this right now. But I have this on my list...