unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 52496@debbugs.gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
	Yilkal Argaw <yilkalargawworkneh@gmail.com>
Subject: bug#52496: syntax highlighting problem on emacs shell-script mode
Date: Mon, 20 Dec 2021 10:46:03 +0100	[thread overview]
Message-ID: <87sfunpq1w.fsf@gnus.org> (raw)
In-Reply-To: <87pmpsmwb3.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Sun, 19 Dec 2021 16:46:56 +0100")

Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:

> So IIUC for here-documents anything is fair game except (1)
> {single,double,back} quotes (2) metacharacters (3) backslashes and
> comment openers (#); all of which can still be used if quoted or escaped
> *on the opening line only*.

Thanks.

As far as I can see, sh-mode doesn't really try too hard to be correct
here -- it accepts word constituents, but then adds back -/~._ which it
has defined as punctuation in `sh-mode-syntax-table'.  So perhaps we
should just continue doing that and add @, too, even though that's not
very satisfactory.

So I've now done that in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-12-20  9:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15  0:35 bug#52496: syntax highlighting problem on emacs shell-script mode Yilkal Argaw
2021-12-19 12:54 ` Lars Ingebrigtsen
2021-12-19 13:30   ` Andreas Schwab
2021-12-19 13:33     ` Lars Ingebrigtsen
2021-12-19 13:57       ` Andreas Schwab
2021-12-19 14:10         ` Lars Ingebrigtsen
2021-12-19 14:47           ` Andreas Schwab
2021-12-19 15:46             ` Kévin Le Gouguec
2021-12-20  9:46               ` Lars Ingebrigtsen [this message]
2021-12-21  4:20                 ` Yilkal Argaw
     [not found]   ` <CAJddU=rbKWaPHBmxAGz-bM4TsziYPOoC5tOJMKpybWOE-GJEPA@mail.gmail.com>
2021-12-19 19:42     ` Lars Ingebrigtsen

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=87sfunpq1w.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52496@debbugs.gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=yilkalargawworkneh@gmail.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).