Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Comments on Continuously read from piped input using Vim

Parent

Continuously read from piped input using Vim

+6
−0

In Vim, it's possible to tell it to read from stdin instead of a file, by using vim -. This is so that you can pipe the output of one command into Vim, to view/edit it there.

The problem I'm facing is that Vim seems to wait until the pipe is closed before starting up and displaying anything. It sits there saying Vim: Reading from stdin... until the piped command terminates. This can be a very long time, depending on the command!

Is there any way I can get Vim to instead start displaying immediately, and autoread as more data comes from the pipe?

My use case is trying to use Vim as a pager, so that I can have custom syntax highlighting and folding, for Git logs. My current attempts are failing because Vim waits until the entire log has been loaded before displaying anything at all.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

2 comment threads

Limit the log? (1 comment)
I don't think it's possible, but if it is, less.vim might do it (1 comment)
Post
+0
−2

Maybe passing the piped results through tail first would partially work. Use tail with the -f flag so that tail will continuously its contents. Example: <cmd> | tail -f | vim -

I think you would still need to tell vim to get updates from tail periodically with :e!

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

That won't work. `tail -f` is just another continuously outputting command; From Vim's perspective it... (1 comment)
That won't work. `tail -f` is just another continuously outputting command; From Vim's perspective it...
Quasímodo‭ wrote almost 3 years ago

That won't work. tail -f is just another continuously outputting command; From Vim's perspective it is none the better.