Anton Astashov
Anton Astashov
Yeah, `g:ruby_debugger_debug_mode` https://github.com/astashov/vim-ruby-debugger/blob/master/doc/ruby_debugger.txt#L173
Yup, commands 'edit', 'frame', 'where'/'backtrace' and 'jump' fail with Segfaults.
The problem is inside context_frame_file(), no idea how to fix it though. :(
debugger-xml should not affect any debugger's behavior, it is just a different formatter for the 'debugger' gem. :) I'll have a look though. Would be nice to have some short...
The feature kinda makes sense, but I'll have postpone it for now, to avoid complicating the transitioning to the new editor, sorry! Maybe later someday.
Moved it to the feature roadmap
Usually you want to increase weight when you hit the upper limit though, right? Like the standard double progression - you have a range 8-12, and once you hit 12,...
Currently, if you use rep ranges with `progress: lp`, then it uses the top of the range to make a decision if you need to bump up the weight, and...
You can kinda do that right now, with creating a non used exercise, and reuse its progress: ``` my_very_cool_progression: Squat / 1x1 / used: none / progress: custom() {~ //...