From: Reuben Thomas via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: Juri Linkov <juri@jurta.org>, Lars Ingebrigtsen <larsi@gnus.org>,
12098@debbugs.gnu.org
Subject: bug#12098: How to trap errors in man?
Date: Wed, 19 Aug 2020 14:51:46 +0100 [thread overview]
Message-ID: <CAOnWdogjPoBTr4b-k-qsfTdvZ8+=wy7uiyKeR6NexyrqBQ+n=Q@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmn66t-=H8A3kJBz7KHsJbtv2WY2pgjtEGKdT_eA1YW8QA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
On Wed, 19 Aug 2020 at 14:51, Stefan Kangas <stefan@marxist.se> wrote:
> Reuben Thomas <rrt@sc3d.org> writes:
>
> > As I said earlier in the thread, this seems only to add complexity (for
> > example making it hard to reuse `man` for other things, the reason I
> filed
> > this issue originally) for no useful gain on modern machines (the delay
> > when formatting even the longest man page is short).
>
> What if you are running this remotely using TRAMP? What if you're on a
> laggy network with an NFS mounted filesystem? What if your disk is
> failing and this command takes several seconds to complete? etc.
>
No different from any other command that interacts with the disc and is
normally run synchronously.
--
https://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 1408 bytes --]
next prev parent reply other threads:[~2020-08-19 13:51 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOnWdogjPoBTr4b-k-qsfTdvZ8+=wy7uiyKeR6NexyrqBQ+n=Q@mail.gmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=12098@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=larsi@gnus.org \
--cc=rrt@sc3d.org \
--cc=stefan@marxist.se \
/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.