From: Erwin Waterlander <waterlan@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Shouldn't 'man' depend on 'col'? Shouldn't 'col' be easier to find?
Date: Fri, 11 Jul 2014 07:30:00 -0000 [thread overview]
Message-ID: <53BF929D.1050904@xs4all.nl> (raw)
In-Reply-To: <53BE30C5.7080508@cygwin.com>
Op 10-7-2014 8:20 Yaakov Selkowitz schreef:
> On 2014-07-09 17:28, Keith Christian wrote:
>> There are other packages that require a bit of time post-install, such
>> as the texlive package. Having the man-db package update the DB
>> immediately after install sounds like a good idea, even if it takes a
>> few minutes.
>
> We're talking 20 minutes or more, which is IMO excessive.
>
>> Else, end users that aren't familiar with re-creating the DB may be
>> discouraged at not finding something in the man pages.
>>
>> That, or else use a non-blocking method of printing a message with the
>> DB creation command line.
>
> There is another issue: creating it during man-db's postinstall only
> helps for the manpages installed as of then; any pages added or
> updated afterwards won't get into the DB. There is a way we could
> handle that (similar to _update-info-dir), but only if DB generation
> is faster.
>
Isn't there an option that man-db grows a database cache while you are
using it. Such that a page is added to the cache the first time you read
a man page. Then you have a small extra delay only the first time.
Usually people read only a small percentage of the man pages frequently.
Caching all man pages is a bit excessive.
Man-db also displays non-cached man pages. What is the time difference
between loading a cached or a non-cached page on Cygwin? Perhaps it's
not worth caching.
regards,
--
Erwin Waterlander
http://waterlan.home.xs4all.nl/
--
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
next prev parent reply other threads:[~2014-07-11 7:30 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
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 [this message]
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=53BF929D.1050904@xs4all.nl \
--to=waterlan@xs4all.nl \
--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).