From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52496@debbugs.gnu.org, "Andreas Schwab" <schwab@linux-m68k.org>,
"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Subject: bug#52496: syntax highlighting problem on emacs shell-script mode
Date: Tue, 21 Dec 2021 07:20:47 +0300 [thread overview]
Message-ID: <CAJddU=q_SxY8jZLjCgHgNPZesci3cBk5CSZwGHs=HVp7CnvP8Q@mail.gmail.com> (raw)
In-Reply-To: <87sfunpq1w.fsf@gnus.org>
Yes, I agree. I think this is enough for now until a refactor becomes
necessary.
On Mon, Dec 20, 2021 at 12:46 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> 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
next prev parent reply other threads:[~2021-12-21 4:20 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
2021-12-21 4:20 ` Yilkal Argaw [this message]
[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='CAJddU=q_SxY8jZLjCgHgNPZesci3cBk5CSZwGHs=HVp7CnvP8Q@mail.gmail.com' \
--to=yilkalargawworkneh@gmail.com \
--cc=52496@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.org \
/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).