-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
termopen()
ignores on_stderr
channel and bumps everything in stdout
#23660
Comments
It's mentioned in docs that with
And |
Oh I've missed that! Thanks. As for the escape sequences there is a similar explanation? |
Support of this is planned although the API is gonna look a bit different:
|
Problem
I was making a PR for a code runner plugin. The main objective was to implement error handling via quickfix or diagnostics.
For running the commands we use the
termopen()
function, to make possible to handle running/testing even TUI or something that requires input from the user. Reading the docs I saw thattermopen
supports the same arguments asjobstart
, so I tryied to implement something but I kept getting the errors only from stdout and all the coloured output had the color escape sequences still on it. Comparing tojobstart
is another level of user experience.Steps to reproduce
assuming this minimal C file:
testing functions with following code:
Steps
nvim --clean /tmp/nvim_bug_report/lua/test.lua
:so
:messages
at the bottom should be a report of how the cmd went.
Expected behavior
The behaviour I expect is the same I have with
jobstart
.Termopen
JobStart
Neovim version (nvim -v)
v0.9.0 Release
Vim (not Nvim) behaves the same?
no, doesn't seem to have the same function
Operating system/version
macOS 13.3.1
Terminal name/version
kitty 0.28.1
$TERM environment variable
xterm-kitty
Installation
homebrew
The text was updated successfully, but these errors were encountered: