unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: 54745@debbugs.gnu.org
Subject: bug#54745: Subject: 28.1; woman fails on "file"
Date: Wed, 06 Apr 2022 14:14:41 +0300	[thread overview]
Message-ID: <83mtgycvku.fsf@gnu.org> (raw)
In-Reply-To: <6b928406-f552-c2a5-a672-04832b8b37bd@easy-emacs.de> (message from Andreas Röhler on Wed, 6 Apr 2022 11:20:52 +0200)

> Date: Wed, 6 Apr 2022 11:20:52 +0200
> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
> 
> M-x woman RET file RET
> 
> errors saying:
> 
> Debugger entered--Lisp error: (error "WoMan can only format man pages
>   written with the usual ‘-man’ macros") signal(error ("WoMan can only
>   format man pages written with the usual ‘-man’ macros"))
>   error("WoMan can only format man pages written with the usual `-man'
>   macros") woman-decode-region(1 21597) woman-decode-buffer()
>   woman-process-buffer()
>   woman-really-find-file("/usr/share/man/man1/file.1.gz" t "*WoMan 1
>   file*<2>") woman-find-file("/usr/share/man/man1/file.1.gz")
> 
> However from bash, manpage appears correctly.
> Also would read nicely from:  "man file > file.txt"

woman.el doesn't use the 'man' program.  It is implemented completely
in Emacs Lisp.  So what 'man' does is not really relevant; what _is_
relevant is that Someone(TM) should step up and volunteer to keep
woman.el up-to-date with all the recent advances in roff markup.
Until that happens, the error you see above is intentional, meant to
alert you, the user, to the fact that the man page cannot be reliably
formatted this way.





  parent reply	other threads:[~2022-04-06 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  9:20 bug#54745: Subject: 28.1; woman fails on "file" Andreas Röhler
2022-04-06 10:02 ` Lars Ingebrigtsen
2022-04-06 11:14 ` Eli Zaretskii [this message]
2022-04-06 15:47   ` Andreas Röhler
2022-04-06 16:27     ` 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

  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=83mtgycvku.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54745@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    /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).