MSP-Greg

Thanks for closing the capybara PR and the additional changes. We can squash commits when merging a PR. Once a PR hit's 'last minute changes/discussion/suggested changes', if you do a...

@chjasonwu First of all, I haven't had time to review this PR. But, the current Puma test suite may have intermittent failures, I'll re-run the failing tests.

@thomthom Try (note the '@'): ```ruby # @!group ExampleGroup # @!endgroup ExampleGroup ``` I don't recall groups ever affecting constants, just methods and attributes. Also, they are only grouped in...

@thomthom I just did a quick check of things, and only used groups in the `rb_*` section of methods. The following patch seemed to correct things. ```patch diff --git a/lib/yard/handlers/c/handler_methods.rb...

Have you seen: https://ruby.sketchup.com/file.exporter_options.html#label-Industry+Foundation+Classes+-28IFC-29 -or- https://msp-greg.github.io/su/file.exporter_options.html#industry-foundation-classes-ifc-

The general concept here has been brought up before. I don't think implementing it should include any 'rule based' logic. Maybe the app provides a block to Puma, Puma passed...

I need to start paying more attention to bundler. That's similar to what I've been thinking, but I'd like to see a specific flag to enable checking/updating default gems. Maybe...

@duckinator, my vote is ``` gem update GEMNAME gem update --all --defaults gem update --all --no-defaults gem update --all # defaults to --no-defaults. ``` To clarify: `gem update --defaults` does...

Working a bit with `gem update` with the update for the `required_rubygems_version` constraints. Below is output. Note that the correct 'did_you_mean' is selected. 1. So, about these new options like...

Ok, I dropped the ball. It seems this has two issues. 1. Should an option like `--all` be added so `gem update` won't do so? 2. Considering the above, should...