all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xiyue Deng <manphiz@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69483@debbugs.gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#69483: 29.2; "\fC" macro in ox-man.el
Date: Fri, 01 Mar 2024 03:24:31 -0800	[thread overview]
Message-ID: <87o7byjits.fsf@debian-hx90.lan> (raw)
In-Reply-To: <864jdqsaac.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Mar 2024 09:04:11 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Xiyue Deng <manphiz@gmail.com>
>> Date: Thu, 29 Feb 2024 16:21:26 -0800
>> 
>> 
>> "mu4e"[1] (a popular Emacs mail client) uses Org to generate its
>> manpages.  However, the generated output contains macros that are not
>> understood by groff.  After some debugging, Jeremy traced this back to
>> the macro "\fC" used in ox-man.el[2].  Git history shows that this may
>> have been there since the beginning.  We tried to find a documentation
>> for the "\fC" macro but has not been able to find one.  Jeremy suggests
>> that "C" may be an old alias for Courier, and if that's the case it
>> should be changed to "\f[CR]".  Would be great if Org people can
>> confirm.
>> 
>> [1] https://github.com/djcb/mu
>> [2] E.g. https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/org/ox-man.el#n362
>>     (Credit to Jeremy Sowden <jeremy@azazel.net>)
>
> Thanks.  I think this should be reported to the Org developers first,
> as ox-man.el is developed and maintained by them.

Ack.  Sent using `M-x org-submit-bug-report'.

-- 
Xiyue Deng





  reply	other threads:[~2024-03-01 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-01  0:21 bug#69483: 29.2; "\fC" macro in ox-man.el Xiyue Deng
2024-03-01  7:04 ` Eli Zaretskii
2024-03-01 11:24   ` Xiyue Deng [this message]
2024-03-09  8:45     ` Eli Zaretskii

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=87o7byjits.fsf@debian-hx90.lan \
    --to=manphiz@gmail.com \
    --cc=69483@debbugs.gnu.org \
    --cc=eliz@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 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.