From: Van Ly via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eliz@gnu.org, 73656@debbugs.gnu.org
Subject: bug#73656: 30.0.91; icomplete-vertical has no matches for M-x man RET chdir
Date: Fri, 25 Oct 2024 05:34:28 +0000 [thread overview]
Message-ID: <dcs1q04g2zf.fsf@SDF.ORG> (raw)
In-Reply-To: <jwvjze25h8b.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 20 Oct 2024 22:26:19 -0400)
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> + (if (eq system-type 'berkeley-unix) "-l")
>
As gap filler, the following change does not misbehave on deb or netbsd.
+ (if (eq system-type 'berkeley-unix) "-l" "")
> Maybe a more robust approach would be something like
>
> (defvar man--apropos-args (...))
>
> where (...) is a piece of code which actually runs `man` with `-k` and
> with or without `-l` to try and determine which kind of `man` we're
> dealing with, but without making assumptions about which kind of `man`
> is installed on which kind of OS.
>
As probe to reveal switches available to "man", try "man -h" and
"man -?" but the output doesn't look helpful, perhaps a complete
solution has to probe the manpage for "man".
. net$ man -h
. man -h
. Usage: man [-acw|-h] [-C cfg] [-M path] [-m path] [-S srch] [[-s] sect] name ...
. Usage: man [-C file] -f command ...
. Usage: man [-C file] -k keyword ...
. Usage: man -p
. net$ man -?
. man -?
. man: unknown option -- ?
. Usage: man [-acw|-h] [-C cfg] [-M path] [-m path] [-S srch] [[-s] sect] name ...
. Usage: man [-C file] -f command ...
. Usage: man [-C file] -k keyword ...
. Usage: man -p
. deb$ man -h
. Usage: man [OPTION...] [SECTION] PAGE...
.
. -C, --config-file=FILE use this user configuration file
. -d, --debug emit debugging messages
. -D, --default reset all options to their default values
. --warnings[=WARNINGS] enable warnings from groff
.
. Main modes of operation:
. -f, --whatis equivalent to whatis
. -k, --apropos equivalent to apropos
. -K, --global-apropos search for text in all pages
. -l, --local-file interpret PAGE argument(s) as local filename(s)
. -w, --where, --path, --location
. print physical location of man page(s)
. -W, --where-cat, --location-cat
. print physical location of cat file(s)
.
. -c, --catman used by catman to reformat out of date cat pages
. -R, --recode=ENCODING output source page encoded in ENCODING
.
. Finding manual pages:
. -L, --locale=LOCALE define the locale for this particular man search
. -m, --systems=SYSTEM use manual pages from other systems
. -M, --manpath=PATH set search path for manual pages to PATH
.
. -S, -s, --sections=LIST use colon separated section list
.
. -e, --extension=EXTENSION limit search to extension type EXTENSION
.
. -i, --ignore-case look for pages case-insensitively (default)
. -I, --match-case look for pages case-sensitively
.
. --regex show all pages matching regex
. --wildcard show all pages matching wildcard
.
. --names-only make --regex and --wildcard match page names only,
. not descriptions
.
. -a, --all find all matching manual pages
. -u, --update force a cache consistency check
.
. --no-subpages don't try subpages, e.g. 'man foo bar' => 'man
. foo-bar'
.
. Controlling formatted output:
. -P, --pager=PAGER use program PAGER to display output
. -r, --prompt=STRING provide the `less' pager with a prompt
.
. -7, --ascii display ASCII translation of certain latin1 chars
. -E, --encoding=ENCODING use selected output encoding
. --no-hyphenation, --nh turn off hyphenation
. --no-justification, --nj turn off justification
. -p, --preprocessor=STRING STRING indicates which preprocessors to run:
. e - [n]eqn, p - pic, t - tbl,
. g - grap, r - refer, v - vgrind
.
. -t, --troff use groff to format pages
. -T, --troff-device[=DEVICE] use groff with selected device
.
. -H, --html[=BROWSER] use www-browser or BROWSER to display HTML output
. -X, --gxditview[=RESOLUTION] use groff and display through gxditview
. (X11):
. -X = -TX75, -X100 = -TX100, -X100-12 = -TX100-12
. -Z, --ditroff use groff and force it to produce ditroff
.
. -?, --help give this help list
. --usage give a short usage message
. -V, --version print program version
.
. Mandatory or optional arguments to long options are also mandatory or optional
. for any corresponding short options.
.
. Report bugs to cjwatson@debian.org.
--
vl
next prev parent reply other threads:[~2024-10-25 5:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 12:38 bug#73656: 30.0.91; icomplete-vertical has no matches for M-x man RET chdir Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-06 13:33 ` Eli Zaretskii
2024-10-06 14:33 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-06 14:48 ` Eli Zaretskii
2024-10-06 13:35 ` Eli Zaretskii
2024-10-06 14:54 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-06 16:10 ` Eli Zaretskii
2024-10-09 12:43 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-13 12:09 ` Eli Zaretskii
2024-10-15 5:20 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-17 17:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-18 0:37 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-19 9:42 ` Eli Zaretskii
2024-10-20 15:06 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-20 15:50 ` Eli Zaretskii
2024-10-21 2:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-22 9:31 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-25 5:34 ` Van Ly via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-10-31 18:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=dcs1q04g2zf.fsf@SDF.ORG \
--to=bug-gnu-emacs@gnu.org \
--cc=73656@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=van.ly@SDF.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).