From: Colin Watson <cjwatson@debian.org>
To: jidanni@jidanni.org
Cc: cyd@stupidchicken.com, rfrancoise@debian.org,
man-db@packages.debian.org, 5578@debbugs.gnu.org
Subject: bug#5578: 23.1.92; M-x man should consider $MANPATH when making completions
Date: Sun, 14 Feb 2010 08:57:23 +0000 [thread overview]
Message-ID: <20100214085721.GX4484@riva.ucam.org> (raw)
In-Reply-To: <87tytkpcq8.fsf@jidanni.org>
On Sun, Feb 14, 2010 at 02:12:31PM +0800, jidanni@jidanni.org wrote:
> $ man -w whoami
> /usr/share/man/man1/whoami.1.gz
> $ man -k whoami
> whoami (1) - print effective userid
> $ man -w sa-update
> /home/jidanni/.spamassassin-tree/man/man1/sa-update.1p
> $ man -k sa-update
> $
>
> Well, OK, but to change things, the user must probably fiddle with
> /etc/manpath.config and run roots cronjob, when all he wants to do is
> expand the names and not look at the definitions...
Not at all. Run mandb as your ordinary user and then 'man -k' will
work.
You may only care about the names, but if M-x man currently searches
definitions as well then that means a number of users have almost
certainly got used to that, and 'man -k' seems like a reasonable way to
do that kind of thing. Having to make sure the database is up to date
seems like a not unreasonable price to pay, given that user manual
hierarchies are comparatively rare.
--
Colin Watson [cjwatson@debian.org]
next prev parent reply other threads:[~2010-02-14 8:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 23:48 bug#5578: 23.1.92; M-x man should consider $MANPATH when making completions jidanni
2010-02-14 1:29 ` Chong Yidong
2010-02-14 6:12 ` jidanni
2010-02-14 8:57 ` Colin Watson [this message]
2010-02-14 16:30 ` Stefan Monnier
2010-02-15 8:41 ` Colin Watson
2010-02-14 21:06 ` jidanni
2010-02-15 8:45 ` Colin Watson
2010-02-15 14:47 ` jidanni
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=20100214085721.GX4484@riva.ucam.org \
--to=cjwatson@debian.org \
--cc=5578@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=jidanni@jidanni.org \
--cc=man-db@packages.debian.org \
--cc=rfrancoise@debian.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).