-
-
Notifications
You must be signed in to change notification settings - Fork 117
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
Feature request: integrate close when tests succeed with vim-test
#123
Comments
tbh I didn't know |
Haha, that's funny since vim-test has some integration with neoterm. I'd like it if neoterm generalized to essentially being a "window manager" for terminals and letting other plugins actually control what goes in them. Neoterm could control things like opening/closing terminals, resizing them to fit the input/output, etc. |
@kassio @alok I agree, I think it would be a good if Neoterm was only a terminal manager, and leaves generating test commands to a separate plugin that is specialized only for that (vim-test). Because generating test commands is really a separate responsibility, since these commands can also be run using other "terminal managers", e.g. dispatch.vim. |
@kassio please don't remove the test status on status bar .. It's very useful in my workflow .. implement it on vim-test instead would be great though, |
@drselump14 I think this is a generic feature for any shell command, it just indicates whether the shell command is currently running, succeeded, or errored, so I imagine this feature will stay. |
@kassio good to hear that .. thanks
…On 01/13 05:44:53 PM, Janko Marohnić wrote:
@drselump14 I think this is a generic feature for any shell command, it just indicates whether the shell command is currently running, succeeded, or errored, so I imagine this feature will stay.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#123 (comment)
|
@drselump14 and @janko-m, actually, nowadays, it's not checking if the shell command succeeds or not, today it's parsing the shell command output. I really tried to use the command output status when I created this feature, but I wasn't able at the time to make it work. 😢 We can add this to vim-test later, but I think this would be better if it worked with any vim-test's strategies. |
I'm not sure which plugin to report this to, but when vim-test uses
neoterm
to run tests, neoterm does not close after tests succeed even if the following options are set:The text was updated successfully, but these errors were encountered: