https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112018-02-28T08:10:24ZRuby Issue Tracking SystemRuby master - Bug #14558: "Backtrace in reverse order" always upsets my brain!https://redmine.ruby-lang.org/issues/14558?journal_id=707142018-02-28T08:10:24Zmrkn (Kenta Murata)muraken@gmail.com
<ul></ul><blockquote>
<p>it sometimes "reversed", sometimes "non-reversed"</p>
</blockquote>
<p>Is it acceptable that the backtrace is always new, 2.5-style order?</p> Ruby master - Bug #14558: "Backtrace in reverse order" always upsets my brain!https://redmine.ruby-lang.org/issues/14558?journal_id=707152018-02-28T08:20:01Zgfx (Goro FUJI)gfuji@cpan.org
<ul></ul><p>mrkn (Kenta Murata) wrote:</p>
<blockquote>
<blockquote>
<p>it sometimes "reversed", sometimes "non-reversed"</p>
</blockquote>
<p>Is it acceptable that the backtrace is always new, 2.5-style order?</p>
</blockquote>
<p>Might be acceptable, or at least it's better than the current "random" order.</p>
<p>Why not provide a way to customize it, for example <code>RubyVM.backtrace_reverse_order = -> (io) { true }</code>, where <code>-> (io) { io.tty? }</code> is the algorithm that 2.5.0 has.</p> Ruby master - Bug #14558: "Backtrace in reverse order" always upsets my brain!https://redmine.ruby-lang.org/issues/14558?journal_id=707202018-02-28T12:39:16Zshevegen (Robert A. Heiler)shevegen@gmail.com
<ul></ul><p>I think I understand what Goro Fuji refers to.</p>
<p>It sometimes takes me a while as well to adjust to the change, too.</p>
<p>What I found in particular hard is when it is a long backtrace AND<br>
when the .rb file names are long and deeply branched on the local<br>
filesystem, for example:</p>
<pre><code>/foo/bar/bla/somewhere_anywhere/really_long_path/very_long_name_of_a_file.rb
</code></pre>
<p>Then it becomes quite difficult for me to see where the error is<br>
because it is overflowing on my console output. This leads to a<br>
situation where the error reported number is on the right side,<br>
but the error is often on the next line overflow on the left<br>
side, which actually makes the intent of the change a bit moot<br>
since it may take me longer than before to find the error. :D</p>
<p>I think the <strong>suggestion to customize</strong> it would be best. Then people<br>
could use what they prefer in regards to the order style in use.</p>
<p>I don't mind the changed tracking order so much as such, but I think<br>
it really would be best if there is some way to customize it, either<br>
at run-time, or settable at compile-time via a configure switch<br>
or both ways (but "run-time" is probably best, as Goro Fuji showed<br>
in his example).</p> Ruby master - Bug #14558: "Backtrace in reverse order" always upsets my brain!https://redmine.ruby-lang.org/issues/14558?journal_id=707252018-02-28T21:41:47Zvo.x (Vit Ondruch)v.ondruch@tiscali.cz
<ul></ul><p>I wish the original backtrace order is back. If at least the order was consistent. I must agree that the current situation is unbearable.</p> Ruby master - Bug #14558: "Backtrace in reverse order" always upsets my brain!https://redmine.ruby-lang.org/issues/14558?journal_id=859322020-06-01T17:08:19Zjeremyevans0 (Jeremy Evans)merch-redmine@jeremyevans.net
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>The backtrace order was switched back in <a class="changeset" title="eval_error.c: revert the "reversed" backtrace [Feature #8661] Now, the order is good, old-fashio..." href="https://redmine.ruby-lang.org/projects/ruby-master/repository/git/revisions/487d0c99d53208594702bb3ce1c657130fb8d65f">487d0c99d53208594702bb3ce1c657130fb8d65f</a>.</p>