ytti

``` irb(main):001:0> "moi".sub /#{"(\x82.*\xB8)".b}/, '' => "moi" ``` Bit less ugly version ``` irb(main):001> re = Regexp.new "(\x82.*\xB8)".b => /(\x82.*\xB8)/ irb(main):002> "moi".match re => nil ``` The problem is that...

```cmd``` does take parameters, I'm thinking we configure >1 input methods in model and then in the config block we give them execution order. If execution order is unset it...

Personally I dont think static unchanging error line on config which you can load to device, because error is comment isnt broken. I’m not against fixing it, but I’m not...

I had toyed around with this in https://github.com/ytti/oxidized/compare/master...filename - it has bit more flexibility into how to name the file, but no fetch method. The fecth method is tricky with...

> You are right. I'm thinking how handle the fetch method properly.. but I don't understand very well how I aim for it. My idea is to implement the same...

I am bit on the fence, why this is the right approached compared to my approach, which affects all outputs. Why wouldn't there be anyone who would want to emit...

Yeah I'm not sure #fetch is going to be reliable anyhow. I'm also skeptical if you can flatten the opts safely. And I don't think your version supports passing directory...

On top of my branch changes, I was thinking maybe 'fetch' can work, because we store the name. So we don't have to try to infer it? Like so: ```diff...

I'm not really sure I agree it should be another output model. I agree we have some icky problems, but I don't see how another output class solves any of...

12. we should support routers pushing config to us, http, ftp, tftp.. listener thread, with worker fetching configs from listener threads via Queue 13. API should be changed to Swagger...