From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Faces for strong, emph and friends in Info? Date: Wed, 10 Apr 2024 19:51:27 +0300 Message-ID: <86le5lupo0.fsf@gnu.org> References: <86o7ajyk6v.fsf@gnu.org> <87o7ajssgp.fsf@gmail.com> <86jzl7yajk.fsf@gnu.org> <87jzl6syde.fsf@gmail.com> <86le5mx3j8.fsf@gnu.org> <878r1lrydu.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31619"; mail-complaints-to="usenet@ciao.gmane.io" Cc: raman@google.com, emacs-devel@gnu.org To: Robert Pluim Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Apr 10 18:52:46 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rubBl-00082L-RF for ged-emacs-devel@m.gmane-mx.org; Wed, 10 Apr 2024 18:52:46 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rubAx-0004mu-VU; Wed, 10 Apr 2024 12:51:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rubAp-0004mU-2K for emacs-devel@gnu.org; Wed, 10 Apr 2024 12:51:47 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rubAo-0001wX-N9; Wed, 10 Apr 2024 12:51:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=9E9mnWYbG63A0e7dFbV/eHb5/AcbQwlHCC5NW8sv8WA=; b=IdkM4aDm4YBTmUKxiyq7 W59qA7v9iU5jDeD5XVpP62zX6KXXh1xFASUWMzoJ8A2P1mg4LKvmd/65HeyWP/vIFQxgcdFj3rYEU I75Vqigs+bHOZaSu1729NIJWUQFwktojPqPpOLwAJA54Mmtm3AsA/gyAGPnsBn8/7QkdNrIVWeW1r fGSUibaDyDOTn5aWluMJHB4iNQfhZ2sKQnJk/OsteTFN6A7y5FI40H7Di+rlFGj1IeBjAEt7mAI0m UnzlA97uK77MOtBmicjgn7jAy1vQA4XvyowmfOcm9EXidE02SaNEHnhZtGMwuWvDUbMSU28AwohZ2 c8NA8iLzMNN2/Q==; In-Reply-To: <878r1lrydu.fsf@gmail.com> (message from Robert Pluim on Wed, 10 Apr 2024 18:11:25 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:317668 Archived-At: > From: Robert Pluim > Cc: raman@google.com, emacs-devel@gnu.org > Date: Wed, 10 Apr 2024 18:11:25 +0200 > > >>>>> On Tue, 09 Apr 2024 12:56:43 +0300, Eli Zaretskii 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. This can happen in Texinfo anywhere, and there's nothing we can do to avoid this, in general. > 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: Forgive me, but I think you are trying to solve too many loosely related problems at once, so you take a simple problem and conclude that it's almost unsolvable. Let me try to simplify things: > - 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 > {} We match whatever the Texinfo source produced. In the above case, the colon will be included, and if the author doesn't like the results, they need to say @strong{Warning}: instead. (But since this produces bold in the printed version, I guess including the colon is actually perfectly okay.) > - do we match across newlines? Yes, we do. > - 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?) Not a problem for this feature to solve. If people dislike what it will produce, they will either turn off this feature (which must be optional, btw) or go back and wrap in @w what they want. We do that already with the likes of @code and @kbd, where it matters, so how are these markups different? > - 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. A single toggle is enough.