From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: getting a modern `more`
Date: Fri, 13 Jan 2012 18:22:15 -0600 [thread overview]
Message-ID: <4F10CAB7.6060808@gmail.com> (raw)
In-Reply-To: <CAG27Bk0Z8Aij+Tj42pA447FN9+zTu94YEmNhe2eDPo=KW2oYeg@mail.gmail.com>
Sami Kerola wrote:
> On Sat, Jan 14, 2012 at 00:12, Bruce Dubbs <bruce.dubbs@gmail.com> wrote:
>> Does anyone still use 'more'? The only thing needed is a symlink to 'less':
>> http://www.greenwoodsoftware.com/less/
>
> I do.
>
>> Are there any distros that don't provide 'less' by default?
>>
>> What value added does 'more' provide?
>
> It does not clear screen when 'q' is pressed, which is the main reason
> I sometime choose to use more.
"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."
>> I'd think development time would be
>> better used elsewhere. To me, 'more' was developed in the era of paper
>> terminals (e.g. Teletype) and it is time to retire it.
>
> I appreciate highly when someone volunteers to maintain & develop
> something superficially old and obsolete. Earlier one might have said
> that why bother to make vi better now when emacs is so great, which
> lead eventually to vim. Who knows how much better more might be in
> future in comparison to less if people who like it have change of
> making it such.
You have a point here, but I would certainly suggest that the volunteer
start with the most robust current software. Of course there is nothing
wrong with reviewing the older code for missing features.
-- Bruce
next prev parent reply other threads:[~2012-01-14 0:22 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 [this message]
2012-01-14 1:08 ` Mike Frysinger
2012-01-14 3:17 ` Bruce Dubbs
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=4F10CAB7.6060808@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).