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

Add default Clojure associations for file extensions .bb and .cljd #1617

Closed
baibhavbista opened this issue Mar 24, 2022 · 4 comments · Fixed by #1618
Closed

Add default Clojure associations for file extensions .bb and .cljd #1617

baibhavbista opened this issue Mar 24, 2022 · 4 comments · Fixed by #1618
Labels

Comments

@baibhavbista
Copy link
Contributor

Does not support some extensions (.bb, .cljd) by default.

.bb is for Babashka files
.cljd is for ClojureDart files (currently under private beta, will be released pretty soon)

Workaround is to change the language association manually via the setting File: Association, or at-will with the command Change Language Mode.

Discussed here: https://clojurians.slack.com/archives/CBE668G4R/p1648009121586269

@PEZ
Copy link
Collaborator

PEZ commented Mar 24, 2022

Thanks for this issue! Maybe @borkdude knows of some more extension we could add as default?

@PEZ PEZ added the editing label Mar 24, 2022
@PEZ PEZ changed the title Does not support some extensions (.bb, .cljd) by default Add default Clojure associations for file extensions .bb and .cljd Mar 24, 2022
PEZ added a commit that referenced this issue Mar 24, 2022
@borkdude
Copy link

Other than .bb from my side there are no special extensions. Thanks!

@Cyrik
Copy link
Member

Cyrik commented Apr 5, 2022

This is now also added to lsp, so I'm closing the ticket

@Cyrik Cyrik closed this as completed Apr 5, 2022
@PEZ
Copy link
Collaborator

PEZ commented Apr 5, 2022

I should learn the resolving commit message syntax better. 😄

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

Successfully merging a pull request may close this issue.

4 participants