From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46312@debbugs.gnu.org, 40844@debbugs.gnu.org,
stephen.berman@gmx.net, 43941@debbugs.gnu.org,
jidanni@jidanni.org
Subject: bug#40844: bug#46312: HTML+ mode vs. quotes
Date: Mon, 14 Jun 2021 16:02:02 +0300 [thread overview]
Message-ID: <83zgvs61md.fsf@gnu.org> (raw)
In-Reply-To: <87y2bczjmn.fsf_-_@gnus.org> (message from Lars Ingebrigtsen on Mon, 14 Jun 2021 15:00:16 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 46312@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>,
> 40844@debbugs.gnu.org, 43941@debbugs.gnu.org, jidanni@jidanni.org
> Date: Mon, 14 Jun 2021 15:00:16 +0200
>
> 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...
Fine with me.
next prev parent reply other threads:[~2021-06-14 13:02 UTC|newest]
Thread overview: 17+ 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 ` Eli Zaretskii [this message]
2021-06-14 13:52 ` Stephen Berman
2021-06-14 13:58 ` bug#43941: " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zgvs61md.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40844@debbugs.gnu.org \
--cc=43941@debbugs.gnu.org \
--cc=46312@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.