> (I do use less, FWIW).
FWIW, I do use less more as well, but I also use more, tho less so.
Stefan
On Wed, Oct 16, 2024 at 03:45:44PM +0100, Chris Green wrote:
> On Wed, Oct 16, 2024 at 10:26:33AM -0400, Dan Ritter wrote:
> > Chris Green wrote:
> > >
> > > Hasn't the whole linus/unix world moved to using less instead or more?
> >
> > If it continues to build and work, there's no reason to dis
On Wed, 16 Oct 2024 16:49:20 -0400
Jeffrey Walton wrote:
> > Some people have habits ingrained over 40 years, more or less.
>
> This could be the next big emacs vs vi religious debate.
More or less.
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.c
On Wed, Oct 16, 2024 at 3:20 PM Dan Ritter wrote:
>
> Chris Green wrote:
> >
> > Hasn't the whole linus/unix world moved to using less instead or more?
>
> If it continues to build and work, there's no reason to discard
> it.
>
> Some people have habits ingrained over 40 years, more or less.
This
Hi all,
Am 16.10.2024 um 16:45 schrieb Chris Green:
On Wed, Oct 16, 2024 at 10:26:33AM -0400, Dan Ritter wrote:
Chris Green wrote:
Hasn't the whole linus/unix world moved to using less instead or more?
If it continues to build and work, there's no reason to discard
it.
Some people have hab
On Wed 16 Oct 2024 at 10:38:53 (-0400), Greg Wooledge wrote:
> On Wed, Oct 16, 2024 at 15:14:20 +0100, Chris Green wrote:
> > Greg Wooledge wrote:
> > > On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote:
> > > > Exporting MORE set to some unknown option (I did MORE=-q) leads to
> > >
On Wed, Oct 16, 2024 at 10:26:33AM -0400, Dan Ritter wrote:
> Chris Green wrote:
> >
> > Hasn't the whole linus/unix world moved to using less instead or more?
>
> If it continues to build and work, there's no reason to discard
> it.
>
> Some people have habits ingrained over 40 years, more or
Chris Green wrote:
>
> Hasn't the whole linus/unix world moved to using less instead or more?
If it continues to build and work, there's no reason to discard
it.
Some people have habits ingrained over 40 years, more or less.
-dsr-
On Wed, Oct 16, 2024 at 15:14:20 +0100, Chris Green wrote:
> Greg Wooledge wrote:
> > On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote:
> > > Exporting MORE set to some unknown option (I did MORE=-q) leads to
> > > more complaining and refusing service (so it seems to behave as if
>
Greg Wooledge wrote:
> On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote:
> > Exporting MORE set to some unknown option (I did MORE=-q) leads to
> > more complaining and refusing service (so it seems to behave as if
> > one passed that option directly in the command line).
>
> D'oh!
Greg Wooledge (12024-10-16):
> I still think that *conditionally* exporting MORE=-e (after performing
> whatever version-number-checking backflips are needed)
Do not check the version number, check if the option is supported:
if more -e /dev/null; then
MORE=-e
export MORE
fi
Regards,
--
On Wed, Oct 16, 2024 at 09:54:32AM -0400, Greg Wooledge wrote:
> On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote:
> > Exporting MORE set to some unknown option (I did MORE=-q) leads to
> > more complaining and refusing service (so it seems to behave as if
> > one passed that option d
On Wed, Oct 16, 2024 at 15:48:07 +0200, to...@tuxteam.de wrote:
> Exporting MORE set to some unknown option (I did MORE=-q) leads to
> more complaining and refusing service (so it seems to behave as if
> one passed that option directly in the command line).
D'oh!
What a disaster. OK, now I have
On Wed, Oct 16, 2024 at 09:41:41AM -0400, Greg Wooledge wrote:
> On Wed, Oct 16, 2024 at 15:34:51 +0300, Anssi Saari wrote:
> > $ ls|more -e
> > more: unknown option -e
> > Try 'more --help' for more information.
> >
> > I included the reason in my post by listing the Linux environments I use
> >
On Wed, Oct 16, 2024 at 15:34:51 +0300, Anssi Saari wrote:
> $ ls|more -e
> more: unknown option -e
> Try 'more --help' for more information.
>
> I included the reason in my post by listing the Linux environments I use
> and where I expect this to work. Interestingly the man page for more in
> Deb
Greg Wooledge writes:
> Why did you make it so complicated? What's wrong with simply:
>
> alias l='ls -lF|more -e'
>
> or perhaps:
>
> export MORE=-e
> alias l='ls -lF|more'
$ ls|more -e
more: unknown option -e
Try 'more --help' for more information.
I included the reason in my pos
Jeffrey Walton wrote:
> On Tue, Oct 15, 2024 at 3:40 AM Todd Zullinger wrote:
>> For additional (and _possibly_ interesting) context, this
>> isn't a Debian-specific change. It's part of the upstream
>> util-linux-2.38 release¹. It was submitted to the
>> util-linux mailing list in 2021² and ref
On Tue, Oct 15, 2024 at 3:40 AM Todd Zullinger wrote:
>
> Jim Anderson wrote:
> > I'm not sure why the Debian developers chose to change the
> > behavior of the 'more' command, but the Debian release 12
> > has the annoying habit, upon reaching end of the file, of
> > displaying extra empty lines
On 15/10/2024 11:06, Todd Zullinger wrote:
For additional (and _possibly_ interesting) context, this
isn't a Debian-specific change. It's part of the upstream
util-linux-2.38 release¹. It was submitted to the
util-linux mailing list in 2021² and referenced the POSIX
specification as the ration
On Tue, Oct 15, 2024 at 16:01:41 +0300, Anssi Saari wrote:
> For decades, I've had an alias like this:
>
> alias l="ls -lF|more"
>
> Convenient, no pager unless the directory listing is long. And now it's
> become this code:
>
> more_version=$(more --version|awk '{print $4}'|cut -d. -f1-2)
> if
Jim Anderson writes:
> One time usage is not bad, but if you use 'more' often, as I do, this
> behavior is a repeating waste of time. I hope the developers will
> revert to the traditional behavior.
I doubt that but who knows.
For decades, I've had an alias like this:
alias l="ls -lF|more"
C
Jim Anderson wrote:
> I'm not sure why the Debian developers chose to change the
> behavior of the 'more' command, but the Debian release 12
> has the annoying habit, upon reaching end of the file, of
> displaying extra empty lines to fill a terminal window,
> then inserting the text:
>
> (END)
On Mon, Oct 14, 2024 at 15:09:48 -0500, David Wright wrote:
> On Mon 14 Oct 2024 at 14:38:36 (-0400), Jim Anderson wrote:
> > I'm not sure why the Debian developers chose to change the behavior of
> > the 'more' command, but the Debian release 12 has the annoying habit,
> > upon reaching end of the
On Mon 14 Oct 2024 at 14:38:36 (-0400), Jim Anderson wrote:
>
> I'm not sure why the Debian developers chose to change the behavior of
> the 'more' command, but the Debian release 12 has the annoying habit,
> upon reaching end of the file, of displaying extra empty lines to fill
> a terminal windo
I'm not sure why the Debian developers chose to change the behavior of
the 'more' command, but the Debian release 12 has the annoying habit,
upon reaching end of the file, of displaying extra empty lines to fill a
terminal window, then inserting the text:
(END)
at the end of file. This re
25 matches
Mail list logo
