I have created a syntax file for some AnB-files for vim and while it does load the syntax highlighting and highlight everything I want it to highlight, it seems to highlight some unwanted stuff as well.
The images show both my highlight file and the AnB file and the problem is:
The word "Elgamel", the characters "g" and "h" (any single lower-case letters) and the words "M1" and "M2" (any single upper-case letter followed by an integer) are highlighted with an unwanted magenta color. Anyone knows what to do here? I tried searching for the problem on both google and stackoverflow, but I couldn't find any similar questions (I might not search using the correct terms, though :D)
Syntax file: http://i.imgur.com/bYoAQcu.png
AnB file: http://i.imgur.com/FOtccXJ.png
This looks like error highlighting from the spell checker.
:set nospell
should then turn it off. You can determine which syntax groups get spell checked via :syntax spell, see :help :syn-spell. Usually, you use enable spelling in comments, etc. by added contains=#Spell.
Here's a tip for syntax script development: When you need to find out which syntax group causes the highlighting. :syn list shows all active groups, but it's easier when you install the SyntaxAttr.vim - Show syntax highlighting attributes of character under cursor plugin.
You can use the plugin HiKinkTrace to determine the highlighting group for the offending text, that should help you to narrow it down.
Related
I would like to get Vim to stop highlighting list characters (-,*) and heading characters (#) in rmarkdown. You can find a screenshot here: https://imgur.com/a/0YSB8V8.
This is happening when I set the file type to either pandoc or rmd. This is also happening no matter what terminal or colortheme I use.
I have the plugins: vim-pandoc, vim-pandoc-syntax, and vim-rmarkdown installed.
I would like to know a way to make the two characters just appear normally.
I would also like to know if there is a way to make italicized text in tables and headings appear italicized. As far as modifying the appearance of italicized text, I've tried using: hi Italic ctermfg=red cterm=italic in my vimrc, but that does not seem to affect the text in between asterisks (*) in rmd files. I admit I don't know much about the way that syntax works in Vim. Do I need to modify after/ftplugin/rmd.vim or runtime/syntax/rmd.vim? What is the difference between the two?
Any help would be appreciated!
Your syntax highlighter does not seem to recognize the bullet points, but thinks that they mark the beginning of an italic span. Maybe you have a clash of plugins. You could also try another highlighter (e.g. vim-polyglot, supports italics).
vim-pandoc-syntax uses the conceal feature (:h conceal). You can recolor the highlighting group Conceal to change the appearance of the replacement characters.
You can put changes to existing syntax files in .vim/after/syntax/rmd.vim. Files in syntax are executed when they are needed for the first time, but at most once per session. Files in ftplugin are executed every time the file type is changed.
Comments keyword are damn highlighted in Macvim/terminal vim and keeps on irritating me. I am not a pro in customizing vim, but really want to get rid of them and have subtle grey keywords
You need to find out which syntax group causes the highlighting. :syn list shows all active groups, but it's easier when you install the SyntaxAttr.vim - Show syntax highlighting attributes of character under cursor plugin. When you have the name of the offending syntax group, you can investigate where it comes from; (the last lines of) :scriptnames may help.
One solution in your case would be linking the syntax groups to the original Comment group, so that the distinction is lost. This can be done in ~/.vimrc:
:hi link FoundSyntaxGroupHere Comment
Comments were highlighted because of vim javascript plugin and by setting following inside .vimrc file, i am able to stop my comments from getting highlighted
let g:javascript_ignore_javaScriptdoc="1
Vim has a tonne of highlighting built in, and plug-ins add more. Highlighting is applied for various reasons, including code syntax, spelling, indenting, search, coding errors and standards, and so on. Because there is limited options for highlighting, there are a few highlights that look the same - in particular, code errors, and spelling mistakes are both underlined red (in my colourscheme).
Is there any way of asking vim "What highlighting rules are being applied to the character under the cursor?"
To find out which syntax group causes the highlighting. :syn list shows all active groups, but it's easier when you install the SyntaxAttr.vim - Show syntax highlighting attributes of character under cursor plugin. When you have the name of the offending syntax group, you can investigate where it comes from; (the last lines of) :scriptnames may help.
I have a problem with search highlighting in vim. I have used it before but currently it does not work at all.
I have entered :set hlsearch, which is also in my .vimrc file.
I have entered :set hlsearch? and the result is hlsearch, indicating that I have successfully turned the option on. (right?)
I am running vim and not vi, so that is not the problem.
I have searched around but only found people asking about turning OFF search highlighting.
I would appreciate any input as this has been driving me nuts. Thanks!
Edit: highlighting also doesn't work for spellcheck, so evidently it's something global about highlighting.
When you have problems with multiple highlightings (like search and spell in your case), first check the defined highlightings with
:hi
If any groups are wrong or off, check your :colorscheme, and maybe try another.
In the console, color problems are often related to the number of available colors, a hairy problem. Check with
:set t_Co?
Another good tool for checking problems with individual syntax items is the SyntaxAttr.vim - Show syntax highlighting attributes of character under cursor plugin.
I'm using Vim to edit LaTeX files and it used to automatically highlight these words and was a great help. I also have :set spell to highlight spelling mistakes and I had added TODO, FIXME and XXX to the spell-good list (zg). Recently, I did something I can't recall/reproduce and broke this. I still get LaTeX keywords like begin, section, etc. highlighted, but not these ones.
Searching online only leads to people complaining about these words being highlighted and they turn it off by issuing :syntax clear Todo. I have the exact opposite issue—I want it turned back on. Can someone clue me on how to proceed?