From: Lars Ingebrigtsen <larsi@gnus.org>
To: Bob Hepple <bob.hepple@gmail.com>
Cc: 25585@debbugs.gnu.org
Subject: bug#25585: Fwd: [reddit] 1 new message from u/hvis
Date: Wed, 19 Aug 2020 13:49:16 +0200 [thread overview]
Message-ID: <87lfia6ekj.fsf@gnus.org> (raw)
In-Reply-To: <CAHzpm2i_3GHpwLvxSqxMDNEb_R74==p5GTJhUh78OM9L-J869Q@mail.gmail.com> (Bob Hepple's message of "Wed, 01 Feb 2017 23:31:50 +0000")
Bob Hepple <bob.hepple@gmail.com> writes:
> This patch (suggested by https://reddit.com/u/hvis) works for me ...
>
> diff --git a/lisp/progmodes/sh-script.el b/lisp/progmodes/sh-script.el
>
> index a0bbf55..dc296a2 100644
> --- a/lisp/progmodes/sh-script.el
> +++ b/lisp/progmodes/sh-script.el
> @@ -483,6 +483,7 @@ sh-mode-syntax-table
> ?~ "_"
> ?, "_"
> ?= "."
> + ?/ "."
> ?\; "."
> ?| "."
> ?& "."
I've respun the patch below...
So this would change the / character into a punctuation character in
shell buffers? It fixes the reported problem, and it does seem
reasonable to have / classified like that.
Does anybody object to applying this patch? There may be unwanted side
effects...
diff --git a/lisp/progmodes/sh-script.el b/lisp/progmodes/sh-script.el
index 5a47594878..8cd3aad268 100644
--- a/lisp/progmodes/sh-script.el
+++ b/lisp/progmodes/sh-script.el
@@ -386,6 +386,7 @@ sh-mode-syntax-table
?~ "_"
?, "_"
?= "."
+ ?/ "."
?\; "."
?| "."
?& "."
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-19 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170201155249.114487.66089.C90F097C@redditmail.com>
2017-02-01 23:31 ` bug#25585: Fwd: [reddit] 1 new message from u/hvis Bob Hepple
2020-08-19 11:49 ` Lars Ingebrigtsen [this message]
2020-08-19 12:00 ` Dmitry Gutov
2020-08-19 12:07 ` Lars Ingebrigtsen
2020-08-19 12:11 ` Dmitry Gutov
2020-10-02 5:12 ` 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=87lfia6ekj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=25585@debbugs.gnu.org \
--cc=bob.hepple@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).