Gecko [ renovalkoronred.com.tr ]

Name	Size	Permission
arabic.txt	11.66 KB	-rw-r--r--
autocmd.txt	63.87 KB	-rw-r--r--
change.txt	73.12 KB	-rw-r--r--
channel.txt	30.1 KB	-rw-r--r--
cmdline.txt	46.17 KB	-rw-r--r--
debug.txt	7.01 KB	-rw-r--r--
debugger.txt	5.61 KB	-rw-r--r--
develop.txt	21.82 KB	-rw-r--r--
diff.txt	16.14 KB	-rw-r--r--
digraph.txt	60.67 KB	-rw-r--r--
editing.txt	71.46 KB	-rw-r--r--
eval.txt	434.04 KB	-rw-r--r--
farsi.txt	9.48 KB	-rw-r--r--
filetype.txt	25.33 KB	-rw-r--r--
fold.txt	23.14 KB	-rw-r--r--
ft_ada.txt	17.82 KB	-rw-r--r--
ft_rust.txt	9.3 KB	-rw-r--r--
ft_sql.txt	29.97 KB	-rw-r--r--
gui.txt	44.52 KB	-rw-r--r--
gui_w32.txt	18.47 KB	-rw-r--r--
gui_x11.txt	28.79 KB	-rw-r--r--
hangulin.txt	3.21 KB	-rw-r--r--
hebrew.txt	5.58 KB	-rw-r--r--
help.txt	8.38 KB	-rw-r--r--
helphelp.txt	14 KB	-rw-r--r--
howto.txt	2.84 KB	-rw-r--r--
if_cscop.txt	18.91 KB	-rw-r--r--
if_lua.txt	14.3 KB	-rw-r--r--
if_mzsch.txt	11.55 KB	-rw-r--r--
if_ole.txt	7.23 KB	-rw-r--r--
if_perl.txt	10.89 KB	-rw-r--r--
if_pyth.txt	37.05 KB	-rw-r--r--
if_ruby.txt	7.83 KB	-rw-r--r--
if_sniff.txt	266 B	-rw-r--r--
if_tcl.txt	22.49 KB	-rw-r--r--
indent.txt	38.5 KB	-rw-r--r--
index.txt	74.65 KB	-rw-r--r--
insert.txt	81.21 KB	-rw-r--r--
intro.txt	38.31 KB	-rw-r--r--
map.txt	63.15 KB	-rw-r--r--
mbyte.txt	57.92 KB	-rw-r--r--
message.txt	30.5 KB	-rw-r--r--
mlang.txt	7.67 KB	-rw-r--r--
motion.txt	50.39 KB	-rw-r--r--
netbeans.txt	36.13 KB	-rw-r--r--
options.txt	378.02 KB	-rw-r--r--
os_390.txt	4.64 KB	-rw-r--r--
os_amiga.txt	5.33 KB	-rw-r--r--
os_beos.txt	10.73 KB	-rw-r--r--
os_dos.txt	11.74 KB	-rw-r--r--
os_mac.txt	6.69 KB	-rw-r--r--
os_mint.txt	1.37 KB	-rw-r--r--
os_msdos.txt	518 B	-rw-r--r--
os_os2.txt	294 B	-rw-r--r--
os_qnx.txt	3.98 KB	-rw-r--r--
os_risc.txt	323 B	-rw-r--r--
os_unix.txt	2.53 KB	-rw-r--r--
os_vms.txt	31.35 KB	-rw-r--r--
os_win32.txt	13.04 KB	-rw-r--r--
pattern.txt	57.93 KB	-rw-r--r--
pi_getscript.txt	20.58 KB	-rw-r--r--
pi_gzip.txt	1.29 KB	-rw-r--r--
pi_logipat.txt	4.09 KB	-rw-r--r--
pi_netrw.txt	171.44 KB	-rw-r--r--
pi_paren.txt	2.22 KB	-rw-r--r--
pi_spec.txt	4.03 KB	-rw-r--r--
pi_tar.txt	6.5 KB	-rw-r--r--
pi_vimball.txt	11.58 KB	-rw-r--r--
pi_zip.txt	6.87 KB	-rw-r--r--
print.txt	30.43 KB	-rw-r--r--
quickfix.txt	67.4 KB	-rw-r--r--
quickref.txt	69.59 KB	-rw-r--r--
quotes.txt	12.44 KB	-rw-r--r--
recover.txt	10.44 KB	-rw-r--r--
remote.txt	8.22 KB	-rw-r--r--
repeat.txt	38.65 KB	-rw-r--r--
rileft.txt	4.86 KB	-rw-r--r--
russian.txt	3.02 KB	-rw-r--r--
scroll.txt	13.74 KB	-rw-r--r--
sign.txt	6.73 KB	-rw-r--r--
spell.txt	61.31 KB	-rw-r--r--
sponsor.txt	7.03 KB	-rw-r--r--
starting.txt	71.9 KB	-rw-r--r--
syntax.txt	212.37 KB	-rw-r--r--
tabpage.txt	16.33 KB	-rw-r--r--
tags	320.99 KB	-rw-r--r--
tagsrch.txt	35.78 KB	-rw-r--r--
term.txt	44.35 KB	-rw-r--r--
terminal.txt	32.78 KB	-rw-r--r--
tips.txt	20.07 KB	-rw-r--r--
todo.txt	289.32 KB	-rw-r--r--
uganda.txt	13.7 KB	-rw-r--r--
undo.txt	16.15 KB	-rw-r--r--
usr_01.txt	6.92 KB	-rw-r--r--
usr_02.txt	23.77 KB	-rw-r--r--
usr_03.txt	23.05 KB	-rw-r--r--
usr_04.txt	18.63 KB	-rw-r--r--
usr_05.txt	23.27 KB	-rw-r--r--
usr_06.txt	9.36 KB	-rw-r--r--
usr_07.txt	15.61 KB	-rw-r--r--
usr_08.txt	18.92 KB	-rw-r--r--
usr_09.txt	11.18 KB	-rw-r--r--
usr_10.txt	28.5 KB	-rw-r--r--
usr_11.txt	12.32 KB	-rw-r--r--
usr_12.txt	13.11 KB	-rw-r--r--
usr_20.txt	13.38 KB	-rw-r--r--
usr_21.txt	17.94 KB	-rw-r--r--
usr_22.txt	13.96 KB	-rw-r--r--
usr_23.txt	12.29 KB	-rw-r--r--
usr_24.txt	20.38 KB	-rw-r--r--
usr_25.txt	18.67 KB	-rw-r--r--
usr_26.txt	8.06 KB	-rw-r--r--
usr_27.txt	17.31 KB	-rw-r--r--
usr_28.txt	15.64 KB	-rw-r--r--
usr_29.txt	19.64 KB	-rw-r--r--
usr_30.txt	22.13 KB	-rw-r--r--
usr_31.txt	10.15 KB	-rw-r--r--
usr_32.txt	5.25 KB	-rw-r--r--
usr_40.txt	22.64 KB	-rw-r--r--
usr_41.txt	87.21 KB	-rw-r--r--
usr_42.txt	13.47 KB	-rw-r--r--
usr_43.txt	7.23 KB	-rw-r--r--
usr_44.txt	28.53 KB	-rw-r--r--
usr_45.txt	17.49 KB	-rw-r--r--
usr_90.txt	17.25 KB	-rw-r--r--
usr_toc.txt	9 KB	-rw-r--r--
various.txt	28.18 KB	-rw-r--r--
version4.txt	13.58 KB	-rw-r--r--
version5.txt	301.31 KB	-rw-r--r--
version6.txt	563.53 KB	-rw-r--r--
version7.txt	658.95 KB	-rw-r--r--
version8.txt	668.21 KB	-rw-r--r--
vi_diff.txt	41.81 KB	-rw-r--r--
visual.txt	21.33 KB	-rw-r--r--
windows.txt	51.79 KB	-rw-r--r--
workshop.txt	4.52 KB	-rw-r--r--

Code Editor : usr_06.txt

*usr_06.txt*	For Vim version 8.0.  Last change: 2009 Oct 28

VIM USER MANUAL - by Bram Moolenaar

Using syntax highlighting

Black and white text is boring.  With colors your file comes to life.  This
not only looks nice, it also speeds up your work.  Change the colors used for
the different sorts of text.  Print your text, with the colors you see on the
screen.

|06.1|	Switching it on
|06.2|	No or wrong colors?
|06.3|	Different colors
|06.4|	With colors or without colors
|06.5|	Printing with colors
|06.6|	Further reading

==============================================================================
*06.1*	Switching it on

It all starts with one simple command: >

:syntax enable

That should work in most situations to get color in your files.  Vim will
automagically detect the type of file and load the right syntax highlighting.
Suddenly comments are blue, keywords brown and strings red.  This makes it
easy to overview the file.  After a while you will find that black&white text
slows you down!

If you always want to use syntax highlighting, put the ":syntax enable"
command in your |vimrc| file.

If you want syntax highlighting only when the terminal supports colors, you
can put this in your |vimrc| file: >

if &t_Co > 1
	   syntax enable
	endif

If you want syntax highlighting only in the GUI version, put the ":syntax
enable" command in your |gvimrc| file.

==============================================================================
*06.2*	No or wrong colors?

There can be a number of reasons why you don't see colors:

- Your terminal does not support colors.
	Vim will use bold, italic and underlined text, but this doesn't look
	very nice.  You probably will want to try to get a terminal with
	colors.  For Unix, I recommend the xterm from the XFree86 project:
	|xfree-xterm|.

- Your terminal does support colors, but Vim doesn't know this.
	Make sure your $TERM setting is correct.  For example, when using an
	xterm that supports colors: >

setenv TERM xterm-color
<
	or (depending on your shell): >

TERM=xterm-color; export TERM

<	The terminal name must match the terminal you are using.  If it
	still doesn't work, have a look at |xterm-color|, which shows a few
	ways to make Vim display colors (not only for an xterm).

- The file type is not recognized.
	Vim doesn't know all file types, and sometimes it's near to impossible
	to tell what language a file uses.  Try this command: >

:set filetype
<
	If the result is "filetype=" then the problem is indeed that Vim
	doesn't know what type of file this is.  You can set the type
	manually: >

:set filetype=fortran

<	To see which types are available, look in the directory
	$VIMRUNTIME/syntax.  For the GUI you can use the Syntax menu.
	Setting the filetype can also be done with a |modeline|, so that the
	file will be highlighted each time you edit it.  For example, this
	line can be used in a Makefile (put it near the start or end of the
	file): >

# vim: syntax=make

<	You might know how to detect the file type yourself.  Often the file
	name extension (after the dot) can be used.
	See |new-filetype| for how to tell Vim to detect that file type.

- There is no highlighting for your file type.
	You could try using a similar file type by manually setting it as
	mentioned above.  If that isn't good enough, you can write your own
	syntax file, see |mysyntaxfile|.

Or the colors could be wrong:

- The colored text is very hard to read.
	Vim guesses the background color that you are using.  If it is black
	(or another dark color) it will use light colors for text.  If it is
	white (or another light color) it will use dark colors for text.  If
	Vim guessed wrong the text will be hard to read.  To solve this, set
	the 'background' option.  For a dark background: >

:set background=dark

<	And for a light background: >

:set background=light

<	Make sure you put this _before_ the ":syntax enable" command,
	otherwise the colors will already have been set.  You could do
	":syntax reset" after setting 'background' to make Vim set the default
	colors again.

- The colors are wrong when scrolling bottom to top.
	Vim doesn't read the whole file to parse the text.  It starts parsing
	wherever you are viewing the file.  That saves a lot of time, but
	sometimes the colors are wrong.  A simple fix is hitting CTRL-L.  Or
	scroll back a bit and then forward again.
	For a real fix, see |:syn-sync|.  Some syntax files have a way to make
	it look further back, see the help for the specific syntax file.  For
	example, |tex.vim| for the TeX syntax.

==============================================================================
*06.3*	Different colors				*:syn-default-override*

If you don't like the default colors, you can select another color scheme.  In
the GUI use the Edit/Color Scheme menu.  You can also type the command: >

:colorscheme evening

"evening" is the name of the color scheme.  There are several others you might
want to try out.  Look in the directory $VIMRUNTIME/colors.

When you found the color scheme that you like, add the ":colorscheme" command
to your |vimrc| file.

You could also write your own color scheme.  This is how you do it:

1. Select a color scheme that comes close.  Copy this file to your own Vim
   directory.  For Unix, this should work: >

!mkdir ~/.vim/colors
	!cp $VIMRUNTIME/colors/morning.vim ~/.vim/colors/mine.vim
<
   This is done from Vim, because it knows the value of $VIMRUNTIME.

2. Edit the color scheme file.  These entries are useful:

term		attributes in a B&W terminal
	cterm		attributes in a color terminal
	ctermfg		foreground color in a color terminal
	ctermbg		background color in a color terminal
	gui		attributes in the GUI
	guifg		foreground color in the GUI
	guibg		background color in the GUI

For example, to make comments green: >

:highlight Comment ctermfg=green guifg=green
<
   Attributes you can use for "cterm" and "gui" are "bold" and "underline".
   If you want both, use "bold,underline".  For details see the |:highlight|
   command.

3. Tell Vim to always use your color scheme.  Put this line in your |vimrc|: >

colorscheme mine

If you want to see what the most often used color combinations look like, use
this command: >

:runtime syntax/colortest.vim

You will see text in various color combinations.  You can check which ones are
readable and look nice.

==============================================================================
*06.4*	With colors or without colors

Displaying text in color takes a lot of effort.  If you find the displaying
too slow, you might want to disable syntax highlighting for a moment: >

:syntax clear

When editing another file (or the same one) the colors will come back.

*:syn-off*
If you want to stop highlighting completely use: >

:syntax off

This will completely disable syntax highlighting and remove it immediately for
all buffers.

*:syn-manual*
If you want syntax highlighting only for specific files, use this: >

:syntax manual

This will enable the syntax highlighting, but not switch it on automatically
when starting to edit a buffer.  To switch highlighting on for the current
buffer, set the 'syntax' option: >

:set syntax=ON
<
==============================================================================
*06.5*	Printing with colors				*syntax-printing*

In the MS-Windows version you can print the current file with this command: >

:hardcopy

You will get the usual printer dialog, where you can select the printer and a
few settings.  If you have a color printer, the paper output should look the
same as what you see inside Vim.  But when you use a dark background the
colors will be adjusted to look good on white paper.

There are several options that change the way Vim prints:
	'printdevice'
	'printheader'
	'printfont'
	'printoptions'

To print only a range of lines,  use Visual mode to select the lines and then
type the command: >

v100j:hardcopy

"v" starts Visual mode.  "100j" moves a hundred lines down, they will be
highlighted.  Then ":hardcopy" will print those lines.  You can use other
commands to move in Visual mode, of course.

This also works on Unix, if you have a PostScript printer.  Otherwise, you
will have to do a bit more work.  You need to convert the text to HTML first,
and then print it from a web browser.

Convert the current file to HTML with this command: >

:TOhtml

In case that doesn't work: >

:source $VIMRUNTIME/syntax/2html.vim

You will see it crunching away, this can take quite a while for a large file.
Some time later another window shows the HTML code.  Now write this somewhere
(doesn't matter where, you throw it away later):
>
	:write main.c.html

Open this file in your favorite browser and print it from there.  If all goes
well, the output should look exactly as it does in Vim.  See |2html.vim| for
details.  Don't forget to delete the HTML file when you are done with it.

Instead of printing, you could also put the HTML file on a web server, and let
others look at the colored text.

==============================================================================
*06.6*	Further reading

|usr_44.txt|  Your own syntax highlighted.
|syntax|      All the details.

==============================================================================

Next chapter: |usr_07.txt|  Editing more than one file

${this.title}

Code Editor : usr_06.txt