Skip to content
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

Running foundation CLI in the integrated terminal #26462

Closed
eurolife opened this issue May 11, 2017 · 3 comments
Closed

Running foundation CLI in the integrated terminal #26462

eurolife opened this issue May 11, 2017 · 3 comments
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@eurolife
Copy link

I am getting a strange behavior when running 'foundation watch' and then 'foundation build' using the integrated terminal and foundation-cli. After running 'foundation watch' and then hitting Ctrl + C to quit the watch task, I then try to run 'foundation build' but instead of running that task, it keeps asking me 'Terminate batch job (y/n)?' The only way I can get it to work is if I quit VS code and restart it.

  • VSCode Version: 1.12.1
  • OS Version: Windows 7 Professional

Steps to Reproduce:

  1. Run a Foundation 6 project using the integrated terminal and foundation-cli, line command 'foundation watch'
  2. Then stop the watch task by hitting Ctrl + C and hitting Y.
  3. Try to run 'foundation build'. It then keeps asking 'Terminate batch job (y/n)?' instead of running the build task.
@egamma egamma added the info-needed Issue requires more information from poster label May 11, 2017
@egamma
Copy link
Member

egamma commented May 11, 2017

Can you please provide the steps for how to reproduce your setup, what do we have to install?
Can you illustrate the issue with an animated gif.

@eurolife
Copy link
Author

eurolife commented May 11, 2017

You need to have nodejs installed and then install foundation cli by following the steps here: https://github.com/zurb/foundation-cli

Here is a gif (hope it works, have not done this before).
vscode

@Tyriar
Copy link
Member

Tyriar commented May 12, 2017

There are some issues that are a little flaky around using ctrl+c in the terminal on Windows microsoft/node-pty#7

You shouldn't need to restart VS Code though, try killing the terminal (the bin icon in the panel) and creating a new one.

@Tyriar Tyriar closed this as completed May 12, 2017
@Tyriar Tyriar added *duplicate Issue identified as a duplicate of another issue(s) and removed info-needed Issue requires more information from poster labels May 12, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants