unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46312@debbugs.gnu.org, 40844@debbugs.gnu.org,
	43941@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#46312: HTML+ mode vs. quotes
Date: Mon, 14 Jun 2021 15:52:40 +0200	[thread overview]
Message-ID: <8735tkft93.fsf@gmx.net> (raw)
In-Reply-To: <87y2bczjmn.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Mon, 14 Jun 2021 15:00:16 +0200")

On Mon, 14 Jun 2021 15:00:16 +0200 Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> Upthread Eli said "some SGML/HTML expert should say if that is TRT".
>> I'm no such expert so I can't make that decision.
>
> I'm not either, but at this point I'd rather apply the patch and then we
> can see whether some SGML expert pipes up...

Sounds good.

>> Here's the test, in case someone else wants to see if
>> they can figure it out; I haven't succeeded:
>
> Just needs a `font-lock-ensure' after `html-mode'.  :-)  Then the test
> fails without your patch, and passes with your patch.

Ah, thanks.  The ways of font lock are unfathomable to me.

> So I went ahead and pushed your patch (and the test) to Emacs 28 (with
> some minor changes to the test).

Thanks.  I noticed, unfortunately only just now, that the ert test
includes the unused let-bound variable `results' which I inadvertantly
left behind from the previous version, and which will probably make the
byte-compiler complain.

Steve Berman





  parent reply	other threads:[~2021-06-14 13:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 14:30 bug#43941: HTML+ mode: dangerous apostrophe after fullwidth parenthesis 積丹尼 Dan Jacobson
2020-10-12 14:48 ` Eli Zaretskii
2020-10-12 14:52   ` 積丹尼 Dan Jacobson
2020-10-12 15:11   ` Stephen Berman
2020-10-12 15:20     ` Eli Zaretskii
2020-10-12 16:17       ` Stephen Berman
2020-10-12 16:29         ` Eli Zaretskii
2020-10-12 17:21           ` Stephen Berman
2020-10-12 17:38             ` Eli Zaretskii
2020-10-12 21:26               ` Stephen Berman
2020-10-13 10:37                 ` Stephen Berman
2021-06-13 12:21                   ` bug#43941: bug#40844: html mode sometimes fooled by apostrophe Lars Ingebrigtsen
2021-06-13 18:14                     ` Stephen Berman
2021-06-14 13:00                       ` bug#43941: bug#46312: HTML+ mode vs. quotes Lars Ingebrigtsen
2021-06-14 13:02                         ` bug#40844: " Eli Zaretskii
2021-06-14 13:52                         ` Stephen Berman [this message]
2021-06-14 13:58                           ` bug#43941: " Lars Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
2021-02-04 22:57 積丹尼 Dan Jacobson
2021-02-05  9: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=8735tkft93.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=40844@debbugs.gnu.org \
    --cc=43941@debbugs.gnu.org \
    --cc=46312@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    --cc=larsi@gnus.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).