all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: "Trent W. Buck" <trentbuck@gmail.com>
Cc: 5347@debbugs.gnu.org
Subject: bug#5347: 23.1; M-x man: misreports absent man(1) as absent manpage.
Date: Mon, 11 Jan 2010 02:52:07 +0200	[thread overview]
Message-ID: <877hrpfmdt.fsf@mail.jurta.org> (raw)
In-Reply-To: <20100110235929.GA1956@Clio> (Trent W. Buck's message of "Mon, 11 Jan 2010 10:59:31 +1100")

>> Maybe it would be good enough to change
>>
>> 		(error "Can't find the %s manpage" args)
>> into
>> 		(error "Can't find the %s manpage or no man(1)" args)
>
> Yup, that'd be fine.

No, please don't change this.  A new error message is confusing.
It's not clear what "no man(1)" does mean.  The current message is good
for normal cases when the man executable and its filters are present
on the system.  Please either try to detect the fact that the man
executable is missing and display a separate error message, or leave
the current message unchanged.

-- 
Juri Linkov
http://www.jurta.org/emacs/






  reply	other threads:[~2010-01-11  0:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <83skaf8jgv.fsf@gnu.org>
2010-01-09 12:14 ` bug#5347: 23.1; M-x man: misreports absent man(1) as absent manpage trentbuck
2010-01-09 14:03   ` bug#5347: marked as done (23.1; M-x man: misreports absent man(1) as absent manpage.) Emacs bug Tracking System
2010-01-10  4:06   ` Emacs bug Tracking System
2010-01-10  3:05 ` bug#5347: 23.1; M-x man: misreports absent man(1) as absent manpage Trent W. Buck
     [not found]   ` <83pr5i8v07.fsf@gnu.org>
2010-01-10  4:30     ` Trent W. Buck
2010-01-10 17:48       ` Eli Zaretskii
2010-01-10 23:59         ` Trent W. Buck
2010-01-11  0:52           ` Juri Linkov [this message]
2010-01-11  5:34             ` Drew Adams

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=877hrpfmdt.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=5347@debbugs.gnu.org \
    --cc=trentbuck@gmail.com \
    /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.