-
Notifications
You must be signed in to change notification settings - Fork 23
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
Snippets fails to expand #60
Comments
Hi Whatever method I use, snippets won't expand:
This even happens with the demo snippet. |
Check your hotkeys |
Same issue here. ctrl+tab has no bindings and space adds a space (after i checked setting on) |
Same issue here. I can't expand any snippets. |
if you are dependent on this plugin, use legacy editor until this is fixed. |
check bindings in "text-snippets-obsidian:text-snippets": [
{
"modifiers": [
"Mod"
],
"key": "Tab"
}
], Check whether any other action has got this binding |
Hi The binding was missing in the json. Thanks for your help |
The easiest thing for me was to change the hotkey of (text snipets: Run snippet replacement) from command + tab to anything else. Then it works. Thanks! |
Hey folks, came here to see if anyone else was having an issue. I'm running Obsidian v1.2.7 on Windows 11. I have the hotkey set for ctrl+tab, but it wasn't in the hotkeys.json file so I manually added it as per #60 (comment), restarted Obsidian, and it still doesn't work. Am I missing something? Because I have |
@shayaknyc : ctrl-tab won't work because that will switch tabs. Need to change the hotkeys. That said, doesn't work for me either. |
I managed to make it work with the manual shortcut (Ctrl + Shirt + R for me) but space and tab binding isn't working unless I go to legacy editor which will be deprecated. Is there a way to make those bindings work on non-legacy editor? Note: Even with tab disables in the editor settings the binding isn't working |
I'm running Obsidian v1.1.9 on Windows 11 with Snippets v0.12.
Snippets are not expanding and they just get selected. I tried turning off all the community plug-ins, and results in same outcome.
Anyone else having the same issue?
The text was updated successfully, but these errors were encountered: