When running debug mode I stumble into differing installed gems (see error below). It would be great if we could configure our debug command. In my case I would love to prepend bundle exec in front of it.
Running command: rdebug-ide --host 127.0.0.1 --port 1234 -- $EXT_DIR/debug_minitest.rb 'test/system/audio_recordings_test.rb:6'
[2021-02-03 21:14:35.696] [DEBUG] [CHILD PROCESS OUTPUT] Fast Debugger (ruby-debug-ide 0.7.2, debase 0.2.4.1, file filtering is supported) listens on 127.0.0.1:1234
[2021-02-03 21:14:37.668] [DEBUG] [CHILD PROCESS OUTPUT] Uncaught exception: You have already activated minitest 5.14.3, but your Gemfile requires minitest 5.13.0. Prepending bundle exec to your command may solve this.
When running debug mode I stumble into differing installed gems (see error below). It would be great if we could configure our debug command. In my case I would love to prepend
bundle execin front of it.Running command: rdebug-ide --host 127.0.0.1 --port 1234 -- $EXT_DIR/debug_minitest.rb 'test/system/audio_recordings_test.rb:6' [2021-02-03 21:14:35.696] [DEBUG] [CHILD PROCESS OUTPUT] Fast Debugger (ruby-debug-ide 0.7.2, debase 0.2.4.1, file filtering is supported) listens on 127.0.0.1:1234 [2021-02-03 21:14:37.668] [DEBUG] [CHILD PROCESS OUTPUT] Uncaught exception: You have already activated minitest 5.14.3, but your Gemfile requires minitest 5.13.0. Prepending
bundle execto your command may solve this.