From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 12098@debbugs.gnu.org
Subject: bug#12098: How to trap errors in man?
Date: Thu, 02 Aug 2012 07:20:28 +0200 [thread overview]
Message-ID: <87obmtkgyr.fsf@gmail.com> (raw)
In-Reply-To: <87ehnqb4i9.fsf@mail.jurta.org> (Juri Linkov's message of "Thu, 02 Aug 2012 02:12:05 +0300")
Juri Linkov <juri@jurta.org> writes:
>> Also `Man-notify-method' should be more accessible (more let-bindable)
>> probably by making it local, but I may be wrong there (need to look at
>> the code).
>
> This will be possible when you let-bind both `Man-notify-method'
> and `Man-async':
>
> (let ((Man-async nil) (Man-notify-method 'pushy)) (man "bash"))
Ok thanks.
>> Also while you are at it, it would be helpful to add a 't' value to the
>> require-match arg of completing-read in `man'.
>
> But what if `man' is unable to get a complete list of all available man pages?
> Then you can't read some man pages. For instance, this happens when
> you install a new package with a man page, but Man-completion-cache
> is not updated. This is a very rare problem, and you can still
> read the man page by entering its name without completion.
It would be better in this case to reload the cache e.g with a prefix
arg do (setq Man-completion-cache nil) before calling completing-read.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
prev parent reply other threads:[~2012-08-02 5:20 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
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 [this message]
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=87obmtkgyr.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=12098@debbugs.gnu.org \
--cc=juri@jurta.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).