[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables
From: |
Dmitry Gutov |
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 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) |
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?
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Bozhidar Batsov, 2014/03/21
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing),
Dmitry Gutov <=
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Dmitry Gutov, 2014/03/24
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Bozhidar Batsov, 2014/03/24
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Dmitry Gutov, 2014/03/26
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Bozhidar Batsov, 2014/03/26
- bug#17057: 24.3.50; [ruby-mode] Font-locking of special global variables like $$ is broken(missing), Dmitry Gutov, 2014/03/27