Job `on_stdout` always waits for new line

Open
#619 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
tooling

Research direction

Start in lua/plenary/job.lua around the repeat statement at line 302, then compare its output handling with vim.uv.read_start. Trace how Job invokes on_stdout when output lacks a newline. Done means a command's same-line prompt can trigger on_stdout without waiting for a newline, with existing behavior preserved.

Written by the indexing model from the issue text.

Description

Is there a way of not waiting for the new line to have the on_stdout handler called? I couldn't find it and I assume it's related to this repeat statement.

My scenario is that I have a command that waits for the user to press return, but its output asking for it is in the same line. The regular vim.uv.read_start function handles that well, but I couldn't make it work with plenary.job.

Thanks in advance!

Dominant language
Lua
Stars
3.5k
Forks
340
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.