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

Option to exclude/disable vscode in dump #1456

Closed
JtMotoX opened this issue Sep 30, 2024 · 6 comments · Fixed by #1459
Closed

Option to exclude/disable vscode in dump #1456

JtMotoX opened this issue Sep 30, 2024 · 6 comments · Fixed by #1459
Assignees

Comments

@JtMotoX
Copy link

JtMotoX commented Sep 30, 2024

Would it be possible to have a brew bundle dump flag, something like --no-vscode to disable the vscode integration? I use vscode built-in sync functionality and this is causing some issues.

Currently, I have to perform sed -i '/^vscode /d' $HOME/Brewfile after every dump.

@jacobbednarz
Copy link
Member

today there isn't a way to selectively output some types over others. the assumption is that if you have it installed, you will want to manage it via brew bundle -- in your case, that isn't true.

i don't know how widely used this would be but open to leaving this here to gauge the interest and welcome a PR if you want to see this land.

@JtMotoX
Copy link
Author

JtMotoX commented Sep 30, 2024

This has been requested in #1209 and #1212 so there are others that are interested in this option.

@MikeMcQuaid
Copy link
Member

@JtMotoX would you prefer brew bundle dump --skip-vscode or something like export HOMEBREW_BUNDLE_NO_VSCODE=1?

@JtMotoX
Copy link
Author

JtMotoX commented Oct 1, 2024

--skip-vscode would be preferred

@JtMotoX
Copy link
Author

JtMotoX commented Oct 2, 2024

Works great! Thank you! 👍

@MikeMcQuaid
Copy link
Member

@JtMotoX you're welcome, thanks for taking the time to say thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants