I have installed emmet for Sublime Text 2...
And it works - kind a strange way
When I enter d it starts showing possibilities, but as soon as I press: : emmet shows completely different tip:
b (bottom)
So I need to press esc to close fuzzysearch box and press tab to allow Emmet do what it is used to do.
Dow, if I don't press esc before the tab key the resould is: d:bottom:, is I press esc, it desoults in correct: display:block.
Do you have an idea how can i fix that?
This happens because Emmet tries to respect default ST completions and due to lack of API support to properly handle built-in snippets: https://github.com/sergeche/emmet-sublime#tab-key-handler
By default, Emmet will not expand abbreviations by Tab if there’s autocomplete popup visible to allow users to work with default ST completions and snippets. You can override this behavior:
Go to Preferences > Settings — User
Add "disable_tab_abbreviations_on_auto_complete": false option. Make sure this file contains valid JSON.
After that everything should work fine, but you’ll no longer able to complete items from autocomplete popup with Tab key, use Enter key instead.
I had a similar issue but my fix was different to that of the accepted answer.
I had to go to Preferences > Settings — User and remove "emmet" from the ignored packages and everything started working again!
If my cursor is placed after an html closing tag and I press enter, I get a popup auto-completion suggestion as follows:
p> (element)
If I press enter again p> is printed on the screen.
This is annoying and I want to prevent it but how? I have already tried setting auto_complete to false in user preferences but that did not work.
There is complete description for Auto Completion on there site as
Disabling Auto Complete
Auto complete can be disabled with the auto_complete setting. To disable it, add this line to Preferences/File Settings - User:
"auto_complete": false
If auto complete is disabled, the completion popup can be shown manually, or tab can be used to insert the highest ranking completion without showing the popup.
Manually Showing Completions
Pressing Ctrl+Space will show the completion popup if it's not currently showing. If it is showing, it'll select the next item.
Commit on Tab
By default, the selected item in the completion popup will be committed when enter is pressed. This can create ambiguity between committing the completion, and inserting a newline. By setting the auto_complete_commit_on_tab setting to true, enter will insert a newline, and tab will commit the current completion. There are other benefits, too: because Sublime Text knows there is no ambiguity, it will show a more curated list of completions, with the one you want more likely to be in first place.
Enabling Commit on Tab is recommended, but it will take a short time to get used to.
Source :Sublime 2 Auto Complete
Hope this helps.
Answer in short (worked for me): Remove SublimeCodeIntel package.
After searching some more, I found that this is actually a long standing problem (7 months). The problem is posted on github as issue #279 and issue #359. Still not sure how to fix it exactly though (Without removing the package).
Long answer:
I was having the same problem you describe and it also annoyed me.
For me the problem was coming from the SublimeCodeIntel package that I installed in Sublime Text, so I guess you also have this package installed, causing this problem. I'm using ST version 3, but I guess there should be no difference to version 2 regarding this issue.
Although the answer by Jatin seems to be a work-a-round, (disabling the auto_complete will just mask the problem, what if you want to keep auto_complete on true), when I actually set auto_complete to false, I was still getting the auto_complete pop-up. After some thought, my guess was because of the SublimeCodeIntel package I had installed.
So I removed the SublimeCodeIntel package and behold, no popup auto-completion with the "p> (element)" suggestion.
Of course, removing SublimeCodeIntel may also seem a bit of a drastic solution. Maybe the package can be configured in such a way that the problem does not occur any more. I haven't looked into the problem why SublimeCodeIntel displays this incorrect auto complete suggestion. It might be good to send a bug report to the author of the package? (At the moment I'm happy enough to just remove the package)
You can disable the languages that CodeIntel autocompletes for.
The default setting is:
"codeintel_enabled_languages":
[
"JavaScript", "SCSS", "Python", "HTML",
"Ruby", "Python3", "XML", "Sass", "HTML5", "Perl", "CSS",
"Twig", "Less", "Node.js", "TemplateToolkit", "PHP"
],
Override the settings in your User Settings by removing the HTML and HTML5 items (paste this into your User Settings: Go to Preferences -> Package Settings -> SublimeCodeIntel -> Settings - User):
{
"codeintel_enabled_languages":
[
"JavaScript", "SCSS", "Python",
"Ruby", "Python3", "XML", "Sass", "Perl", "CSS",
"Twig", "Less", "Node.js", "TemplateToolkit", "PHP"
]
}
I have some HTML I'd like to fix:
<label>Name<label>
As you can see, this isn't closed. When I attempt to close the element, I get:
<label>Name</label>label>
Which then requires manual fixing.
How can I make Sublime autocomplete work, or disbale it? Note I already have:
"auto_complete": false
In my user preferences.
This is not auto_complete as I know as auto_complete is triggered on tab and other key presses.
What you seek is auto_close_tags, setting it to false will not bother you anymore with this autocompletion, as to fixing this - I don't have such problems in ST3, so consider simply updating.
Anyone with firefox browser can you open up this fiddle.
The issue I have is with this checkbox button I have, it requires multiple clicks to turn it off and my question is how can I stop this from happening? I know its the posistion:relative which is causing this but I need this so that every time I click on a button, it does not go to the top of the page. I just want the button to turn on and off in one click, not multiple clicks
(See comments below the question - now I know what happens to you)
Ahhh - you cannot solve this without Javascript: quick (double?) click on the TEXT ITSELF is interpreted as "select text" by the browser, and it does not send the event to the checkbox when that happens. With Javascript you can force "un-select" of the text on click.
Click "slowly" - avoiding double click text selection - and it will work (just to show the cause of the problem, no solution without Javascript or proprietary CSS).
Try adding this: Prevent text selection after double click
Maybe you should use a full Javascript Checkbox-Button solution instead of trying to accomplish it with just CSS.
I love that I can tab through {}, [], (), etc. in Aptana but when I'm editing HTML and the existing node I'm currently editing is highlighted with the same light-grey border I inevitably try to step through it when I'm done by hitting tab and re-discover it doesn't work.
Am I missing a really obvious keyboard shortcut?
Shift+Enter will jump to the next line (while also adding a new line after the current one), but I don't think there is a shortcut to cycle past it normally.