From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: getting a modern `more`
Date: Fri, 13 Jan 2012 21:17:41 -0600 [thread overview]
Message-ID: <4F10F3D5.9080706@gmail.com> (raw)
In-Reply-To: <201201132008.20863.vapier@gentoo.org>
Mike Frysinger wrote:
> On Friday 13 January 2012 19:22:15 Bruce Dubbs wrote:
>> "COMPATIBILITY WITH MORE
>> If the environment variable LESS_IS_MORE is set to 1, or if the
>> program is invoked via a file link named "more", less behaves
>> (mostly) in conformance with the POSIX "more" command
>> specification."
>
> you've indirectly quoted one reason for needing "more" -- POSIX wants it.
> http://pubs.opengroup.org/onlinepubs/9699919799/utilities/more.html
I guess my intent wasn't clear. I wasn't advocating removing "more"
from distros, I was saying that it's implementation via "less" is much
more flexible and wasn't really required in util-linux.
I suppose the case can be made that 'more' at about 27K is much smaller
and more efficient than 'less' at about 327K, but in the era of TB
drives, I wouldn't think that would make a significant difference. Both
programs are generally used by users at the command line - rarely in a
script.
That said, if you want to spend the effort to update and maintain a
program that duplicates functionality, than that's up to you. I just
think you may want to be careful of NIH thinking.
-- Bruce
next prev parent reply other threads:[~2012-01-14 3:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201201130128.49700.vapier@gentoo.org>
2012-01-13 23:12 ` getting a modern `more` Bruce Dubbs
2012-01-14 0:01 ` Sami Kerola
2012-01-14 0:22 ` Bruce Dubbs
2012-01-14 1:08 ` Mike Frysinger
2012-01-14 3:17 ` Bruce Dubbs [this message]
2012-01-14 5:39 ` Mike Frysinger
2012-01-14 17:30 ` Bruce Dubbs
2012-01-14 21:26 ` Mike Frysinger
2012-01-14 22:19 ` Bruce Dubbs
2012-01-14 22:35 ` Mike Frysinger
2012-01-14 22:47 ` Bruce Dubbs
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=4F10F3D5.9080706@gmail.com \
--to=bruce.dubbs@gmail.com \
--cc=util-linux@vger.kernel.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.
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).