GNU bug report logs - #16610
24.3.50; [ruby-mode] Variables named as built-in functions font-locked incorrectly

Previous Next

Full log

View this message in rfc822 format

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Bozhidar Batsov <bozhidar <at> batsov.com>
Cc: 16610 <at> debbugs.gnu.org
Subject: bug#16610: 24.3.50; [ruby-mode] Variables named as built-in functions font-locked incorrectly
Date: Sat, 01 Feb 2014 17:19:17 +0200

Bozhidar Batsov <bozhidar <at> batsov.com> writes:

> In the following snippet `format` is font-locked as the built-in
> function, but it's actually a variable.
>
> respond_to do |format|
>   format.json do
>     # ...
>   end
> end
>
> This problem obviously exists for all built-ins, but it's not a big
> issue in general, since most of them don't have names that are likely to
> be used as variable names. Not sure if we can have a simple solution for
> this problem without a parser, though. I guess we can have a check if
> the built-in methods have arguments (as most of them have).

A lot of them don't, though (or have no required arguments): __callee__,
__dir__, __method__, binding, caller, block_given?, exit, exit!, raise,
(s)rand, readline(s), sleep.

Guess we can separate these, and for all others, check if they're
followed by " *[]|,.)}]\\|$".

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.