I run Sublime Text 3 with Emmet package installed. Recently Sublime has started underlining my syntax while typing with no indication of why, similar to how spell check runs automatically. I've traced this "feature" to Emmet by adding it to my ignored packages, which removes the issue. Simple question then; How the hell do I turn off this "feature" of Emmet.
It’s abbreviation capturing: https://github.com/emmetio/sublime-text-plugin#expanding-abbreviation
You can disable by setting auto_mark Emmet option to false.
But it’s better to describe cases where Emmet incorrectly marks abbreviations as errors in repo issues so I can fix it
Related
VIM VERSION: VIM - Vi IMproved 8.0 (2016 Sep 12, compiled May 2 2017 03:55:34)
I'm using a number of plugins with vim in order to make things work. I install them via the package manager Vundle, my .vimrc can be found in my dotfiles repository on github
Today, I tried to edit a SASS file with vim, however - the SASS file looks like a color-circus:
I've followed some steps from this answer which include:
Does enabling syntax explicitly fix your problem? :syntax enable
Is filetype detection on? :filetype
Does vim recognize this as a sass file? :set filetype?
Check to make sure your script directories are in the runtime path :set runtimepath?
Does manually loading the syntax file change anything? :runtime! vimfiles/syntax/sass.vim
Also check if syntax highlighting works for other filetypes.
The answers to each point are:
Nothing changed, syntax remains exactly the same.
running :filetype returns filetype detection:ON plugin:ON indent:ON
running :set filetype? returns filetype=sass
running :set runtimepath? returns a long list of ~/.vim/bundle/[PATH] entries of which none include sass in any form
running :runtime! ~/.vim/bundle/vim-haml/syntax/sass.vim also changes nothing
Syntax highlighting works for everything except SASS so far.
Additionally, I've tried adding some plugins from http://vimawesome.com/.
They all seem to be packages that either support a different package which should be supported by default or they do not support SASS (in addition to SCSS) highlighting.
This is, what I came up with in the end, still making no difference:
Plugin 'tpope/vim-haml'
Plugin 'JulesWang/css.vim'
Plugin 'hail2u/vim-css3-syntax'
The plugin tpope/vim-haml however, does have a sass.vim file with it's syntax rules, it's actually the only up-to-date one compared to the rest which all seem to hang at "last updated 5+ years ago".
I basically have two questions, which I hope, more experienced vimologists will be able to answer, or point me in the right direction of fixing it myself:
Is there any known properly updated SASS (indent syntax) plugin that I missed?
If the above question is "no", then how could I get the tpope/vim-haml sass syntax file loaded for all my sass files?
I'm using SASS since, coming from Atom, it is less typing. I would prefer to keep the sass syntax if possible! (I am aware of conversion plugins but for the sake of my colleagues I would like to refrain from using any)
Thanks in advance!
Answer
It was the colorscheme I was using, it caused severe formatting issues for my SASS files.
TLDR;
I was using roosta/srcery and just tried an alternate colorscheme to test if the sass file would look more "sane", it now looks like this (using a random colorscheme):
What we see here is still not perfect, but at least "sane" (I can understand why CSS3 flex properties aren't highlighted yet for instance), I'm simply going to try inform the author of the (really nice nonetheless) colorscheme to see if he is interested in improving it for SASS.
My lesson here, is that one should look at every aspect, I was thinking in the wrong direction and kept on going for too long as a result. When #romainl pointed out it looked fine using just regular-builtin-vim I started expecting a Plugin (a colorscheme) to be the suspect which solved my issue :)
I installed Vintageous in sublime text 3 so i can use some of vim commands and interactions. But I am using it for a long time, and there is a lot of features missing, like the 'ctrl+x' and 'ctrl+a" to decrease and increase a number, the 'ctrl+r' to redo, the 'ctrl+v' to select vertical blocks, 'ctrl+c' to quit insertion mode ... etc.
I really like sublime text 3, but in the other hand, i'm really missing this commands, it's all of theses commands which makes vim so powerful.
So how can I get a complete vim mode in sublime text 3. It would be just perfect if i can do that (because I really miss vim complete features).
PS : I'm using Ubuntu 15.10 with Linux version > 4.
Vintageous has the setting vintageous_use_ctrl_keys, which should solve most of your issues.In contrast to other packages Vintageous uses the User preferences. Hence you can just add the entry "vintageous_use_ctrl_keys": false to "Preferences >> Settings - User". However for this settings there is an entry in the control palette. Press ctrl+shift+p and write Vintageous: Toggle Vim Ctrl Keys. You can see the other settings here and just change them in the user preferences.
If you are still missing some keys I would recommend to look at the default keymap and search for other packages, which provide this behavior and change the keybinding as you want them.
Now there is a new player, ActualVim plugin.
Everything you like about using Sublime Text 3, and everything you
like about typing in vim.
Actual uses an embedded Neovim instance to accurately manipulate each
Sublime Text buffer as though you were editing the text directly in
vim, without breaking any Sublime Text features (aside from multiple
selection for now).
It’s way better than Vintage mode or Vintageous. You can use your own .vimrc, plugins, real vim motions and commands.
To get vim shortcuts in Sublime Text
Install neovim (the actual program which is unrelated to sublime text - it's necessary for this approach to work). Example brew install neovim.
In sublime, press command + shift + p, type "install package" and click on the top result.
Now search for 'ActualVim', and click on it, it should install.
Close and reopen sublime.
Vim shortcuts now work!
I'm trying to install delimitMate on vim version 7.3. I am using Pathogen. My other pathogen bundles work, so it is not a problem with my setup.
In fact, I've also tried auto-pairs and ClosePairs plugins too, and none of them work. I don't know why? Am I using it wrong? Shouldn't a matching paren simply follow when I put an opening paren (similar to sublime Text?)
The commands :DelimitMateTest and :h delimitemate works, so the script is being executed. It's just not actually autoclosing any parens, and I can't figure out why.
Here's the output file for :DelimitMateTest: http://pastebin.com/2WtHVZJL
Any ideas as to why I can't get paren completion from any plugin?
Thanks!
For those of you who come across this problem in the future:
I had set paste in my .vimrc. This permanently disables several other features, and it was messing up key mappings. Simply remove it from your .vimrc and you should fix your problem.
Can't seem to find any reason for this, but I have been using Ycm, syntastic, and all the lh- plugins with vim for a while now. In the case of lh-brackets, I used to have a problem with it generating "«»" every time it 'automatically' generated the other bracket, paren, quote, etc. But it was only happening in .vim files, so i turned it off for vim files in my vimrc. Now nothing has changed, no new scripts installed, and all of the sudden, this happens with ALL files (cpp, h, pl, py, etc). Like i said, not using heavy customization, and everything is default except the disabling of lh-brackets when editing vim files, but that has now become a hotkey since i cant use it anywhere.
My Question is this: does anyone have this or similar problem with lh-brackets, and if so, any idea how to fix it, or is there some setting I am missing?
My first thoughts are to go though and check any updated vim scripts (this just happened a day ago) that could have been updated when doing an apt-get upgrade (like debian.vim) but after that I've got nothing...
The placeholders characters can be jumped to (:h <Plug>MarkersJumpF -> <C-J> with vim, <m-ins> with gvim). That's their purpose.
If you have installed lh-cpp, see :h lh-cpp-first-steps, you'll find a quick guide to my C++ suite (and lh-brackets incidentally).
EDIT: The plugin was badly designed. I've patched the plugin to rely on g:usemarks in order to fix the ergonomic of plugin .
In the (now-) past, if you wanted to set b:usemarks to 0, you'd have needed to add an autocommand that'd set b:usemarks to 0 in all new buffers.
Now, (lh-brackets v2.2.0), if you want to always disable the placeholders/marker characters, you need to set g:usemarks to 0, not b:usemarks. Buffer-local variables are meant to be set from ftplugins, or tree/project-local plugins which are supported thanks to plugins like local_vimrc.
And as romainl has pointed out, don't hesitate to use the bug trackers, or even to contact me.
hmm found it:
:let b:usemarks=0
now needs to be set, apparently that was a marker for integration to another plugin, though i dont use it.
I'm using Vim with EasyMotion plugin. My current .vimrc is following: https://github.com/iAdramelk/.dotfiles/blob/master/vimrc
I'd like how this plugin works, bot every time I tried to move with it it prints following message and didn't move until I hit enter:
EasyMotion: Jumping to [222, 41]
Press ENTER or type command to continue
There is no such behavior in EasyMotion demo at it's repo. So I'm assuming that there is some bug in my config. But even if I disable all plugins and set options bug still persists.
How can I fix this behavior?
Do you consume the plugin through GitHub, or an official version from the vim.org website? This looks like some debugging statement left in the plugin code.
You could work around the problem by using :silent in its mappings, or increasing 'cmdheight', but I would really contact the plugin author to fix the root cause.
Fixed bug by uninstalling vim (installed by homebrew with flag --with-features=big), and then reinstalling it from here homebrew/dupes/vim in huge configuration.