unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Bozhidar Batsov <bozhidar@batsov.com>
Cc: 17057@debbugs.gnu.org
Subject: bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing)
Date: Fri, 21 Mar 2014 16:47:59 +0200	[thread overview]
Message-ID: <87bnwzwqu8.fsf@yandex.ru> (raw)
In-Reply-To: <m2r45vk91h.fsf@batsov.com> (Bozhidar Batsov's message of "Fri, 21 Mar 2014 14:53:14 +0200")

Bozhidar Batsov <bozhidar@batsov.com> writes:

> Here's a few examples:
>
> "this is #$$"
>
> var = $!
>
> Things are different for:
>
> "this is #$1"
>
> var = $1

Have you tried it in the latest Emacs? For me, only one example

"this is #$$"

is not highlighted (I'll fix that).

> There's another thing to consider - do built-in global vars should be
> font-locked like built-ins or like the other (user-defined) global
> variables? Personally I'd font-lock them as built-in to underline their
> significance.

Hmmm, maybe. But we also highlight nil, self, true, false, __LINE__,
__ENCODING__ and __FILE__ with font-lock-variable-name-face. Should we
change these, too?





  reply	other threads:[~2014-03-21 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 12:53 bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing) Bozhidar Batsov
2014-03-21 14:47 ` Dmitry Gutov [this message]
2014-03-21 14:53   ` Bozhidar Batsov
2014-03-22 10:02     ` Bozhidar Batsov
2014-03-22 10:05       ` Bozhidar Batsov
2014-03-24  7:33         ` Dmitry Gutov
2014-03-24  9:12     ` Dmitry Gutov
2014-03-24  9:45       ` Bozhidar Batsov
2014-03-26 12:35         ` Dmitry Gutov
2014-03-26 12:42           ` Bozhidar Batsov
2014-03-27  8:26             ` Dmitry Gutov

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-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bnwzwqu8.fsf@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=17057@debbugs.gnu.org \
    --cc=bozhidar@batsov.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).