unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Christopher Yeleighton <giecrilj@stegny.2a.pl>
Cc: manuel@ledu-giraud.fr, 68583@debbugs.gnu.org
Subject: bug#68583: 29.1; Can't find the cat manpage
Date: Fri, 19 Jan 2024 16:32:26 +0200	[thread overview]
Message-ID: <83wms5v1fp.fsf@gnu.org> (raw)
In-Reply-To: <8960a0d7-a661-4158-a98d-83b2c8d1afd4@stegny.2a.pl> (message from Christopher Yeleighton on Fri, 19 Jan 2024 12:46:57 +0000)

> Date: Fri, 19 Jan 2024 12:46:57 +0000
> Cc: manuel@ledu-giraud.fr, 68583@debbugs.gnu.org
> From: Christopher Yeleighton <giecrilj@stegny.2a.pl>
> 
> If the code in man.el tried to find the manual page by itself, it would 
> not fail because the manual page is there. It succeeds if MANOPT is not 
> set and my MANOPT should not affect the manual page search algorithm.

That depends on how we try to find the manual page(s).  The
implementation calls 'man' in a special way, which evidently fails
under the value of MANOPT you set.





  reply	other threads:[~2024-01-19 14:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 10:06 bug#68583: 29.1; Can't find the cat manpage Christopher Yeleighton
2024-01-19 10:28 ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 10:31   ` Christopher Yeleighton
2024-01-19 10:40     ` Manuel Giraud via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-19 10:44       ` Christopher Yeleighton
2024-01-19 12:01         ` Eli Zaretskii
2024-01-19 12:05           ` Christopher Yeleighton
2024-01-19 12:06             ` Eli Zaretskii
2024-01-19 12:17               ` Christopher Yeleighton
2024-01-19 12:41                 ` Eli Zaretskii
2024-01-19 12:46                   ` Christopher Yeleighton
2024-01-19 14:32                     ` Eli Zaretskii [this message]
2024-01-19 15:18                       ` Christopher Yeleighton
2024-01-19 15:21                       ` Christopher Yeleighton

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=83wms5v1fp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68583@debbugs.gnu.org \
    --cc=giecrilj@stegny.2a.pl \
    --cc=manuel@ledu-giraud.fr \
    /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).