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

Auto-suggest doesn't close properly #150

Open
redtopia opened this issue Oct 1, 2014 · 1 comment
Open

Auto-suggest doesn't close properly #150

redtopia opened this issue Oct 1, 2014 · 1 comment

Comments

@redtopia
Copy link

redtopia commented Oct 1, 2014

Entering <cfoutput> doesn't always close the autosuggest box. The > character should force the box to close. Instead, most of the time, it remains open with the first item highlighted (cfabort). Hitting a return will insert "cfabort" immediately after <cfoutput>

The behavior is that the auto-suggest seems to recognize that I'm typing <cfoutput>, and when the close bracket is entered, the box is repopulated with the entire tag library (with cfabort highlighted) as if I'm starting a new tag.

atomi pushed a commit that referenced this issue Oct 22, 2014
@michelgallant
Copy link

atomi's fix seems to have resolved the issue when closing CFML tags, but the problem remains when closing HTML tags.

For example, I type out <td>, then I type out < and the Coldfusion autocomplete popup opens. Then, I hit the / key and Sublime auto-closes as <td></td>, but the autocomplete window remains open, and when i hit the enter key, it insert "cfabort", as this is the first tag in the autocomplete window.

I don't know if there's any way to stop this behaviour in this cause, since the closing function wouldn't be supplied by the coldfusion plugin. Any hints would be appreciated. Thanks

seancoyne added a commit to seancoyne/ColdFusion that referenced this issue Feb 25, 2015
* development:
  regression fix for new <hidden> element. sorry guys :/ fix SublimeText#155
  adds new <hidden> element to syntax parsing helpers
  closes SublimeText#150
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants