Hi
how to color syntax in terminal in OS X ?
I wrote in .vimrc:
if &t_Co > 2 || has("gui_running")
syntax on
set hlsearch
endif
syntax on
and no results.
Best regards (1 Reply)
So... i cant get it to work.
I had already posted this but it got deleted. Details:
Im running SSH shell on Windows XP, connecting to a server whose term is vt100 (someone asked me that last time)
Im trying to get the syntax highlighting in cc mode to work in color, but its black and... (0 Replies)
I was using vim about an hour ago doing abit of python (i only just started using vim). And I think i typed something wrong, and all of a sudden the letter i is always highlighted. Turning syntax off and on didn't work. and i couldent find the solution online.
Thanks in advanced. (1 Reply)
I wrote a new .lang file for syntax highlighting a language I use frequently. It works fine, except that it doesn't glob onto the files automatically. Is there a utility I need to run to update a gtksourceview database?
Here's the relevant portion of the code.
<language id="pari"... (0 Replies)
I am slowly developing my .vimrc and would like to know how to turn off the highlighting (black text on orange background) which starts at line 73. This doesn't seem to be controlled by any selected/customized colorscheme.
I do CFD, and some older codes I use are written in F77, for which this... (2 Replies)
There are some ksh files named as "*.lib" in my system. When I open them in VIM, vim syntax can't parse it correctly.
Is there a way that I can relate the *.lib with KSH syntax in VIM?
Due to access limitation, i can only update the files under my home directory and can't modify the VIM... (6 Replies)
Hi all,
my sysadmin installed Vim packages (vim-enhanced-6.3-1 & vim-common-6.3-1) on an Aix system (7.1.0.0).
I log in using Putty (vs 0.54) and got an annoying underline issue. All strings and var names are underlined as you can see on the attached file
Is it possible to get rid of that... (4 Replies)
Hey,
Just added a new UserCP option so you can change the code tags to look like the code tags in this example (turn this on and off):
Note: I set the default to "SyntaxHighlighting" for debugging purposes. We can change the default back to the original code tags later.
... (36 Replies)
Discussion started by: Neo
36 Replies
LEARN ABOUT DEBIAN
vim-registry
vim-registry(5) vim addons vim-registry(5)NAME
vim-registry - syntax for vim-addons registry files
SYNOPSIS
PACKAGE-NAME.yaml
DESCRIPTION
A registry file is a multi-document YAML file (i.e. it can be composed by several different YAML documents separated by "---" lines). Each
YAML document represents a registry entry, that is the information describing a single addon.
Ideally, the registry directory contains one file per package shipping addons; with a filename obeying to the convention PACKAGE-NAME.yaml.
Hence a single package can contribute to the registry with multiple entries described in a single YAML file.
For example, the "vim-scripts" package should ship a single /usr/share/vim/registry/vim-scripts.yaml file, containing one YAML document per
shipped addon. The first lines of such file can look like the following:
addon: alternate
description: "alternate pairing files (e.g. .c/.h) with short ex-commands"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_alternateFile = 1"
files:
- plugin/a.vim
- doc/alternate.txt
---
addon: whatdomain
description: "query the meaning of a Top Level Domain"
basedir: /usr/share/vim-scripts/
disabledby: "let loaded_whatdomain = 1"
files:
- plugin/whatdomain.vim
---
Each registry entry may contain the following fields, to be typeset according to the YAML specification:
addon (Required)
Name of the addon.
description (Required)
Human understandable textual description of the addon.
files (Required)
List of the files which compose the addon and are required to be present in a component of the Vim runtime path for the addon to be
enabled. Each file is specified relative to a component of the Vim runtime path.
basedir (Optional)
Directory where the files shipped by the addon (i.e., where the symlinks of the user/sysadm should point to) reside on the filesys-
tem. Default is /usr/share/vim/addons.
disabledby (Optional)
Vim script command that can be used (usually by adding it to ~/.vimrc) to prevent the addon from being used even when it is
installed. The intended usage of this field is to "blacklist" an undesired addon whose files are available, and hence automatically
loaded by Vim, in a component of the Vim runtime path.
AUTHOR
James Vega <jamessan@debian.org>
SEE ALSO vim-addons(1), YAML specification <http://www.yaml.org/>
COPYRIGHT
Copyright (C) 2010 James Vega
This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub-
lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.
Debian Project January 2010 vim-registry(5)