On "Re: And something about less" [EMAIL PROTECTED] said on Apr 27:
> Not unable. Just unwilling. Once less has reached an end of file, that
> is it. Refreshing the screen doesn't get any more stuff to put on it,
> It isn't the screen that is stale, but less's knowledge of the file.
> If you want less to not believe an end of file and keep closing and
> reopening the file to see if it has changed, give it the F
> command. Then you do not need to efresh the screen.
It's strange that unwillingness. I mean it can reach the EOF
when the file is non-zero lenght. And it will work just fine.
I nerver tested this with the "f" command. But I don't really
like that. That way I get a bigger and slower "tail -f". I need that
flexibility less offers. I mean I browse, I reread the file with ^R,
than browse again. It's neat and it's extremely fast - the way I like
it.
I just feel bad because I was hoping less doesn't have any
problems after all that development. Guess I was wrong.
Raider
--
``Liberate tu-temet ex inferis''
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
