From: sawadatsuyoshi@... Date: 2016-04-27T05:01:21+00:00 Subject: [ruby-core:75213] [Ruby trunk Bug#12321] Backticks in log output cause issues Issue #12321 has been updated by Tsuyoshi Sawada. Back tick can appear anywhere else in a code block even if you get rid of this particular use in Ruby error messages. If you claim it breaks when you simply surround such string by backticks, then the way you are doing it is wrong. You should escape the backticks somehow when embedding that as a piece of code. In markdown, it is done by using multiple backticks. But I think that there is no need for Ruby error messages to follow TeX's convention, as TeX is designed for the beauty of the output (with the cost of the source code being ugly), whereas Ruby error messages are to be read as is, and using a combination of backtick and single quote like ``` `foo' ``` surely looks ugly. ---------------------------------------- Bug #12321: Backticks in log output cause issues https://bugs.ruby-lang.org/issues/12321#change-58346 * Author: Derek Kniffin * Status: Open * Priority: Normal * Assignee: * ruby -v: ruby 2.2.3p173 * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- I would like to propose changing ruby's log output slightly. The issue I have is with output like this: ~~~ NoMethodError: undefined method `some_method' for nil:NilClass ~~~ In particular, I don't like how some_method has a backtick on the left, and a single quote on the right. I would much prefer to have single quotes on both sides. Now, this may seem like a very knit-picky thing, but in the modern age where markdown is very widely used, this causes an issue quite often. For instance, every time I copy/paste a log snippet like that into slack, and try wrapping it in backticks, to denote that it's a code snippet, it formats it wrong. I've tried to find a reason why ruby's output does this, but I couldn't find anything. The best guess I have is that it was a way to emulate opening and closing apostrophes, but it's a poor replacement for that. If someone else can enlighten me about the reasoning, I'd be very curious to know it. -- https://bugs.ruby-lang.org/ Unsubscribe: