From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 54745@debbugs.gnu.org
Subject: bug#54745: Subject: 28.1; woman fails on "file"
Date: Wed, 6 Apr 2022 17:47:04 +0200 [thread overview]
Message-ID: <47a34968-7a7b-f222-5590-1e3cb59b68d8@easy-emacs.de> (raw)
In-Reply-To: <83mtgycvku.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1313 bytes --]
Am 06.04.22 um 13:14 schrieb Eli Zaretskii:
>> 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.
That workaround attached does it here.
[-- Attachment #1.2: Type: text/html, Size: 1865 bytes --]
[-- Attachment #2: woman.el.patch --]
[-- Type: text/x-patch, Size: 653 bytes --]
diff --git a/lisp/woman.el b/lisp/woman.el
index c0c8f34348..2f923c5455 100644
--- a/lisp/woman.el
+++ b/lisp/woman.el
@@ -1644,7 +1644,9 @@ woman-really-find-file
(setq default-directory (file-name-directory filename))
(setq-local backup-inhibited t)
(set-visited-file-name "")
- (woman-process-buffer)))
+ (or (ignore-errors (woman-process-buffer))
+ (erase-buffer)
+ (shell-command (concat "man " (replace-regexp-in-string "^\\([^\\.]+\\).\\(.*\\)" "\\1" (file-name-nondirectory (file-name-sans-extension filename)))) bufname))))
(defun woman-process-buffer ()
"The second half of `woman-really-find-file'!"
next prev parent reply other threads:[~2022-04-06 15:47 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
2022-04-06 15:47 ` Andreas Röhler [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47a34968-7a7b-f222-5590-1e3cb59b68d8@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=54745@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.