From: Juri Linkov <juri@jurta.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 12098@debbugs.gnu.org
Subject: bug#12098: How to trap errors in man?
Date: Wed, 01 Aug 2012 03:15:40 +0300 [thread overview]
Message-ID: <87pq7b5uvr.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAOnWdogGgfh-7n3pVCXtohfSHTg2utAczYy9qaJ3MJopVc+wJQ@mail.gmail.com> (Reuben Thomas's message of "Tue, 31 Jul 2012 12:53:43 +0100")
> In a discussion on gnu-prog-discuss today, there was an attempt to
> script Emacs as a standalone info reader. It was also desired to make
> it format man pages (like the standalone info reader) for programs
> that don't have an info manual.
The Emacs Info reader can format man pages with the help
of info-man.el.
> Personally, I'd just rip out all the asynchronous stuff and make "man"
> synchronous (I have man set to "bully" mode in my setup), but I am
> guessing that would be an unpopular change,
Yes, the delay when the whole session is freezing during formatting would
be undesirable. The current situation with asynchronous popping up buffers
is not perfect either. In bug#9084 we are trying to improve this by
modifying man.el to work more like async shell commands.
> so I'm wondering if there's some other way to make it possible to use
> man synchronously and/or allow man's caller to find out about errors.
You can use `Man-cooked-hook' that is called at the end of
`Man-bgproc-sentinel'. In this hook you can check whether the value of
`Man-page-list' is nil.
next prev parent reply other threads:[~2012-08-01 0:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 11:53 bug#12098: How to trap errors in man? Reuben Thomas
[not found] ` <handler.12098.B.13437360754310.ack@debbugs.gnu.org>
2012-07-31 13:36 ` bug#12098: Acknowledgement (How to trap errors in man?) Reuben Thomas
2012-07-31 16:27 ` Eli Zaretskii
2012-08-01 0:15 ` Juri Linkov [this message]
2012-08-01 0:38 ` bug#12098: How to trap errors in man? Reuben Thomas
2012-08-01 8:23 ` Juri Linkov
2012-08-01 11:11 ` Reuben Thomas
2020-08-19 12:49 ` Stefan Kangas
2020-08-19 12:53 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-19 13:08 ` Stefan Kangas
2020-08-19 13:08 ` Lars Ingebrigtsen
2020-08-19 13:10 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-19 13:24 ` Stefan Kangas
2020-08-19 13:28 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-19 13:51 ` Stefan Kangas
2020-08-19 13:51 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-19 14:12 ` Stefan Kangas
2020-08-19 14:21 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-19 15:17 ` Stefan Kangas
2020-08-19 15:22 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-14 6:05 ` Lars Ingebrigtsen
2020-08-19 13:14 ` Stefan Kangas
2020-08-20 0:37 ` Juri Linkov
2020-08-21 7:25 ` Stefan Kangas
2020-08-21 7:41 ` Eli Zaretskii
2020-08-21 9:41 ` Reuben Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2012-08-01 9:05 ` Andy Moreton
2012-08-01 23:10 ` Juri Linkov
2012-08-01 8:27 ` Thierry Volpiatto
2012-08-01 8:41 ` Juri Linkov
2012-08-01 8:58 ` Thierry Volpiatto
2012-08-01 9:29 ` Thierry Volpiatto
2012-08-01 23:12 ` Juri Linkov
2012-08-02 5:20 ` Thierry Volpiatto
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=87pq7b5uvr.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=12098@debbugs.gnu.org \
--cc=rrt@sc3d.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 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).