From: "onf" <onf@disroot.org>
To: "Ihor Radchenko" <yantar92@posteo.net>
Cc: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
<emacs-orgmode@gnu.org>, <groff@gnu.org>
Subject: Re: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]
Date: Sun, 19 Jan 2025 17:43:43 +0100 [thread overview]
Message-ID: <D7678DN1I613.1VXANYL75QOKH@disroot.org> (raw)
In-Reply-To: <D7674O9TELET.1X1VZ2ALG8TMG@disroot.org>
On Sun Jan 19, 2025 at 5:38 PM CET, onf wrote:
> On Sun Jan 19, 2025 at 3:04 PM CET, Ihor Radchenko wrote:
> > "onf" <onf@disroot.org> writes:
> > >> I am wondering if the situations like the above should be caught by
> > >> groff linter. Currently, they seem not.
> > >
> > > They actually are:
> > > ...
> > > troff:<standard input>:2: warning: cannot select font 'C'
> > > One two three four.
> >
> > Sorry, I was not clear.
> > What I meant is
> >
> > \fBbold \fIitalic\fP\fP
>
> Hm. The behavior of \fP\fP is actually intended and can be used
> non-pathologically:
> [...]
s/(\\fP){2}/\1/
I can't imagine a case in which \fP\fP would make sense, so I agree it
could use a diagnostic, although what it's really diagnosing is poor
comprehension of the language in the user.
next prev parent reply other threads:[~2025-01-19 16:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 7:51 [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] Xiyue Deng
2024-03-03 13:30 ` Ihor Radchenko
2024-03-12 0:06 ` Xiyue Deng
2024-03-13 11:25 ` Ihor Radchenko
2024-03-14 21:46 ` Jeremy Sowden
2024-05-22 9:54 ` Ihor Radchenko
2024-12-18 17:20 ` G. Branden Robinson
2024-12-22 15:41 ` Ihor Radchenko
2024-12-31 17:00 ` G. Branden Robinson
2024-12-31 18:15 ` Ihor Radchenko
2024-12-31 18:42 ` onf
2024-12-31 18:54 ` onf
2025-01-01 9:38 ` Ihor Radchenko
2025-01-01 12:30 ` onf
2025-01-02 14:29 ` onf
2025-01-02 17:47 ` [BUG] ox-man: Nested markup is broken (was: [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)]) Ihor Radchenko
2025-01-02 21:51 ` onf
2025-01-03 8:38 ` [BUG] "\fC" macro in ox-man.el [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.2/lisp/org/)] G. Branden Robinson
2025-01-04 0:23 ` onf
2025-01-04 6:37 ` G. Branden Robinson
2025-01-04 20:10 ` onf
2025-01-05 15:24 ` Lennart Jablonka
2025-01-04 13:26 ` Ihor Radchenko
2025-01-04 16:22 ` Dave Kemper
2025-01-04 17:37 ` Ihor Radchenko
2025-01-02 12:14 ` G. Branden Robinson
2025-01-04 12:21 ` Ihor Radchenko
2025-01-19 7:43 ` Ihor Radchenko
2025-01-19 13:58 ` onf
2025-01-19 14:04 ` Ihor Radchenko
2025-01-19 16:38 ` onf
2025-01-19 16:43 ` onf [this message]
2025-01-02 12:38 ` G. Branden Robinson
2025-01-02 14:21 ` onf
2025-01-04 12:36 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D7678DN1I613.1VXANYL75QOKH@disroot.org \
--to=onf@disroot.org \
--cc=emacs-orgmode@gnu.org \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=yantar92@posteo.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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).