public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Shouldn't 'man' depend on 'col'? Shouldn't 'col' be easier to find?
Date: Tue, 08 Jul 2014 16:15:00 -0000	[thread overview]
Message-ID: <53BC191A.5020606@gmail.com> (raw)
In-Reply-To: <CAJqfdW6bCQ4PLnSO2o6a1gd-veLogad9he9TcddZzk9sw8Jr-w@mail.gmail.com>


On 08/07/2014 17:47, Jack Duthen wrote:
> Problem #1:
> ----------
> After I loaded a few cygwin packages, I got this:
>
> $ man bash | wc
> man: can't execute col: No such file or directory
>
> The "man" command works perfectly when the stdout is NOT redirected,
> but, when sent to a pipe or a file, the command "man" fails with the
> above message.
>
> Question #1:
> Shouldn't the 'man' function/package depend on the 'col' function/package?
>
> Problem #2
> ----------
> To solve my 'man' problem,I tried to find the 'col' command.
>
> I launched the standard interface (setup.exe) and entered 'col' in the
> 'Search' text field.
>
> It gave me a list of packages, mainly related to 'colamd', 'colorgc',
> 'protocol' stuff, 'colored' stuff, 'texlive-collection' stuff,
> 'colordiff'...
>
> but no clear link to the missing 'col.exe'.

wrong way. Setup search only package names, not their content

Best with
https://cygwin.com/packages/
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=col.exe&arch=x86

also with
$ cygcheck -p col.exe
Found 4 matches for col.exe
netpbm-10.61.02-1 - Toolkit for manipulation of graphic images
netpbm-debuginfo-10.61.02-1 - Debug information for Toolkit for 
manipulation of graphic images
util-linux-2.21.2-1 - Random collection of Linux utilities
util-linux-debuginfo-2.21.2-1 - Debug information for Random collection 
of Linux utilities

of course "col" is too short to be meaningful, "col.exe"
is a better catch.

> Question #3
> To get a 'man' that works when piped, is there a better way than
> loading this "random" collection of utilities?
>
> Am I the only one to get that problem???

util-linux is a popular package, so the issue was not yet noticed.

man was recently changed, so this dependency was likely missed,
specially as it seems hidden inside the man binary.

> )jack(
Marco



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-07-08 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08 15:47 Jack Duthen
2014-07-08 16:15 ` Marco Atzeri [this message]
2014-07-08 23:01   ` Chris J. Breisch
2014-07-09  0:16     ` Yaakov Selkowitz
2014-07-09  0:30       ` Chris J. Breisch
2014-07-09 22:28         ` Keith Christian
2014-07-10  6:21           ` Yaakov Selkowitz
2014-07-11  7:30             ` Erwin Waterlander
2014-07-11  9:35               ` Andrey Repin

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=53BC191A.5020606@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.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.
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).