From: "Eregon (Benoit Daloze) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "Eregon (Benoit Daloze)" <noreply@ruby-lang.org>
Subject: [ruby-core:116299] [Ruby master Feature#16495] Inconsistent quotes in error messages
Date: Thu, 18 Jan 2024 15:24:14 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-106321.20240118152414.32676@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16495.20200109215418.32676@ruby-lang.org
Issue #16495 has been updated by Eregon (Benoit Daloze).
Great to see progress on this issue.
Agreed, for method names and file names, single quotes are best.
Backticks are best for quoting source code, and there is no source code in Ruby backtraces.
----------------------------------------
Feature #16495: Inconsistent quotes in error messages
https://bugs.ruby-lang.org/issues/16495#change-106321
* Author: Kolano (Kenneth Kolano)
* Status: Open
* Priority: Normal
* Assignee: matz (Yukihiro Matsumoto)
----------------------------------------
Error messages use inconsistent pairs of quotes, for instance:
```
-e:1:in `<main>': undefined local variable or method `foo' for main:Object (NameError)
```
where a back tick is used on the left-hand side, and a single quote is used on the right.
The same quotes should be used on either side of the elements being quoted.
--
https://bugs.ruby-lang.org/
______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/
next prev parent reply other threads:[~2024-01-18 15:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16495.20200109215418.32676@ruby-lang.org>
2020-08-07 0:27 ` [ruby-core:99506] [Ruby master Feature#16495] Inconsistent quotes in error messages naumovvladislav
2022-06-10 2:24 ` [ruby-core:108840] " ioquatix (Samuel Williams)
2022-06-15 3:23 ` [ruby-core:108923] " nobu (Nobuyoshi Nakada)
2022-06-15 10:03 ` [ruby-core:108926] " ioquatix (Samuel Williams)
2022-06-15 11:28 ` [ruby-core:108927] " nobu (Nobuyoshi Nakada)
2022-06-15 12:09 ` [ruby-core:108929] " ioquatix (Samuel Williams)
2022-06-15 12:49 ` [ruby-core:108930] " nobu (Nobuyoshi Nakada)
2022-06-15 13:02 ` [ruby-core:108932] " zverok (Victor Shepelev)
2022-06-15 14:20 ` [ruby-core:108933] " sawa (Tsuyoshi Sawada)
2022-06-15 15:43 ` [ruby-core:108934] " austin (Austin Ziegler)
2022-06-15 16:21 ` [ruby-core:108935] " zverok (Victor Shepelev)
2024-01-03 13:28 ` [ruby-core:115993] " ivoanjo (Ivo Anjo) via ruby-core
2024-01-03 13:33 ` [ruby-core:115994] " mdalessio (Mike Dalessio) via ruby-core
2024-01-04 0:31 ` [ruby-core:116002] " joshuap (Josh Wood) via ruby-core
2024-01-18 7:54 ` [ruby-core:116295] " matz (Yukihiro Matsumoto) via ruby-core
2024-01-18 13:43 ` [ruby-core:116296] " Dan0042 (Daniel DeLorme) via ruby-core
2024-01-18 15:24 ` Eregon (Benoit Daloze) via ruby-core [this message]
2024-01-18 20:28 ` [ruby-core:116310] " mame (Yusuke Endoh) via ruby-core
2024-01-19 7:45 ` [ruby-core:116313] " mame (Yusuke Endoh) via ruby-core
2024-02-14 5:05 ` [ruby-core:116728] " matz (Yukihiro Matsumoto) via ruby-core
2024-02-17 22:22 ` [ruby-core:116828] " ioquatix (Samuel Williams) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-106321.20240118152414.32676@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).