From: Colin Watson <cjwatson@debian.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Ingo Schwarze <schwarze@usta.de>,
linux-man@vger.kernel.org, g.branden.robinson@gmail.com,
man-db-devel@nongnu.org
Subject: Re: Linux man-pages Makefile portability
Date: Mon, 25 Jul 2022 10:28:30 +0100 [thread overview]
Message-ID: <Yt5iPprqbVjiQRy6@riva.ucam.org> (raw)
In-Reply-To: <ff01b98c-563f-dfd3-4996-65ff5e5f44ce@gmail.com>
On Sun, Jul 24, 2022 at 01:09:23PM +0200, Alejandro Colomar (man-pages) wrote:
> [TO += Colin; CC += man-dv-devel@;
> there's a bug in man(1)'s autocomplete]
man-db doesn't ship its own autocomplete code at the moment. This is
probably shipped by some other package in your distribution, although I
don't know exactly what that would be (maybe bash-completion?).
--
Colin Watson (he/him) [cjwatson@debian.org]
next prev parent reply other threads:[~2022-07-25 9:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 17:52 Linux man-pages Makefile portability Alejandro Colomar
2022-06-19 21:06 ` Ingo Schwarze
2022-06-19 22:23 ` Alejandro Colomar
2022-06-20 13:49 ` Ingo Schwarze
2022-07-03 21:44 ` Alejandro Colomar
2022-07-21 14:17 ` Alejandro Colomar
2022-07-22 16:59 ` Ingo Schwarze
2022-07-22 17:37 ` Alejandro Colomar
2022-07-23 18:16 ` Ingo Schwarze
2022-07-24 11:09 ` Alejandro Colomar (man-pages)
2022-07-24 15:57 ` Ingo Schwarze
2022-07-24 17:29 ` Semantic man(7) markup (was: Linux man-pages Makefile portability) G. Branden Robinson
2022-07-24 21:26 ` Ingo Schwarze
2022-07-25 9:28 ` Colin Watson [this message]
2022-07-25 12:46 ` bash-completion doesn't support man subsections " Alejandro Colomar
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=Yt5iPprqbVjiQRy6@riva.ucam.org \
--to=cjwatson@debian.org \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=man-db-devel@nongnu.org \
--cc=schwarze@usta.de \
/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.
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 NNTP newsgroup(s).