Skip to main content
18 events
when toggle format what by license comment
Jul 2 at 23:47 vote accept user22476690
Jul 2 at 19:03 history edited D. Ben Knoble CC BY-SA 4.0
added 143 characters in body; edited tags
Jul 2 at 15:35 answer added romainl timeline score: 1
Jul 2 at 1:06 comment added user22476690 @D.BenKnoble I'm using kitty. On the other hand, I had set my TERM to xterm-256color, I guess for some compatibility reasons? Perhaps that may be related.
Jul 1 at 21:10 history edited Friedrich CC BY-SA 4.0
Actually, I like the sound of "Runnunf"
Jul 1 at 20:28 history edited D. Ben Knoble CC BY-SA 4.0
added 13 characters in body; edited title
Jul 1 at 20:26 comment added D. Ben Knoble The problem probably comes from the terminal emulator terminfo entry. I don’t have this problem either. What terminal are you using?
Jul 1 at 14:30 comment added romainl @Friedrich done, thank you.
Jul 1 at 11:39 comment added user22476690 @Friedrich I'm convinced that my behaviour is explained by this section of the gist ... The results are printed in the shell and clog our terminal's scroll buffer. .... This explains that the behaviour only manifests when grep output is more than a screenful. It would be unsurprisingly either if this exposed some problem in my scrollback config since I almost never use the scrollback, relying on vim's terminal scrollback.
Jul 1 at 10:47 comment added Friedrich I don't think it is ... pressing enter should make it go away. AFAIK, you can provoke this behavior e.g. by misconfiguring grepprg (which isn't the case, here). Anyway, I'm glad I understood your question correctly and I have no idea what's causing it :-D
Jul 1 at 10:27 comment added user22476690 @Friedrich Yes, such a prompt appears, but even after dismissing the prompt with ENTER, the rest of my screen is cluttered with the garbled output of grep. This is explained by the section from romainl.
Jul 1 at 10:13 comment added Friedrich By default, Vim prints grep's output with "Press ENTER or type command to continue" on the bottom. That's the expected (default) behavior and pressing enter should make the output disappear. Does it? If yes, I simply misread your question.
Jul 1 at 9:01 comment added user22476690 @romainl I think your gist explains why this is happening. This bit of your gist ... is the fact that Vim executes the command in Vim's parent shell. This has a few consequences ... seems to explain the issue. Your gist even provides a solution; it should be the answer.
Jul 1 at 7:51 comment added romainl Check out this gist.
Jul 1 at 6:20 history edited user22476690 CC BY-SA 4.0
added 213 characters in body
Jul 1 at 6:13 comment added Friedrich Funny. I cannot reproduce. Can you include the output of :version as well? What distro are you on? You mention something about "too much output"; how much is too much?
Jul 1 at 6:00 history edited user22476690 CC BY-SA 4.0
added 68 characters in body
Jul 1 at 5:16 history asked user22476690 CC BY-SA 4.0