From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: 12098@debbugs.gnu.org
Subject: bug#12098: How to trap errors in man?
Date: Wed, 01 Aug 2012 10:27:52 +0200 [thread overview]
Message-ID: <87ehnrqanr.fsf@gmail.com> (raw)
In-Reply-To: <CAOnWdogGgfh-7n3pVCXtohfSHTg2utAczYy9qaJ3MJopVc+wJQ@mail.gmail.com>
Juri Linkov <juri@jurta.org> writes:
>> 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.
`Man-getpage-in-background' use (if (fboundp 'start-process) to check if
it start an asynchronous process or not.
Why in Emacs-24 `start-process' would not exists?
Why instead don't you add an optional arg to `Man-getpage-in-background'
to make it synchronous?
It would be instead of (if (fboundp 'start-process):
(if synchronous start-man-synchronously start-man-async
This would allow to make an user variable that allow to choose if man is
async or not.
It is simple and change nothing to actual code.
>> 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.
>
>
>
>
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2012-08-01 8:27 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 ` bug#12098: How to trap errors in man? Juri Linkov
2012-08-01 0:38 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ehnrqanr.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=12098@debbugs.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.