You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use the Vintageous plugin and the ColdFusion(development branch) plugin. I frequently use > in visual mode of Vintageous to indent blocks of text. Since installing ST3 I have had trouble getting this to work. Instead of indenting it inserts a ">" at the end of the selection. Looks like the ColdFusion plugin also uses the > key for tag completion. I tried disabling "auto_close_cfml", but it still does not indent and inserts a ">". I was able to work around the problem by commenting out the keybindings for > in the Default.sublime-keymap, but of course then the tag completion will no longer work. I can live with the workaround, but I thought you might want to be aware of the problem.
Thanks for all your work on this plugin. I use it daily..
The text was updated successfully, but these errors were encountered:
@palmerlovett Workaround for your issue is to open Packages/Coldfusion/Default.sublime-keymap and comment out the section around line 11 starting with "{ "keys": [">"], "command": "close_cftag", "context":".
I use the Vintageous plugin and the ColdFusion(development branch) plugin. I frequently use > in visual mode of Vintageous to indent blocks of text. Since installing ST3 I have had trouble getting this to work. Instead of indenting it inserts a ">" at the end of the selection. Looks like the ColdFusion plugin also uses the > key for tag completion. I tried disabling "auto_close_cfml", but it still does not indent and inserts a ">". I was able to work around the problem by commenting out the keybindings for > in the Default.sublime-keymap, but of course then the tag completion will no longer work. I can live with the workaround, but I thought you might want to be aware of the problem.
Thanks for all your work on this plugin. I use it daily..
The text was updated successfully, but these errors were encountered: