Tag Info

Hot answers tagged

7

When you have the file open, you can run: :set filetype=messages To automate this for all files called messages, put the following into ~/.vim/ftdetect/messages.vim: autocmd BufNewFile,BufReadPost *messages* :set filetype=messages


5

Please see: http://kde-look.org/content/show.php/darK+-+A+Kate+Syntax+Highlighting+Theme?content=53388 http://kde-look.org/content/show.php/DarkOxygen?content=140718 They might help. Also, http://askubuntu.com/questions/19005/using-oblivion-color-scheme-from-gedit-in-kate There are three dead links at the bottom of this email ...


3

This is not a direct answer but despite i hope it helps you. If you want to use vim to write your latex documents latex-suite isn't recommended anylonger, at least from my perspective. There are several more comprehensive vim-scripts which handle this task a lot better. It is worth to take a look at http://atp-vim.sourceforge.net/ and ...


2

For syntaxhighlighting in Ikiwiki there is a plugin called highlight. You can use it like [[!format tex """ \documentclass{scrartcl} … """]] This will give you nice syntax highlighting. It uses Perl bindings. The library itself has a longer documentation.


1

Turns out I can't define the style in the .lang file. In the <style> tag there I can only refer to a style that is defined in the files in /usr/share/gtksourceview-3.0/styles. E.g. to the style used for keywords in programming languages: <style id="chord" _name="Chord" map-to="def:keyword"/>


1

You have to define highlight colors. From :h :match :mat[ch] {group} /{pattern}/ Define a pattern to highlight in the current window. It will be highlighted with {group}. Example: > :highlight MyGroup ctermbg=green guibg=green :match MyGroup /TODO/ So, something like this: :hi OpenTag guibg=Green :hi ...


1

I don't think this exists. It would be useful, but hard to implement by standard means of syntax parsing used in editors. From the parsing point of view, there are many keywords and special symbols that would have to be analysed to determine a block of code that belongs to a subshell. But I'd be happy to see I'm wrong and someone has put the effort needed ...


1

First. When editing one of your .hbs, or .handlebars files, issue :set ft? in vim, and see if your filetype is being detected. If you don't see filetype=handlebars, try setting :filetype on in your .vimrc file and test again. If that doesn't work, you may need to put a filetype.vim file in your .vim directory. if exists("did_load_filetypes") finish ...



Only top voted, non community-wiki answers of a minimum length are eligible