Fork me on GitHub
#vim
<
2020-06-24
>
Chase15:06:00

Not sure if this is a vim or fireplace thing but say I open a big file with slurp it takes me to a buffer and at the bottom it says -- More -- I can't escape out of this. C-c does nothing. C-d gives me a small menu option, including q: quit but that does nothing either. I have to just keep pressing enter for more until it's done. What am I doing wrong here?

dominicm16:06:30

@chase-lambert See :help more-prompt

dominicm16:06:46

You could :set nomore

dominicm16:06:56

which I find to be a funny option name 😁

😄 3
dominicm16:06:13

Hmm, q maybe doesn't work anymore due to streaming? It did at some point

dominicm16:06:25

G works too, which is something I use often.

dominicm16:06:02

Apparently <C-Y> will do something to yank it, interesting, gotta try that one

Chase16:06:56

Ahh, G of course. That will work fine. Thank you!

noisesmith17:06:31

haha wow - after years at the command line, it baffled me to see that someone wouldn't know what to do at a -- More -- prompt

noisesmith17:06:45

but of course if you've never seen one, it's totally bizarre

noisesmith17:06:25

(back in the day, less didn't exist, and the more pager only accepted space / G / etc. and didn't understand arrow keys)

noisesmith17:06:35

it also couldn't scroll up lol

parrot 3
Chase17:06:53

And I use G all the time, even in the browser with vimium. lol

noisesmith17:06:10

also space scrolls a page, even in a browser

Chase17:06:01

It still seems inefficient to send the cursor all the way to the bottom to let me exit instead of having q work

dominicm17:06:39

q is supposed to work, I suspect there's something else at play.

👍 3