ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "nobu (Nobuyoshi Nakada)" <noreply@ruby-lang.org>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:108930] [Ruby master Feature#16495] Inconsistent quotes in error messages
Date: Wed, 15 Jun 2022 12:49:54 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-98015.20220615124954.32676@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16495.20200109215418.32676@ruby-lang.org

Issue #16495 has been updated by nobu (Nobuyoshi Nakada).


As it seems working in other than titles, it would be an issue of GitHub.
You should report it to GitHub, not here.

----------------------------------------
Feature #16495: Inconsistent quotes in error messages
https://bugs.ruby-lang.org/issues/16495#change-98015

* 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/

  parent reply	other threads:[~2022-06-15 12:50 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 ` nobu (Nobuyoshi Nakada) [this message]
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 ` [ruby-core:116299] " Eregon (Benoit Daloze) via ruby-core
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-98015.20220615124954.32676@ruby-lang.org \
    --to=ruby-core@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).