dmgr

Results 12 comments of dmgr

The usecase is similar to `default:` option behavior: https://github.com/cgriego/active_attr/blob/55406079d70171df8bccfeb9b4eb2e98a02f58ab/lib/active_attr/attribute_defaults.rb#L114 By the way, the: ```rb when default.respond_to?(:call) then instance_exec(&default) ``` should be ```rb when default.is_a?(Proc) then instance_exec(&default) ``` in my opinion...

It would be nice if there were an option to set a background color of your choice. Then you would be able to show a weather on a black background...

OK, currently I use workaround: ```ruby variant = nil OptionParser.new do |opts| opts.on("--variant=CODE") do |v| variant = v end end.parse ``` Then I have a `variant` and I can load...

Actually I think `on_transition` callback is quite useful, but limited due to its lack of recognition of `from` and `to` states. It can be a lot more useful if it...

Might be worth looking at the logic implemented in a Syncthing scanning feature: > There are two methods how Syncthing detects changes: By regular full scans and by notifications received...

This issue should have not been closed, TTTPOB... My comment above is not a solution, but an inspiration.

Just a simple "black & white" and "white & black" color schemes would be nice as a low hanging fruit for a strart.

I would like to see that syntax possible: ```ruby operation = Math.sin 2.then(operation) ``` instead of the current approach: ```ruby operation = Math.method(:sin) 2.then(&operation) ``` which will encourage community to...

I would like to see Crystal as a better Ruby. As Crystal is Ruby inspired language, it can deviate from it. So I would like Crystal has first-class functions also...

It is not "explicitness of Ruby (and Crystal)". You can rather say otherwise: it is the explicitness of functional languages that they require you to explicitly use parenthesis if you...