unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: raman@google.com,  emacs-devel@gnu.org
Subject: Re: Faces for strong, emph and friends in Info?
Date: Wed, 10 Apr 2024 18:11:25 +0200	[thread overview]
Message-ID: <878r1lrydu.fsf@gmail.com> (raw)
In-Reply-To: <86le5mx3j8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Apr 2024 12:56:43 +0300")

>>>>> On Tue, 09 Apr 2024 12:56:43 +0300, Eli Zaretskii <eliz@gnu.org> said:

    Eli> Here's the first hit I found:

    Eli>   ‘woman-use-topic-at-point’
    Eli>        A boolean value that defaults to ‘nil’.  If non-‘nil’ then the
    Eli>        ‘woman’ command uses the word at point as the topic, _without
    Eli>        interactive confirmation_, if it exists as a topic.

    Eli> We never wrap @emph and @strong in @w, so it's small wonder this
    Eli> happens quite a lot.

In the original texi "without interactive confirmation" is all on the
same line, so this one is understandable.

And thereʼs indentation in the resulting info file, which means when
we use '_' to simulate italics, the indentation does not look good. So
hereʼs what needs deciding:

- what do we fontify? There are instances of eg @strong{Warning:}
where I could argue that the ':' should be outside the @strong{}. So
we either match ?: (and ?.) as well, or move those chars outside the
{}

- do we match across newlines? (in fact, in info buffers, we have to
make an effort to not match across newlines, since newline has
whitespace syntax there, so [[:space:]] matches it.

- if we match across newlines, do we go around wraping @w around all
the multiword @emph and @strong? (could we persuade the texinfo
project to do this for us or emit a warning?)

- how configurable does this need to be? Iʼd say a single toggle is
enough, but Drew might disagree. I guess adding a defcustom for the
matching regexp is easy enough as well.

Robert

PS "This looks like a nice simple change, I have a small amount of
time" always seems to turn into something much bigger with Emacs :)
-- 



  reply	other threads:[~2024-04-10 16:11 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 [this message]
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

  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=878r1lrydu.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=raman@google.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).