unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: jidanni@jidanni.org
To: cyd@stupidchicken.com, man-db@packages.debian.org
Cc: rfrancoise@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 14:12:31 +0800	[thread overview]
Message-ID: <87tytkpcq8.fsf@jidanni.org> (raw)
In-Reply-To: <87tytkn1e3.fsf@jidanni.org>

>>>>> "CY" == Chong Yidong <cyd@stupidchicken.com> writes:
CY> jidanni@jidanni.org writes:

>> M-x man should consider $MANPATH when making completions. It (via
>> /usr/bin/man) finds the pages fine, but one must type them in without
>> any TAB completion help. The TAB completion should examine one's e.g.,
>> MANPATH=/usr/local/man:/home/jidanni/.spamassassin-tree/man: too.

CY> It does complete, using `man -k'.  Please provide a proper bug report.

$ 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...

Just like one can expand the names of $PATH, why not $MANPATH...






  parent reply	other threads:[~2010-02-14  6:12 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 [this message]
2010-02-14  8:57   ` Colin Watson
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=87tytkpcq8.fsf@jidanni.org \
    --to=jidanni@jidanni.org \
    --cc=5578@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --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).