From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Robert Pluim <rpluim@gmail.com>
Cc: "raman@google.com" <raman@google.com>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Faces for strong, emph and friends in Info?
Date: Mon, 8 Apr 2024 19:32:46 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488612E2BD7643C2035C5A5F3002@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86jzl7yajk.fsf@gnu.org>
> > + (while (re-search-forward "\\([*_]\\)\\([^*_\n]+\\)\\([*_]\\)"
> nil t)
>
> This is too fragile, I think. It matches stuff like "*Note foo_",
> which can happen in cross-references, for example. Also, what if
> @emph or @strong spans a newline?
See my mail about this.
___
I think it's good to let users decide
how tight/loose they want matching to
be - user option(s) for the regexp(s).
___
IMO, _..._ and *...* should be handled
separately.
Definitely don't let _...* and *..._ be
taken as emphasis of any kind.
And maybe you need to decide whether you
intend to allow combining the two: *_..._*
or _*...*_. (Does texinfo allow/produce
such combinations?)
next prev parent reply other threads:[~2024-04-08 19:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 14:49 Faces for strong, emph and friends in Info? T.V Raman
2024-04-08 14:59 ` Eli Zaretskii
2024-04-08 16:57 ` Robert Pluim
2024-04-08 17:28 ` T.V Raman
2024-04-08 18:06 ` [External] : " Drew Adams
2024-04-08 18:27 ` Eli Zaretskii
2024-04-08 19:32 ` Drew Adams [this message]
2024-04-09 9:01 ` Robert Pluim
2024-04-09 9:56 ` Eli Zaretskii
2024-04-10 16:11 ` Robert Pluim
2024-04-10 16:17 ` T.V Raman
2024-04-10 16:27 ` Robert Pluim
2024-04-10 16:53 ` Eli Zaretskii
2024-04-11 12:59 ` Robert Pluim
2024-04-11 14:10 ` T.V Raman
2024-04-10 16:51 ` Eli Zaretskii
2024-04-08 22:02 ` T.V Raman
2024-04-08 22:29 ` T.V Raman
2024-04-09 1:47 ` [External] : " Drew Adams
2024-04-09 2:23 ` T.V Raman
2024-04-09 4:22 ` Eli Zaretskii
2024-04-09 1:35 ` T.V Raman
2024-04-09 4:21 ` Eli Zaretskii
2024-04-09 13:29 ` T.V Raman
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=SJ0PR10MB5488612E2BD7643C2035C5A5F3002@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raman@google.com \
--cc=rpluim@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 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.