-
Notifications
You must be signed in to change notification settings - Fork 180
Missing support for .vue files #364
Comments
+1 |
+1 ;) |
Yes, it would be great! |
Adding the following to my keymap.cson did the trick
|
@joshuajohnson814 I added this, and worked well for html expanding, while failed for css in style tag, |
@joshuajohnson814 Thank you, that works in vue template tag, but now emmet also expands in script tag so when i type someFile.vue
|
This would be appreciated. For now I'm just using |
@joshuajohnson814 thanks, man. That works for me! |
When using @joshuajohnson814 solution with a
So I guess that Emmet is interpreting the whole document as Does that makes sense @sergeche? |
It didn't work well with using your method, neither |
Working on a new Emmet implementation, will fix that in new version |
@joshuajohnson814 Thank you! |
Any news on this :)? I am waaaaay too used to using |
language-vue-component. Adds syntax highlighting to Vue Component files in Atom. |
Check out upcoming new Atom plugin with Emmet 2 onboard, seems like Vue works fine there: https://github.com/emmetio/atom-plugin |
Very good! |
Is it possible to get the fuzzy search and tab to expand? |
@daphen The behaviour of tab expander (including expanding without completions) will be tuned later. There could be problems for users who don’t want to expand Emmet but insert tab instead |
@sergeche I see, cool, and it's not possible to set that up manually right away? |
@daphen not yet, sorry. Still no dedicated command to expand abbreviation by handle, only via autocomplete popup |
@sergeche Alright, do you have an EST? Ballpark? |
@daphen not yet, doing this project on my spare time, very busy at my job |
@sergeche Ah, I see. Best of luck then. |
For me replacing .source.vue with .text.html.vue (in snippets.cson file) did the trick |
Please add support for .vue files
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28747938-missing-support-for-vue-files?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F535900&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: