Only for the first time you press END though, it seems to scroll through the entire file, instead of just allocating for the end of the file, and showing that view. After pressing END once, sp seems to cache the file and jumping from HOME to END, and vice versa becomes fast (When Loading... stops). On less, G and SHIFT+G are basically instant, there's no scroll shown. I use these pagers for large logs, so often I'm starting at the end of the file, and then reading up. This seems to only happen when a file's being piped into the pager, as opposed to read directly, I think sp tries to read to the current end of the buffer, and shows that, instead of waiting until it sees an EOF. less doesn't seem to even let me jump to the end of the file until EOF exists.
Only for the first time you press END though, it seems to scroll through the entire file, instead of just allocating for the end of the file, and showing that view. After pressing END once, sp seems to cache the file and jumping from HOME to END, and vice versa becomes fast (When
Loading...stops). On less, G and SHIFT+G are basically instant, there's no scroll shown. I use these pagers for large logs, so often I'm starting at the end of the file, and then reading up. This seems to only happen when a file's being piped into the pager, as opposed to read directly, I think sp tries to read to the current end of the buffer, and shows that, instead of waiting until it sees an EOF. less doesn't seem to even let me jump to the end of the file until EOF exists.