GNU bug report logs - #18379
24.3.93; Bash font lock: pretty inconsistent treatment of `` and $()

Previous Next

Package: emacs;

Reported by: Carlos Pita <carlosjosepita <at> gmail.com>

Date: Mon, 1 Sep 2014 14:19:02 UTC

Severity: minor

Found in version 24.3.93

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

Message #11 received at 18379 <at> debbugs.gnu.org (full text, mbox):

From: Carlos Pita <carlosjosepita <at> gmail.com>
To: Andreas Schwab <schwab <at> suse.de>
Cc: occitan <at> esperanto.org, 18379 <at> debbugs.gnu.org
Subject: Re: bug#18379: 24.3.93;
 Bash font lock: pretty inconsistent treatment of `` and $()
Date: Mon, 01 Sep 2014 16:27:58 -0300

Hi Andreas,

> They have different quoting rules, with `...` using rules similar to
> double quotes, whereas $(...) is a fully nesting construct.

True, but both contains bash code for a subshell which is far from being
an uninterpreted string. IMO the important distintion to highlight is
"intepreted code" vs "uninterpreted string", not the ability to nest vs
the inability to nest (due to different quoting rules).

I've been checking how other editors do this. vim works the way I'm
proposing, while scintilla based editors do it the emacs way. Regarding
my second observation before, neither vim nor scintilla treat the
leading word in a command substution in any special way, which I think
is sensible.

Cheers
--
Carlos
This bug report was last modified 154 days ago.

Previous Next

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