From: shevegen@... Date: 2018-02-28T12:39:17+00:00 Subject: [ruby-core:85862] [Ruby trunk Bug#14558] "Backtrace in reverse order" always upsets my brain! Issue #14558 has been updated by shevegen (Robert A. Heiler). I think I understand what Goro Fuji refers to. It sometimes takes me a while as well to adjust to the change, too. What I found in particular hard is when it is a long backtrace AND when the .rb file names are long and deeply branched on the local filesystem, for example: /foo/bar/bla/somewhere_anywhere/really_long_path/very_long_name_of_a_file.rb Then it becomes quite difficult for me to see where the error is because it is overflowing on my console output. This leads to a situation where the error reported number is on the right side, but the error is often on the next line overflow on the left side, which actually makes the intent of the change a bit moot since it may take me longer than before to find the error. :D I think the **suggestion to customize** it would be best. Then people could use what they prefer in regards to the order style in use. I don't mind the changed tracking order so much as such, but I think it really would be best if there is some way to customize it, either at run-time, or settable at compile-time via a configure switch or both ways (but "run-time" is probably best, as Goro Fuji showed in his example). ---------------------------------------- Bug #14558: "Backtrace in reverse order" always upsets my brain! https://bugs.ruby-lang.org/issues/14558#change-70720 * Author: gfx (Goro FUJI) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin16] * Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN ---------------------------------------- A Ruby 2.5.0 feature "backtrace in reverse order", issued in https://bugs.ruby-lang.org/issues/8661, is confusing in developing Rails applications because I can't expect the order: it sometimes "reversed", sometimes "non-reversed". It just sucks. Please revert this feature, or provide a way to disable it. -- https://bugs.ruby-lang.org/ Unsubscribe: