Page 1 of 2

list | more broken (?)

Posted: Wed Aug 31, 2011 12:47 pm
by Raziel
First of all...THANK YOU very much for the great update :-D
It feels faster, even more stable and it's just awesome to be able to install it without a complete new install. KUDOS!

Now for a simple misbehaviour i found.

list | more should list the files, stop when the shell's window bottom is reached and show the rest or next page when the user presses a key...

with update 3 none of this happens, instead the shell window is blanked and somehow "frozen"...i can move it around, resize, put to background, get it back to front and such but i cannot close it for my life :-)

It just stays there and probably waits for something ;-)

Anyone can reproduce that?
Is it a regression?
PIPE is in Devs:/DOSDrivers, but i assume there was a change in L:queue-handler which triggers this behaviour, no?

Thank you very much again
Oh...it worked in update 2

Re: list | more broken (?)

Posted: Wed Aug 31, 2011 2:04 pm
by abalaban
@Raziel

'xxx | more' always behave a bit strangely (IMHO, or at least compared to how someone used to the Unix feature would expect it to work). In practise I found myself using more and more the 'recorder' command line and then a 'more' or 'EditPad' on the result.
In the meantime this might be of some to you :?:

Re: list | more broken (?)

Posted: Wed Aug 31, 2011 2:12 pm
by Raziel
abalaban wrote:@Raziel

'xxx | more' always behave a bit strangely (IMHO, or at least compared to how someone used to the Unix feature would expect it to work). In practise I found myself using more and more the 'recorder' command line and then a 'more' or 'EditPad' on the result.
In the meantime this might be of some to you :?:
I need to try that recorder thingie :-)

Normally on large texts i do a list xxx >ram:xxx.txt and then read it with all the time i have ;-)

...still, this command shouldn't lock up the shell, should it? :-)

Re: list | more broken (?)

Posted: Wed Aug 31, 2011 2:19 pm
by abalaban
Raziel wrote:I need to try that recorder thingie :-)

Normally on large texts i do a list xxx >ram:xxx.txt and then read it with all the time i have ;-)
Advantage of using recorder is that it does not prevent the shell output contrary to a simple file redirection. So you know in real-time (or quasi) what is going on unlike with a redirection.
Raziel wrote:...still, this command shouldn't lock up the shell, should it? :-)
Yes I agree

Re: list | more broken (?)

Posted: Wed Aug 31, 2011 4:41 pm
by Hypex
I can confirm here. It blanks my shell. How strange. :-)

Re: list | more broken (?)

Posted: Wed Aug 31, 2011 10:33 pm
by nbache
Raziel wrote:...still, this command shouldn't lock up the shell, should it? :-)
It doesn't. Press Ctrl-C and then q, and you will get your prompt back.

Still, weird behaviour. I'll try experimenting a bit more ;-) here.

Best regards,

Niels

Re: list | more broken (?)

Posted: Thu Sep 01, 2011 1:12 am
by tonyw
None of the Shell/con-handler/console group has changed since Update 2, so it must be something else causing it.

Re: list | more broken (?)

Posted: Thu Sep 01, 2011 2:55 am
by xenic
Raziel wrote: PIPE is in Devs:/DOSDrivers, but i assume there was a change in L:queue-handler which triggers this behaviour, no?
I don't think so. I just replaced the Update3 more command with the Update2 more command and that works. It looks like someone botched an update of the more command :-)

Re: list | more broken (?)

Posted: Thu Sep 01, 2011 11:51 am
by Raziel
@nbache

ah, thank for that :-)
I gotta really try to dig out my old amiga knowledge ;-)

@xenic

damn, the nearest solution :-D
good catch, thanks...do you also know who is responsible for the more command?
...and ask him to fix it ;-)

Hihi, i like the update :-D

Re: list | more broken (?)

Posted: Thu Sep 01, 2011 12:01 pm
by broadblues
It seams to be a probablem with more and reading from a pipe as:

list >PIPE:mypipe
more <PIPE:mypipe

fails in a similar way, once you hit ctrl-c you et a warning that the file might be binary.