Uh oh!
There was an error while loading. Please reload this page.
Use default max_lines when calling up & down - #1094
Conversation
st0012
commented
Apr 4, 2024
I want to second this proposal as I also often need to chain |
c07fda0 to
caec1c5CompareHeyNonster
commented
Apr 5, 2024
Also probably useful to note that byebug-vs-debug.mov |
caec1c5 to
b1963e7CompareLaunchable Report❌ Test session #2907805 failed ❌ Test session #2907807 failed Passed test sessions✅ Test session #2907791 passed Build: refs_pull_1094_merge_b1963e7b72554c9672900ba046c3088598955488 |
HeyNonster
commented
May 19, 2024
Seems the protocol tests are flaky: #1060 |
b1963e7 to
a1df646CompareBoth `up` and `down` only show 1 source line when called, I think it would be more useful if they provided more context. This removes the `max_lines: 1` kwarg when they call `show_src`. `max_lines` in `show_src` will default to `CONFIG[:show_src_lines]`[^1]. [^1]:(https://github.com/ruby/debug/blob/0b77e8294b5b220b3b2a089bf09f94808654899a/lib/debug/thread_client.rb#L510)
a1df646 to
98a7521Compareko1
commented
Dec 17, 2024
Maybe we need to introduce another configuration. |
Description
Both
upanddownonly show 1 source line when called, I think it would be more useful if they provided more context. This removes themax_lines: 1kwarg when they callshow_src.max_linesinshow_srcwill default toCONFIG[:show_src_lines]1.Big thanks to @st0012 for showing me and @bquorning where this behavior is defined.
Footnotes
(https://github.com/ruby/debug/blob/0b77e8294b5b220b3b2a089bf09f94808654899a/lib/debug/thread_client.rb#L510) ↩