Open HeyNonster opened 7 months ago
I want to second this proposal as I also often need to chain whereami
after moving to a different frame, which IMO is not the best user experience in most cases.
Also probably useful to note that byebug
displays more lines by default making it quite a difference switching from byebug
to debug
:
https://github.com/ruby/debug/assets/47484308/5f2174b9-1264-4753-be71-14203977c69f
:x: Test session #2907805 failed details on CI
:bell: no issues :heavy_multiplication_x:1 test failed :heavy_check_mark:63 tests passed
:x: Test session #2907807 failed details on CI
:bell: no issues :heavy_multiplication_x:1 test failed :heavy_check_mark:63 tests passed
Build: refs_pull_1094_merge_b1963e7b72554c9672900ba046c3088598955488
Seems the protocol tests are flaky: https://github.com/ruby/debug/pull/1060
Description
Both
up
anddown
only show 1 source line when called, I think it would be more useful if they provided more context. This removes themax_lines: 1
kwarg when they callshow_src
.max_lines
inshow_src
will default toCONFIG[:show_src_lines]
^1.Big thanks to @st0012 for showing me and @bquorning where this behavior is defined.