unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: T.V Raman <raman@google.com>, "rpluim@gmail.com" <rpluim@gmail.com>
Cc: "eliz@gnu.org" <eliz@gnu.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Faces for strong, emph and friends in Info?
Date: Tue, 9 Apr 2024 01:47:32 +0000	[thread overview]
Message-ID: <SJ0PR10MB54887DB89B98E3BAF6079B06F3072@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <26132.28632.986421.497515@google.com>

> After  applying the patch, @strong is turning bold,
> but @emph is still showing up with '_'.
> As an example in node on dabbrevs:

That contains a newline char.  See what I
wrote in my previous mail.

With info+.el, using the default value of
option `Info-emphasis-regexp' ("_\(\sw+\)_"),
that text is also not highlighted.

But if you change the option value to this
one (mentioned in the doc string) then the
text is highlighted as you'd expect:
"_\(\sw+\(\s-+\sw+\)*\)_".

However, with that regexp you'll encounter
problems with other occurrences of `_'.

There's no single silver bullet for this.
That's why my approach was to try to make
it easy for users to tailor the behavior
to what they want, and to easily change it
any time. 

My suggestion is to try a given regexp value
and then peruse a manual (different manuals
can present different challenges).  (I've
visited zillions of nodes in Emacs and Elisp
manuals, to see the effects.)

  reply	other threads:[~2024-04-09  1:47 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       ` [External] : " Drew Adams
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       ` Drew Adams [this message]
2024-04-09  2:23         ` [External] : " 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

  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=SJ0PR10MB54887DB89B98E3BAF6079B06F3072@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 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).