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

Flycheck is removed after every launch #3677

Closed
selfawaresoup opened this issue Nov 5, 2015 · 6 comments
Closed

Flycheck is removed after every launch #3677

selfawaresoup opened this issue Nov 5, 2015 · 6 comments
Labels
Bug :-( Core stale marked as a stale issue/pr (usually by a bot)

Comments

@selfawaresoup
Copy link

I have the flycheckpackage in my dotspacemacs-additional-packages but after launch, it is not installed. When I install it manually using package-install it works until the next relaunch and then it's gone again. My other packages are not affected by this.

This issue only started popping up recently, I don't know with which version exactly.

@syl20bnr
Copy link
Owner

syl20bnr commented Nov 5, 2015

Interesting behavior.
To know if a package is already supported in Spacemacs you can summon helm-spacemacs on SPC f e h and type flycheck. You'll that it belongs to the layer syntax-checking. So you can add this layer to your layer list.

I keep this opened because we have to fix the behavior you got when adding flycheck to additional packages.

@selfawaresoup
Copy link
Author

Thanks, adding the 'syntax-checking' layer helped. Flycheck is now installed after launch.

@robbyoconnor
Copy link
Contributor

That's definitely a problem -- but (this is my opinion solely), I think we should just not support this setup.

@syl20bnr
Copy link
Owner

syl20bnr commented Nov 5, 2015

@robbyoconnor it may be useful to allow it but we can add a warning about the existed layer that contains the same package.

@robbyoconnor
Copy link
Contributor

in that case, people should provide their own layer

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug :-( Core stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

3 participants