Vim Tips Wiki - Recent changes [en]

Search for current word in multiple files

2012-05-16T22:05:54Z

Comments:

← Older revision		Revision as of 22:05, May 16, 2012
Line 33:		Line 33:

	Only the first of those commands will work when using gvim in Windows Vista.		Only the first of those commands will work when using gvim in Windows Vista.
		+
		+
		+	Need to add a single quote around the \b versions (i.e. grep '\b<cword>\b').

Loading scripts in vimrc safely

2012-05-16T14:14:49Z

← Older revision		Revision as of 14:14, May 16, 2012
Line 21:		Line 21:
	endif		endif
	</pre>		</pre>
		+	Note: version 6.1 would be 601

	(2) Use environment variables:		(2) Use environment variables:

Convert between hex and decimal

2012-05-16T12:15:28Z

80 character line wrap without broken words

2012-05-16T03:09:45Z

Comments: Add links to related tips.

← Older revision		Revision as of 03:09, May 16, 2012
Line 25:		Line 25:
	==Comments==		==Comments==
	What problem are you trying to solve? Inserting hard line breaks in a line which is too long never wraps in the middle of the word. Were you having trouble with the 'wrap' option? Did you not know about it's partner 'linebreak' option?		What problem are you trying to solve? Inserting hard line breaks in a line which is too long never wraps in the middle of the word. Were you having trouble with the 'wrap' option? Did you not know about it's partner 'linebreak' option?
		+
		+	----
		+	Related tips:
		+	*[[VimTip38\|38 Move cursor by display lines when wrapping]]
		+	*[[VimTip308\|308 Move through wrapped lines]]
		+	*[[VimTip440\|440 Automatic formatting of paragraphs]] (mentions <tt>formatoptions</tt>)
		+	*[[VimTip850\|850 Automatic word wrapping]]
		+	*[[VimTip989\|989 Word wrap without line breaks]] (mentions <tt>formatoptions</tt>)
		+	From {{help\|fo-table}}:
		+	:<tt>w</tt> Trailing white space indicates a paragraph continues in the next line. A line that ends in a non-white character ends a paragraph.
		+	I'm not familiar with the <tt>w</tt> option and am not sure if it is doing anything useful in this tip. I guess this tip should be merged to one of those above. [[User:JohnBeckett\|JohnBeckett]] 03:09, May 16, 2012 (UTC)

Vim Tips Wiki:New tips/201204

2012-05-16T02:56:51Z

Have renamed tip and added a "probably delete" comment.

← Older revision		Revision as of 02:56, May 16, 2012
Line 19:		Line 19:
	!align="center" width="150"\|Current consensus		!align="center" width="150"\|Current consensus
	\|-		\|-
-	\| [[Auto-detect number of cores for parallel built]]	+	\| [[Auto-detect number of cores for parallel build]]
-	\|align="center"\| -	+	\|align="center"\| Keep
	\|-		\|-
	\| [[Highlighting]]		\| [[Highlighting]]
Line 33:		Line 33:
	==General comments (not for a specific tip)==		==General comments (not for a specific tip)==

-	==[[Auto-detect number of cores for parallel built]]==	+	==[[Auto-detect number of cores for parallel build]]==
-	*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)	+	Renamed from original: [[Auto-detect number of cores for parallel built]]
		+	*'''Keep'''. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)
	:Yes, I like this title (with the typo corrected). --[[User:Fritzophrenic\|Fritzophrenic]] 17:12, May 15, 2012 (UTC)		:Yes, I like this title (with the typo corrected). --[[User:Fritzophrenic\|Fritzophrenic]] 17:12, May 15, 2012 (UTC)

Line 43:		Line 43:
	Unusual tip. Is it useful for Vim? Rename it to what? [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)		Unusual tip. Is it useful for Vim? Rename it to what? [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)
	:I agree with that assessment! I'm not sure what to do with it. At least we should go ahead and search for Vim plugins to do this...but even then, most of the tip is a generic description of what DBGp is and has very little to do with Vim. I don't want to alienate a user who is obviously willing to do a lot of writing on the wiki, but on the other hand, the tip as mentioned has very little to do with Vim, so I think normally we'd delete it. --[[User:Fritzophrenic\|Fritzophrenic]] 17:36, May 15, 2012 (UTC)		:I agree with that assessment! I'm not sure what to do with it. At least we should go ahead and search for Vim plugins to do this...but even then, most of the tip is a generic description of what DBGp is and has very little to do with Vim. I don't want to alienate a user who is obviously willing to do a lot of writing on the wiki, but on the other hand, the tip as mentioned has very little to do with Vim, so I think normally we'd delete it. --[[User:Fritzophrenic\|Fritzophrenic]] 17:36, May 15, 2012 (UTC)
		+	::I have added a comment to the tip to alert anyone following it that the page is likely to be deleted. [[User:JohnBeckett\|JohnBeckett]] 02:56, May 16, 2012 (UTC)

	----		----

Vim DBGp client (for debugging php with XDebug extension)

2012-05-16T02:55:37Z

Comments: Alert that tip is likely to be deleted.

← Older revision		Revision as of 02:55, May 16, 2012
Line 59:		Line 59:

	==Comments==		==Comments==
		+	Anyone following this page may want to join the discussion at [[Vim Tips Wiki:New tips/201204]]. This tip does not have any significant information about Vim, so its future is unclear and it is likely that it '''will be deleted''' as it currently stands. The documentation at {{script\|id=4009}} seems adequate and the explanation here does not seem to be needed. The text should be used at a website with information about XDebug. [[User:JohnBeckett\|JohnBeckett]] 02:55, May 16, 2012 (UTC)

Auto-detect number of cores for parallel built

2012-05-16T02:45:27Z

moved [[Auto-detect number of cores for parallel built]] to [[Auto-detect number of cores for parallel build]] Fix typo as agreed at 201204.

Show the length of the current word

2012-05-16T01:51:11Z

Clean.

← Older revision		Revision as of 01:51, May 16, 2012
Line 1:		Line 1:
-	{{review}}
	{{TipImported		{{TipImported
	\|id=258		\|id=258
-	\|previous=256	+	\|previous=255
	\|next=261		\|next=261
	\|created=2002		\|created=2002
Line 12:		Line 11:
	\|category2=		\|category2=
	}}		}}
-	Ever wondered how long the current word is? This can be quite useful when editing data files. Simply add the following to your [[vimrc]]:	+	Ever wondered how long the current word is? This can be quite useful when editing data files. Add the following to your [[vimrc]]:
	<pre>		<pre>
-	nmap <C-_> :echo 'word' expand("<cword>") ' wordlen =' strlen(expand("<cword>"))<CR>	+	nnoremap <C-_> :echo 'word' expand('<cword>') 'has length' strlen(expand('<cword>'))<CR>
	</pre>		</pre>

-	and it will tell you the word under the cursor, and how long it is.	+	Then press Ctrl-_ to display the word under the cursor, and its length. The length is the number of ''bytes'' in the word, which is not the same as the number of characters if a multi-byte encoding is used. To get the number of characters, use:
		+	<pre>
		+	nnoremap <C-_> :echo 'word' expand('<cword>') 'has length' strlen(substitute(expand('<cword>'), '.', 'x', 'g'))<CR>
		+	</pre>

-	And for things that aren't words, this addition to your vimrc works on sections of a line that have been hightligted in visual mode	+	For strings that aren't words, use the following to show the number of bytes in visually selected text when Ctrl-_ is pressed:
	<pre>		<pre>
-	vmap <C-_> "-y:echo 'word' @- ' wordlen =' strlen(@-)<CR>	+	vnoremap <C-_> "-y:echo 'text' @- 'has length' strlen(@-)<CR>
	</pre>		</pre>

-	again you see the "word", and its length.	+	It would be better to use {{tt\|:set showcmd}} to display the length (in bytes and characters) of any visually selected text. Then type <tt>viw</tt> to select the current word and show its length (<tt>v</tt> starts a character-wise visual selection and <tt>iw</tt> selects the inner word).

	==Comments==		==Comments==
-	If <tt>'showcmd'</tt> is set, viw also shows the length of the current word. {{help\|'showcmd'}}
-	:v - start visual mode per character
-	:iw - select inner word
-
-	----

Integrate gvim with Visual Studio

2012-05-16T01:27:11Z

Tweaks, mainly header levels, changed "VimualStudio" to "VimStudio" for clarity as "Vimual" looks like a typo.

← Older revision		Revision as of 01:27, May 16, 2012
Line 2:		Line 2:
	\|id=683		\|id=683
	\|previous=682		\|previous=682
-	\|next=684	+	\|next=685
	\|created=2004		\|created=2004
	\|complexity=intermediate		\|complexity=intermediate
Line 13:		Line 13:
	On Windows systems, there are several ways to integrate Vim with Microsoft Visual Studio.		On Windows systems, there are several ways to integrate Vim with Microsoft Visual Studio.

-	=Integration of Vim with Visual Studio 2003 and later=	+	==Integration of Vim with Visual Studio 2003 and later==
-	==Control Visual Studio from Vim==	+	===Control Visual Studio from Vim===
	Script {{script\|id=864\|text=visual_studio.vim}}{{anchor\|MetaCosm VisVim Disinterest}} includes features:		Script {{script\|id=864\|text=visual_studio.vim}}{{anchor\|MetaCosm VisVim Disinterest}} includes features:
	*Compatible with Visual Studio 2003, 2005 and 2008		*Compatible with Visual Studio 2003, 2005 and 2008
Line 24:		Line 24:
	*Load results from Visual Studio into the Vim quickfix file.		*Load results from Visual Studio into the Vim quickfix file.

-	==Making Visual Studio's Editor Work like Vim==	+	===Making Visual Studio's editor work like Vim===
	[http://www.viemu.com/ ViEmu for Visual Studio] is commercial software that emulates Vim editing commands within Visual Studio (Vim is not used).		[http://www.viemu.com/ ViEmu for Visual Studio] is commercial software that emulates Vim editing commands within Visual Studio (Vim is not used).

	[http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 VsVim] is an open source Vim emulator (code at https://github.com/jaredpar/VsVim ). It is only available for all editons of Visual Studio 2010 (with support for 2011 planned) excluding Express Edition, and as with viemu does not use Vim.		[http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 VsVim] is an open source Vim emulator (code at https://github.com/jaredpar/VsVim ). It is only available for all editons of Visual Studio 2010 (with support for 2011 planned) excluding Express Edition, and as with viemu does not use Vim.

-	==Vim as an External Tool==	+	===Vim as an external tool===
	If you like Vim and use MS Visual Studio .NET for debugging and want a lightweight way to open the file you're currently debugging in VS in Vim, you can add Vim as an external tool. This will let you use a single keystroke to open the current VS file in vim with the cursor at the same line and even at the same column.		If you like Vim and use MS Visual Studio .NET for debugging and want a lightweight way to open the file you're currently debugging in VS in Vim, you can add Vim as an external tool. This will let you use a single keystroke to open the current VS file in vim with the cursor at the same line and even at the same column.

	'''The Tool:''' In Visual Studio, Tools > External Tools > Add:		'''The Tool:''' In Visual Studio, Tools > External Tools > Add:
-	*''Title:'' &Vim	+	*''Title:'' <tt>&Vim</tt>
-	*''Command:'' C:\Vim\vim73\gvim.exe	+	*''Command:'' <tt>C:\Vim\vim73\gvim.exe</tt>
-	*''Arguments:'' --servername VimualStudio --remote-silent +"call cursor($(CurLine),$(CurCol))" $(ItemFileName)$(ItemExt)	+	*''Arguments:'' <tt>--servername VimStudio --remote-silent +"call cursor($(CurLine),$(CurCol))" $(ItemFileName)$(ItemExt)</tt>
-	*''Initial directory:'' $(ItemDir)	+	*''Initial directory:'' <tt>$(ItemDir)</tt>

	If you have other settings you'd like to apply (like ''normal zz'' to centre the cursor or updating ''path'' for '':[[Project_browsing_using_find\|find]]'', then you can put them in ''~/.vim/visualstudioinvoke.vim'' and add ''+"runtime visualstudioinvoke.vim"'' before ''$(ItemFileName)''.		If you have other settings you'd like to apply (like ''normal zz'' to centre the cursor or updating ''path'' for '':[[Project_browsing_using_find\|find]]'', then you can put them in ''~/.vim/visualstudioinvoke.vim'' and add ''+"runtime visualstudioinvoke.vim"'' before ''$(ItemFileName)''.
Line 46:		Line 46:
	This will allow you to use your key combination to open the current file at the current line and cursor in a new vim browser. The browser will start at the directory of that file, so ':e .' will edit the directory of that file.		This will allow you to use your key combination to open the current file at the current line and cursor in a new vim browser. The browser will start at the directory of that file, so ':e .' will edit the directory of that file.

-	Remove the <code>--servername VimualStudio</code> part if you want it to open a new instance of Vim each time.	+	Remove the <tt>--servername VimStudio</tt> part if you want it to open a new instance of Vim each time.

	'''Preventing Nagging:''' In order to effectively use the two together and make sure .NET does not complain about its files changing, goto Tools > Options > Environment > Documents and ensure these two options are checked:		'''Preventing Nagging:''' In order to effectively use the two together and make sure .NET does not complain about its files changing, goto Tools > Options > Environment > Documents and ensure these two options are checked:
Line 57:		Line 57:
	See [[Use Vim like an IDE]] for some useful plugins to help you stay in Vim longer.		See [[Use Vim like an IDE]] for some useful plugins to help you stay in Vim longer.

-	===Using Old Versions of Vim===	+	====Using old versions of Vim====
	'''Note:''' Only old versions of Vim include sendtovim.exe.		'''Note:''' Only old versions of Vim include sendtovim.exe.

Line 68:		Line 68:
	Note: <c-z> brings gvim to foreground - on win2k, gvim gets focus but won't bring itself to foreground otherwise. You can remove it if you don't have this bring-to-foreground problem.		Note: <c-z> brings gvim to foreground - on win2k, gvim gets focus but won't bring itself to foreground otherwise. You can remove it if you don't have this bring-to-foreground problem.

-	==Opening Vim file in Visual Studio==	+	===Opening Vim file in Visual Studio===
-	Much like vim's --remote, you can run devenv with the edit parameter to open a file in an existing visual studio. This command abbreviation opens the file you're currently editing, but doesn't transfer line or column postition.	+	Much like Vim's <tt>--remote</tt>, you can run devenv with the edit parameter to open a file in an existing Visual Studio. This command abbreviation opens the file you are currently editing, but doesn't transfer line or column postition.
	<pre>		<pre>
	:cabbrev vsedit :!"c:\Program Files\Microsoft Visual Studio 8\Common7\ide\devenv.exe" /edit "%"		:cabbrev vsedit :!"c:\Program Files\Microsoft Visual Studio 8\Common7\ide\devenv.exe" /edit "%"
Line 76:		Line 76:
	''See also [[Using DDE to open the current Vim file in Visual Studio]].''		''See also [[Using DDE to open the current Vim file in Visual Studio]].''

-	==Use Vim instead of Visual Studio's Editor==	+	==Use Vim instead of Visual Studio's editor==
	''This is not the same as [[Embedding vim in Visual Studio]].''		''This is not the same as [[Embedding vim in Visual Studio]].''

Line 90:		Line 90:
	Of course if you want to reverse changes simply remove gvim from the list of editors; but why would you want to do that?		Of course if you want to reverse changes simply remove gvim from the list of editors; but why would you want to do that?

-	===Window Size===	+	===Window size===
	VS.net opens the window in the middle of the screen and at the location and size of the its "source pane". How can I adjust where and of what size is the vim window when it opens? You can control your window size in your vimrc:		VS.net opens the window in the middle of the screen and at the location and size of the its "source pane". How can I adjust where and of what size is the vim window when it opens? You can control your window size in your vimrc:
	<pre>		<pre>
Line 100:		Line 100:
	You can restrict this to files of a certain type by adding the above lines to a .vim file in your ftplugin directory. (For example in ~/.vim/ftplugin/cpp.vim for c++ files in visual studio.)		You can restrict this to files of a certain type by adding the above lines to a .vim file in your ftplugin directory. (For example in ~/.vim/ftplugin/cpp.vim for c++ files in visual studio.)

-	===Editing in a Single Vim===	+	===Editing in a single Vim===
	If VS.Net insists on opening each file in a new vim window, you may be able to force it to open each file in the same window by using a batch file instead of gvim to use vim's server-client functionality. Try this:		If VS.Net insists on opening each file in a new vim window, you may be able to force it to open each file in the same window by using a batch file instead of gvim to use vim's server-client functionality. Try this:
-	pathtovim\gvim.exe --servername VIMUALSTUDIO --server-silent %*	+	<pre>
		+	pathtovim\gvim.exe --servername VimStudio --server-silent %*
		+	</pre>

-	=Integration of Vim with older versions of Visual Studio=	+	==Integration of Vim with pre-2003 versions of Visual Studio==
	*[[VisVim for Visual Studio]]		*[[VisVim for Visual Studio]]
	*[[Using DDE to open the current Vim file in Visual Studio]]		*[[Using DDE to open the current Vim file in Visual Studio]]
	*[[Embedding vim in Visual Studio]]		*[[Embedding vim in Visual Studio]]

-	=Compiling from Vim=	+	==Compiling from Vim==
	If you use nmake, you can use <tt>compiler msvc</tt> to set Vim's <tt>errorformat</tt> and <tt>makeprg</tt> for Visual C++. Use <tt>compiler cs</tt> for C#.		If you use nmake, you can use <tt>compiler msvc</tt> to set Vim's <tt>errorformat</tt> and <tt>makeprg</tt> for Visual C++. Use <tt>compiler cs</tt> for C#.

-	=See also=	+	==See also==
	*[[Use Vim like an IDE]]		*[[Use Vim like an IDE]]
	*[[VimTip345\|345 Quickfix and Visual Studio and cygwin]]		*[[VimTip345\|345 Quickfix and Visual Studio and cygwin]]
	*[[VimTip719\|719 Use Python to build project in Visual Studio]]		*[[VimTip719\|719 Use Python to build project in Visual Studio]]

-	=References=	+	==References==
	*{{help\|--servername}}		*{{help\|--servername}}
	*{{help\|--remote}}		*{{help\|--remote}}
	*[http://msdn.microsoft.com/en-us/library/ekbzk5f8(v=VS.100).aspx Visual Studio: Arguments for External Tools]		*[http://msdn.microsoft.com/en-us/library/ekbzk5f8(v=VS.100).aspx Visual Studio: Arguments for External Tools]

-	=Comments=	+	==Comments==

Use Taglist with LaTeX files

2012-05-16T01:07:13Z

Redirect to Browsing programs with tags which has the useful content (link to doc page).

← Older revision		Revision as of 01:07, May 16, 2012
Line 1:		Line 1:
-	{{delete\|The taglist plugin says NOT to make a change like this tip does. In addition, the taglist documentation includes an example how to integrate with LaTeX, making this tip obsolete. In addition, the taglist documentation is a better place to keep this info since the taglist developers will keep the example up to date. Also, I link to the vim-taglist documentation on [[:Category:LaTeX]].}}	+	#REDIRECT [[Browsing programs with tags]]
-	{{TipImported
-	\|id=453
-	\|previous=452
-	\|next=457
-	\|created=April 14, 2003
-	\|complexity=intermediate
-	\|author=Florent Manens
-	\|version=6.0
-	\|rating=19/7
-	\|category1=LaTeX
-	\|category2=Navigation
-	\|category3=Plugin
-	}}
-
-	Read the documentation at [http://vim-taglist.sourceforge.net/extend.html vim-taglist] for how to integrate LaTeX. Essentially, you just need to add some entries into ~/.ctags and then add two lines to your vimrc or tex.vim ftplugin.

VimTip453

2012-05-16T01:07:09Z

Fix redirect for merged tip.

← Older revision		Revision as of 01:07, May 16, 2012
Line 1:		Line 1:
-	#REDIRECT [[Use Taglist with LaTeX files]]	+	#REDIRECT [[Browsing programs with tags]]

Browsing programs with tags

2012-05-16T01:05:02Z

Remove mention of unhelpful 453, but link to taglist docs.

← Older revision		Revision as of 01:05, May 16, 2012
Line 168:		Line 168:
	</pre>		</pre>

-	See [[VimTip453\|Use Taglist with LaTeX files]] for another example that adds support for LaTeX.	+	Other examples, including for LaTeX, are in the [http://vim-taglist.sourceforge.net/extend.html documentation] for the {{script\|id=273\|text=taglist}} plugin.

	==Creating a tags file using ctags==		==Creating a tags file using ctags==
Line 205:		Line 205:
	*[[VimTip79\|79 Use grep to get a clickable list of function names]]		*[[VimTip79\|79 Use grep to get a clickable list of function names]]
	*[[VimTip404\|404 Tags for Mixed Assembly and C]]		*[[VimTip404\|404 Tags for Mixed Assembly and C]]
-	*[[VimTip453\|453 Use Taglist with LaTeX files]]
	*[[VimTip558\|558 Using TagList for ANT build files]]		*[[VimTip558\|558 Using TagList for ANT build files]]
	*[[VimTip568\|568 Use temporary tags file when browsing new source]]		*[[VimTip568\|568 Use temporary tags file when browsing new source]]

Template:Removed

2012-05-16T00:42:59Z

Add __NOEDITSECTION__ as pointless to have edit link on 'removed' pages.

← Older revision		Revision as of 00:42, May 16, 2012
(One intermediate revision not shown)
Line 1:		Line 1:
-	<includeonly>[[Category:Removed]]	+	<includeonly>[[Category:Removed]]__NOEDITSECTION__
	{{TipNavigation\|{{{1}}}\|prev={{{prev\|}}}\|next={{{next\|}}}}}		{{TipNavigation\|{{{1}}}\|prev={{{prev\|}}}\|next={{{next\|}}}}}
	==Tip {{{1}}} has been removed==		==Tip {{{1}}} has been removed==
-
	It is hard to find helpful information if there are too many tips.		It is hard to find helpful information if there are too many tips.

Line 9:		Line 8:
	{{#ifexpr: {{{1}}} > 1504 \| This tip was created on this wiki (it was not imported from vim.org). \| The original tip was at vim.org which may be in this archive [http://web.archive.org/web/www.vim.org/tips/tip.php?tip_id={{{1}}} Tip#{{{1}}}].}}		{{#ifexpr: {{{1}}} > 1504 \| This tip was created on this wiki (it was not imported from vim.org). \| The original tip was at vim.org which may be in this archive [http://web.archive.org/web/www.vim.org/tips/tip.php?tip_id={{{1}}} Tip#{{{1}}}].}}

-	'''{{{info\|}}}'''	+	{{#if: {{{info\|}}}\|'''{{{info}}}'''}}
	</includeonly><noinclude>		</includeonly><noinclude>
	__NOTOC__		__NOTOC__
Line 18:		Line 17:
	However, current practice is that unwanted tips are generally replaced with a redirect to a another relevant tip.		However, current practice is that unwanted tips are generally replaced with a redirect to a another relevant tip.

-	== Usage ==	+	==Usage==
		+	The following is of historical interest only as it is unlikely this template will be needed on more pages because current practice when removing an old tip is to find another tip which covers similar material, and replace the removed tip with a redirect to its replacement.
		+
		+	Original procedure was:
	#<tt><nowiki>{{Removed\|</nowiki></tt>''number''<tt><nowiki>}}</nowiki></tt>		#<tt><nowiki>{{Removed\|</nowiki></tt>''number''<tt><nowiki>}}</nowiki></tt>
	#<tt><nowiki>{{Removed\|</nowiki></tt>''number''<tt>\|info=</tt>''info''<tt><nowiki>}}</nowiki></tt>		#<tt><nowiki>{{Removed\|</nowiki></tt>''number''<tt>\|info=</tt>''info''<tt><nowiki>}}</nowiki></tt>

Script:1643

2012-05-15T18:00:55Z

Comments:

← Older revision		Revision as of 18:00, May 15, 2012
Line 18:		Line 18:
	----		----
	Nice job! Thanks for creating and maintaining this! -- Mike Ellis February 4, 2012		Nice job! Thanks for creating and maintaining this! -- Mike Ellis February 4, 2012
		+	----
		+	Current version 1.6 seems to have unpleasant side effect/bug. For those of us still using Ctrl-N and Ctrl-P to autocomplete, behavior is reversed compared to normal; for example hitting Ctrl-N selects nearest completion that come BEFORE the cursor position, not the one that is AFTER it. This is very confusing and unfortunate. -- Olek Poplavsky May 15 2012
	----		----

Vim Tips Wiki:New tips/201204

2012-05-15T17:36:47Z

Vim DBGp client (for debugging php with XDebug extension): I don't know...delete?

← Older revision		Revision as of 17:36, May 15, 2012
Line 42:		Line 42:
	==[[Vim DBGp client (for debugging php with XDebug extension)]]==		==[[Vim DBGp client (for debugging php with XDebug extension)]]==
	Unusual tip. Is it useful for Vim? Rename it to what? [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)		Unusual tip. Is it useful for Vim? Rename it to what? [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)
		+	:I agree with that assessment! I'm not sure what to do with it. At least we should go ahead and search for Vim plugins to do this...but even then, most of the tip is a generic description of what DBGp is and has very little to do with Vim. I don't want to alienate a user who is obviously willing to do a lot of writing on the wiki, but on the other hand, the tip as mentioned has very little to do with Vim, so I think normally we'd delete it. --[[User:Fritzophrenic\|Fritzophrenic]] 17:36, May 15, 2012 (UTC)

	----		----

80 character line wrap without broken words

2012-05-15T17:15:01Z

Comments: not sure what the point of this tip is

← Older revision		Revision as of 17:15, May 15, 2012
Line 24:		Line 24:

	==Comments==		==Comments==
		+	What problem are you trying to solve? Inserting hard line breaks in a line which is too long never wraps in the middle of the word. Were you having trouble with the 'wrap' option? Did you not know about it's partner 'linebreak' option?

Vim Tips Wiki:New tips/201204

2012-05-15T17:12:58Z

Auto-detect number of cores for parallel built: apparently not signed in

← Older revision		Revision as of 17:12, May 15, 2012
Line 35:		Line 35:
	==[[Auto-detect number of cores for parallel built]]==		==[[Auto-detect number of cores for parallel built]]==
	*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)		*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)
-	:Yes, I like this title (with the typo corrected). --[[Special:Contributions/205.175.225.12\|205.175.225.12]] 17:12, May 15, 2012 (UTC)	+	:Yes, I like this title (with the typo corrected). --[[User:Fritzophrenic\|Fritzophrenic]] 17:12, May 15, 2012 (UTC)

	==[[Highlighting]]==		==[[Highlighting]]==

Vim Tips Wiki:New tips/201204

2012-05-15T17:12:18Z

Auto-detect number of cores for parallel built: yes on title

← Older revision		Revision as of 17:12, May 15, 2012
Line 35:		Line 35:
	==[[Auto-detect number of cores for parallel built]]==		==[[Auto-detect number of cores for parallel built]]==
	*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)		*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)
		+	:Yes, I like this title (with the typo corrected). --[[Special:Contributions/205.175.225.12\|205.175.225.12]] 17:12, May 15, 2012 (UTC)

	==[[Highlighting]]==		==[[Highlighting]]==

VimTip971

2012-05-15T11:54:17Z

Fix redirect for merged tip.

← Older revision		Revision as of 11:54, May 15, 2012
Line 1:		Line 1:
-	#REDIRECT [[Substitute with incrementing numbers]]	+	#REDIRECT [[Making a list of numbers]]

Vim Tips Wiki:New tips/201204

2012-05-15T10:40:34Z

Update.

← Older revision		Revision as of 10:40, May 15, 2012
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	<big>'''New tips April 2012'''</big> <small>[[Vim Tips Wiki:New tips/201203\|Previous]] • [[Vim Tips Wiki:New tips/201205\|Next]]</small>		<big>'''New tips April 2012'''</big> <small>[[Vim Tips Wiki:New tips/201203\|Previous]] • [[Vim Tips Wiki:New tips/201205\|Next]]</small>
-
-	'''This is a place holder – not ready for use. Please wait until the end of April 2012 before editing this page because it is generated by a script, and any edits would be lost.'''

	For each proposed new tip:		For each proposed new tip:
Line 20:		Line 18:
	!align="left"\|Proposed new tip		!align="left"\|Proposed new tip
	!align="center" width="150"\|Current consensus		!align="center" width="150"\|Current consensus
		+	\|-
		+	\| [[Auto-detect number of cores for parallel built]]
		+	\|align="center"\| -
	\|-		\|-
	\| [[Highlighting]]		\| [[Highlighting]]
		+	\|align="center"\| -
		+	\|-
		+	\| [[Vim DBGp client (for debugging php with XDebug extension)]]
	\|align="center"\| -		\|align="center"\| -
	\|}		\|}
Line 28:		Line 32:

	==General comments (not for a specific tip)==		==General comments (not for a specific tip)==
		+
		+	==[[Auto-detect number of cores for parallel built]]==
		+	*Keep. Is title ok? It needs to be renamed to change last word to "build". [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)

	==[[Highlighting]]==		==[[Highlighting]]==
		+	*Keep, I'm developing this. [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)

		+	==[[Vim DBGp client (for debugging php with XDebug extension)]]==
		+	Unusual tip. Is it useful for Vim? Rename it to what? [[User:JohnBeckett\|JohnBeckett]] 10:40, May 15, 2012 (UTC)

	----		----

Vim Tips Wiki:New tips/201205

2012-05-15T10:40:23Z

New month.

New page

__NOTOC__
<big>'''New tips May 2012'''</big> <small>[[Vim Tips Wiki:New tips/201204|Previous]] • [[Vim Tips Wiki:New tips/201206|Next]]</small>

'''This is a place holder – not ready for use. Please wait until the end of May 2012 before editing this page because it is generated by a script, and any edits would be lost.'''

For each proposed new tip:
*Is it worth keeping as a separate tip?
*Should it be merged into an existing tip? Which?
*If it should be kept, is it ready for release? Which points need fixing? Should it be renamed?

Please edit this page (not the talk page) in the appropriate section below the following table.<br />

Alternatively, comments can be posted on the [http://lists.wikia.com/mailman/listinfo/vim-l mailing list].

{| border="1" cellpadding="2"
|-
!align="left"|Proposed new tip
!align="center" width="150"|Current consensus
|-
| [[256 colors setup for console Vim]]
|align="center"| -
|-
| [[80 character line wrap without broken words]]
|align="center"| -
|-
| [[Comment & Uncomment multiple lines in Vim]]
|align="center"| -
|-
| [[Using standard editor shortcuts in Vim]]
|align="center"| -
|}

'''Please add your comment (sign with <tt><nowiki>~~~~</nowiki></tt>) below the appropriate heading. Use <tt><nowiki>----</nowiki></tt> between comments.'''

==General comments (not for a specific tip)==

==[[256 colors setup for console Vim]]==

==[[80 character line wrap without broken words]]==

==[[Comment & Uncomment multiple lines in Vim]]==

==[[Using standard editor shortcuts in Vim]]==

----
[[Category:VimTipProposed]]

Vim Tips Wiki:New tips

2012-05-15T10:37:28Z

Add more.

← Older revision		Revision as of 10:37, May 15, 2012
Line 10:		Line 10:
	===Lists of new tips===		===Lists of new tips===
	''New tips that need to be discussed.''		''New tips that need to be discussed.''
		+	*[[/201206\|June 2012]]
		+	*[[/201205\|May 2012]]
	*[[/201204\|April 2012]]		*[[/201204\|April 2012]]
	*[[/201203\|March 2012]]		*[[/201203\|March 2012]]

Script:1797

2012-05-15T08:27:06Z

Standard format.

← Older revision		Revision as of 08:27, May 15, 2012
Line 1:		Line 1:
-	The svnvimdiff script requires tempfile command. But it doesn't exist in my CentOS and FreeBSD system. So I modified the script:	+	{{ScriptComments\|svnvimdiff: svn diff + vimdiff}}

-	<code>#patch=`tempfile -p $suffix`	+	==Patch for tempfile==
		+	The svnvimdiff script requires tempfile command. But it doesn't exist in my CentOS and FreeBSD system. So I modified the script:
		+	<pre>
		+	#patch=`tempfile -p $suffix`
	#orig=`tempfile -p $suffix`		#orig=`tempfile -p $suffix`
	patch=`mktemp -t $suffix.XXXXXXXXXX`		patch=`mktemp -t $suffix.XXXXXXXXXX`
	orig=`mktemp -t $suffix.XXXXXXXXXX`		orig=`mktemp -t $suffix.XXXXXXXXXX`
-	</code>	+	</pre>
		+
		+	==Comments==

User:Dcai

2012-05-15T04:05:02Z

New user account

Script:1797

2012-05-15T01:41:00Z

Created page with "The svnvimdiff script requires tempfile command. But it doesn't exist in my CentOS and FreeBSD system. So I modified the script: <code>#patch=`tempfile -p $suffix` #orig=`tempfi..."

New page

The svnvimdiff script requires tempfile command. But it doesn't exist in my CentOS and FreeBSD system. So I modified the script:

<code>#patch=`tempfile -p $suffix`
#orig=`tempfile -p $suffix`
patch=`mktemp -t $suffix.XXXXXXXXXX`
orig=`mktemp -t $suffix.XXXXXXXXXX`
</code>

Folding of find locate tar-tf output

2012-05-14T21:29:39Z

TODO work-off

← Older revision		Revision as of 21:29, May 14, 2012
Line 11:		Line 11:
	\|category2=		\|category2=
	}}		}}
-	On Unix systems (*nix, linux, etc.) you can browse output of find, locate, tar -tf, ... in a file-browser like manner:	+	Given a huge file listing as text file, you can use this script to comfortably browse it. Use all fold commands of Vim to open/close parts of the directory tree, as used from standard file managers ( but even more flexible, including moving in fold structure, executing commands on folds ... )
		+
		+	The more, on Unix-like systems you can pipe the output of tools like <tt>find</tt>, <tt>locate</tt>, <tt>tar -t</tt>, ... directly into Vim executing this script by using <tt>-</tt> as filename.
		+
		+	Examples:
	<pre>		<pre>
-	find ~ \| vim -u browser.vim -	+	vim -u browser.vim arch-hurd-i386.files
-	locate "" \| vim -u browser.vim -	+	find . \| vim -u browser.vim -
		+	locate nox \| vim -u browser.vim -
	tar -tzf boost.tar.gz \| vim -u browser.vim -		tar -tzf boost.tar.gz \| vim -u browser.vim -
	</pre>		</pre>

Script:2657

2012-05-14T16:43:56Z

Comments:

← Older revision		Revision as of 16:43, May 14, 2012
Line 19:		Line 19:
	:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)		:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)
	:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)		:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)
		+	::: No, that is not possible. Voom does not configure folding or any other settings in the source buffer. That should be done by filetype-specific plugins. There is the "R" command: in the Tree buffer you can select some nodes and hit "R" to select corresponding Range in the source buffer. Then you can create fold with "zf" if &foldmethod is manual. [[User:Vlad.irnov\|Vlad.irnov]] 16:43, May 14, 2012 (UTC)

Script:2657

2012-05-14T15:43:11Z

Comments:

← Older revision		Revision as of 15:43, May 14, 2012
Line 18:		Line 18:
	I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)		I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)
	:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)		:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)
		+	:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)

Script:2657

2012-05-14T14:26:52Z

Comments:

← Older revision		Revision as of 14:26, May 14, 2012
Line 8:		Line 8:
	I'm having difficulty getting Voom to work with files whose filenames contain spaces. I get the error "Only one file name allowed." Is there a workaround for this?		I'm having difficulty getting Voom to work with files whose filenames contain spaces. I get the error "Only one file name allowed." Is there a workaround for this?
	:Probably you just need to escape it like all file names you edit on the command line, for example, {{tt\|:edit C:\Documents\ and\ Settings\exampleuser\My\ Documents\file.txt}} —[[User:Fritzophrenic\|Fritzophrenic]] 15:35, April 30, 2012 (UTC)		:Probably you just need to escape it like all file names you edit on the command line, for example, {{tt\|:edit C:\Documents\ and\ Settings\exampleuser\My\ Documents\file.txt}} —[[User:Fritzophrenic\|Fritzophrenic]] 15:35, April 30, 2012 (UTC)
		+	:: This has been fixed in version 4.3.[[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)

	* I can't get this plugin to contract/expand notes. As I read it should be "space" or following key combos which I mapped to F10:		* I can't get this plugin to contract/expand notes. As I read it should be "space" or following key combos which I mapped to F10:
Line 16:		Line 17:
	vnoremap <F10> zf		vnoremap <F10> zf
	I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)		I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)
		+	:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)

Script:2657

2012-05-14T13:27:37Z

improvement request

← Older revision		Revision as of 13:27, May 14, 2012
Line 1:		Line 1:
	{{ScriptComments\|VOoM (Vim Outliner of Markers) -- two-pane outliner and related utilities}}		{{ScriptComments\|VOoM (Vim Outliner of Markers) -- two-pane outliner and related utilities}}
		+
		+	==Improvements==
		+	* Voom should also parse TeX-files

	==Comments==		==Comments==

Script:2657

2012-05-14T13:24:01Z

unable to contract/expand

← Older revision		Revision as of 13:24, May 14, 2012
Line 5:		Line 5:
	I'm having difficulty getting Voom to work with files whose filenames contain spaces. I get the error "Only one file name allowed." Is there a workaround for this?		I'm having difficulty getting Voom to work with files whose filenames contain spaces. I get the error "Only one file name allowed." Is there a workaround for this?
	:Probably you just need to escape it like all file names you edit on the command line, for example, {{tt\|:edit C:\Documents\ and\ Settings\exampleuser\My\ Documents\file.txt}} —[[User:Fritzophrenic\|Fritzophrenic]] 15:35, April 30, 2012 (UTC)		:Probably you just need to escape it like all file names you edit on the command line, for example, {{tt\|:edit C:\Documents\ and\ Settings\exampleuser\My\ Documents\file.txt}} —[[User:Fritzophrenic\|Fritzophrenic]] 15:35, April 30, 2012 (UTC)
		+
		+	* I can't get this plugin to contract/expand notes. As I read it should be "space" or following key combos which I mapped to F10:
		+	"Collapse or expand outline
		+	inoremap <F10> <C-O>za
		+	nnoremap <F10> za
		+	onoremap <F10> <C-C>za
		+	vnoremap <F10> zf
		+	I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)

HyperList: Script:4006

2012-05-14T10:29:07Z

deleted "[[HyperList: Script:4006]]" Comments on Script:4006 created in wrong place.

Vim Tips Wiki:New tips

2012-05-14T10:22:39Z

Two done.

← Older revision		Revision as of 10:22, May 14, 2012
Line 16:		Line 16:
	*[[/201112\|December 2011]]		*[[/201112\|December 2011]]
	*[[/201111\|November 2011]]		*[[/201111\|November 2011]]
-	*[[/201110\|October 2011]]
-	*[[/201109\|September 2011]]

	<div style="background:#f0f0f0; margin-top:0.5em; padding:0 10px 0 10px; border:1px solid #888888;">		<div style="background:#f0f0f0; margin-top:0.5em; padding:0 10px 0 10px; border:1px solid #888888;">
	''Discussion on the following has been completed.''		''Discussion on the following has been completed.''
		+	*[[/201110\|October 2011]]
		+	*[[/201109\|September 2011]]
	*[[/201108\|August 2011]]		*[[/201108\|August 2011]]
	*[[/201107\|July 2011]]		*[[/201107\|July 2011]]

Vim Tips Wiki:New tips/201110

2012-05-14T10:00:44Z

All done, roughly merged Java tip to 143 Syntax folding for Java.

← Older revision		Revision as of 10:00, May 14, 2012
Line 2:		Line 2:
	<big>'''New tips October 2011'''</big> <small>[[Vim Tips Wiki:New tips/201109\|Previous]] • [[Vim Tips Wiki:New tips/201111\|Next]]</small>		<big>'''New tips October 2011'''</big> <small>[[Vim Tips Wiki:New tips/201109\|Previous]] • [[Vim Tips Wiki:New tips/201111\|Next]]</small>

-	For each proposed new tip:
-	*Is it worth keeping as a separate tip?
-	*Should it be merged into an existing tip? Which?
-	*If it should be kept, is it ready for release? Which points need fixing? Should it be renamed?
-
-	Please edit this page (not the talk page) in the appropriate section below the following table.<br />
-	<!-- (When discussion finished, delete above and remove begin/end of this comment)
	'''This page is an archive listing tips created in October 2011. Please do not edit this page because discussion has finished. If you have any comments, edit the appropriate tip page.'''		'''This page is an archive listing tips created in October 2011. Please do not edit this page because discussion has finished. If you have any comments, edit the appropriate tip page.'''
-
-	-->
-	Alternatively, comments can be posted on the [http://lists.wikia.com/mailman/listinfo/vim-l mailing list].

	{\| border="1" cellpadding="2"		{\| border="1" cellpadding="2"
Line 23:		Line 13:
	\|-		\|-
	\| [[Syntax Fold For Java]]		\| [[Syntax Fold For Java]]
-	\|align="center"\| '''Merge? Need comments'''	+	\|align="center"\| Merged to [[VimTip143]]
	\|}		\|}
-
-	'''Please add your comment (sign with <tt><nowiki>~~~~</nowiki></tt>) below the appropriate heading. Use <tt><nowiki>----</nowiki></tt> between comments.'''

	==[[Preview current HTML in browser on Linux]]==		==[[Preview current HTML in browser on Linux]]==
Line 33:		Line 21:

	==[[Syntax Fold For Java]]==		==[[Syntax Fold For Java]]==
-	*'''Merged''' We have probably changed our minds. See below. [[User:JohnBeckett\|JohnBeckett]] 11:34, May 6, 2012 (UTC)	+	*'''Merged''' to [[VimTip143]]. We have probably changed our minds. See below. [[User:JohnBeckett\|JohnBeckett]] 11:34, May 6, 2012 (UTC)
	----		----
	'''Keep'''. The tip has a few problems, see my comments. Most people may not care about these problems because they probably always use standard indent.		'''Keep'''. The tip has a few problems, see my comments. Most people may not care about these problems because they probably always use standard indent.

User:Onnuex

2012-05-13T19:37:15Z

New user account

User:CipHuK

2012-05-13T17:44:30Z

New user account

Fix syntax highlighting

2012-05-12T07:12:47Z

Comments:

← Older revision		Revision as of 07:12, May 12, 2012
Line 66:		Line 66:
	==Comments==		==Comments==
	I have tweaked the wording, but haven't considered the content much. The autocmd is a bit extreme (applying to all files). It's not clear why the extract from <tt>syntax/c.vim</tt> is useful. When synching breaks for me, I find that scrolling up/down often fixes it, with no need for the more elaborate ideas here. This doesn't happen often, so I'm not sure what is actually needed, or whether anything helpful can be said about scrolling. [[User:JohnBeckett\|JohnBeckett]] 10:06, May 1, 2011 (UTC)		I have tweaked the wording, but haven't considered the content much. The autocmd is a bit extreme (applying to all files). It's not clear why the extract from <tt>syntax/c.vim</tt> is useful. When synching breaks for me, I find that scrolling up/down often fixes it, with no need for the more elaborate ideas here. This doesn't happen often, so I'm not sure what is actually needed, or whether anything helpful can be said about scrolling. [[User:JohnBeckett\|JohnBeckett]] 10:06, May 1, 2011 (UTC)
		+
		+	Surprisingly, I've actually found :syntax sync fromstart to be faster than only reading back a few hundred lines. This is on a fairly long and complex HTML file with embedded CSS and lots of Javascript.

Script:167

2012-05-11T23:22:53Z

add smylink hack

← Older revision		Revision as of 23:22, May 11, 2012
(2 intermediate revisions not shown)
Line 15:		Line 15:
	:set ff=unix		:set ff=unix
	:wq!		:wq!
		+	</pre>
		+
		+	== Handling AltRoots ==
		+	If you have altroots in your perforce user specification you might
		+	want to add the equivalent of 'alias p4='p4 -d `/bin/pwd`'
		+
		+	I did this by changing this around line 105:
		+
		+	<pre>
		+	"Basic check for p4-enablement
		+	if executable( "p4" )
		+	let s:PerforceExecutable="p4 -d " . getcwd()
		+	else
		+	augroup! perforce
		+	endif
		+	</pre>
		+
		+	== Handling Symlinks ==
		+
		+	Let's say you have a symlink to a file. If you want to edit the file you would normally have to do something like "p4 edit `readlink $file`". This hack does basically that.
		+
		+	Line 122-ish
		+	<pre>
		+	"----------------------------------------------------------------------------
		+	" A wrapper around a p4 command line for the current buffer
		+	"----------------------------------------------------------------------------
		+	function s:P4ShellCommandCurrentBuffer( sCmd )
		+	let filename = resolve(expand( "%:p" ))
		+	return s:P4ShellCommand( a:sCmd . " " . filename )
		+	endfunction
		+	</pre>
		+
		+	== Not Requiring a Changelist ==
		+	This plugin assumes you use the methodology where you have an explicit changelist created for every edit. If you want to use a default changelist, then you need to remove the "-c" options given to a couple commands:
		+
		+	Line 335-ish
		+	<pre>
		+	" let listnum = ""
		+	" let listnum = s:P4GetChangelist( "Current changelists:\n" . s:P4GetChangelists(0) . "\nEnter changelist number: ",
		+	" if listnum == ""
		+	" echomsg "No changelist specified. Edit cancelled."
		+	" return
		+	" endif
		+	" call s:P4ShellCommandCurrentBuffer( action . " -c " . listnum )
		+	call s:P4ShellCommandCurrentBuffer( action )
		+	</pre>
		+
		+	Line 366-ish
		+	<pre>
		+	" let listnum = ""
		+	" let listnum = s:P4GetChangelist( "Current changelists:\n" . s:P4GetChangelists(0) . "\nEnter changelist number
		+	" if listnum == ""
		+	" echomsg "No changelist specified. Delete cancelled."
		+	" return
		+	" endif
		+	" call s:P4ShellCommandCurrentBuffer( "delete -c " . listnum )
		+	call s:P4ShellCommandCurrentBuffer( "delete" )
	</pre>		</pre>

Finding phone numbers

2012-05-11T10:54:53Z

Clean.

← Older revision		Revision as of 10:54, May 11, 2012
Line 1:		Line 1:
-	{{review}}
	{{TipImported		{{TipImported
	\|id=872		\|id=872
	\|previous=869		\|previous=869
	\|next=873		\|next=873
-	\|created=February 10, 2005	+	\|created=2005
	\|complexity=intermediate		\|complexity=intermediate
	\|author=Bertram Scharpf		\|author=Bertram Scharpf
Line 12:		Line 11:
	\|category2=		\|category2=
	}}		}}
-	I have a little script making my modem dial phone numbers. As the numbers are contained in a file I edit with Vim, I call the script with:	+	When editing a file containing phone numbers, the following can be used to dial the number under the cursor. It uses a shell script (not shown) to make a modem dial the number.
-
	<pre>		<pre>
-	func CPhone( ...)	+	" Return phone number under cursor.
-	" Get phone number under cursor	+	" If no number, return an empty string (if argument is zero),
-	let s="[-+./()0-9 ]*"	+	" otherwise throw an error to abort script.
-	let nr=matchstr( getline("."), "\\s*\\zs".s."\\%".col(".")."c".s)	+	function! CPhone(check)
-	let nr=substitute( nr, "\\s\\+$", "", "")	+	let s = '[-+./()0-9 ]*'
-	if nr == "" && a:0 && a:1	+	let nr = matchstr(getline('.'), '\s*\zs'.s.'\%'.col('.').'c'.s)
-	throw "No phone number under cursor."	+	let nr = substitute(nr, '\s\+$', '', '')
		+	if a:check && empty(nr)
		+	throw 'No phone number under cursor.'
	endif		endif
	return nr		return nr
-	endf	+	endfunction

-	let @p=":exec \":!dial '\".CPhone(1).\"'\"\<CR>"	+	let @p = ":execute \":!dial '\".CPhone(1).\"'\"\<CR>"

	augroup LocalUser		augroup LocalUser
-	autocmd BufRead phone* nnoremap <buffer> <CR> :exec ":!dial '".CPhone(1)."'"<CR>	+	autocmd BufRead phone* nnoremap <buffer> <CR> :execute ":!dial '".CPhone(1)."'"<CR>
	augroup END		augroup END
	</pre>		</pre>

-	==Comments==	+	After sourcing the above script:
-	This makes no sense? Does Vim dial the number?	+	*In any file, put the cursor on a phone number and type <tt>@p</tt> to dial the number.
		+	*In any file with a name starting with "<tt>phone</tt>", put the cursor on a phone number and press Enter to dial the number.

-	----	+	The shell script <tt>dial</tt> (not shown) uses its argument to write modem control sequences to <tt>/dev/ttysS0</tt> to cause the modem to dial the phone number. The script removes all non-digit characters from the number, then does something like this shell command:
-	My shell script 'dial' does that. I omitted it because writing "ATDT" sequences to '/dev/ttysS0' has nothing to do with Vim.	+	<pre>
		+	echo -ne 'atdt,<number>;h0\r' >/dev/ttyS0
		+	</pre>

-	Roughly spoken, the script does an ":!echo -ne 'atdt,<number>;h0\r' >/dev/ttyS0", having stripped off all non-digit characters before.	+	==Comments==
-		+	Not many people will have a modem (or the required <tt>dial</tt> script) to try this tip, but there are some useful ideas that might be useful for other applications. [[User:JohnBeckett\|JohnBeckett]] 10:54, May 11, 2012 (UTC)
-	----

256 colors setup for console Vim

2012-05-11T08:24:20Z

Terminal recap:

← Older revision		Revision as of 08:24, May 11, 2012
Line 191:		Line 191:
	\|Preferences→Advanced to set $TERM		\|Preferences→Advanced to set $TERM
	\|-		\|-
-	\|ROXterm	+	\|ROXTerm
	\|yes		\|yes
	\|no		\|no

Use Vim like an IDE

2012-05-11T08:17:53Z

Code Browsing:

← Older revision		Revision as of 08:17, May 11, 2012
Line 32:		Line 32:
	===Code Browsing===		===Code Browsing===
	*{{script\|id=273\|text=taglist}} gives you an outline of the source you're viewing		*{{script\|id=273\|text=taglist}} gives you an outline of the source you're viewing
-	*{{script\|id=3465\|text=Tagbar}} similar to taglist but can order tags by scope	+	*{{script\|id=3465\|text=Tagbar}} similar to taglist but can order tags by scope. Recommend for programming languages with classes, e.g. C++, Java, Python.
	*{{script\|id=3221\|text=Indexer}} generates tags for all files in project automatically and keeps tags up-to-date. Using ctags. Works well with project plugin or independently.		*{{script\|id=3221\|text=Indexer}} generates tags for all files in project automatically and keeps tags up-to-date. Using ctags. Works well with project plugin or independently.
	*{{script\|id=2368\|text=CCTree}} is a Call-Tree Explorer, Cscope based source-code browser, and code flow analyzer.		*{{script\|id=2368\|text=CCTree}} is a Call-Tree Explorer, Cscope based source-code browser, and code flow analyzer.

Integrate gvim with Visual Studio

2012-05-10T17:03:36Z

Making Visual Studio's Editor Work like Vim:

← Older revision		Revision as of 17:03, May 10, 2012
(One intermediate revision not shown)
Line 27:		Line 27:
	[http://www.viemu.com/ ViEmu for Visual Studio] is commercial software that emulates Vim editing commands within Visual Studio (Vim is not used).		[http://www.viemu.com/ ViEmu for Visual Studio] is commercial software that emulates Vim editing commands within Visual Studio (Vim is not used).

-	[http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 VsVim] is an open source Vim emulator (code at https://github.com/jaredpar/VsVim ). It is only available for Visual Studio 2010 (with support for 2011 planned), and as with viemu does not use Vim.	+	[http://visualstudiogallery.msdn.microsoft.com/59ca71b3-a4a3-46ca-8fe1-0e90e3f79329 VsVim] is an open source Vim emulator (code at https://github.com/jaredpar/VsVim ). It is only available for all editons of Visual Studio 2010 (with support for 2011 planned) excluding Express Edition, and as with viemu does not use Vim.

	==Vim as an External Tool==		==Vim as an External Tool==

Integrate gvim with Visual Studio

2012-05-10T14:32:41Z

Undo revision 33330 by 144.92.14.71 (talk)

← Older revision		Revision as of 14:32, May 10, 2012
(2 intermediate revisions not shown)
Line 40:		Line 40:
	If you have other settings you'd like to apply (like ''normal zz'' to centre the cursor or updating ''path'' for '':[[Project_browsing_using_find\|find]]'', then you can put them in ''~/.vim/visualstudioinvoke.vim'' and add ''+"runtime visualstudioinvoke.vim"'' before ''$(ItemFileName)''.		If you have other settings you'd like to apply (like ''normal zz'' to centre the cursor or updating ''path'' for '':[[Project_browsing_using_find\|find]]'', then you can put them in ''~/.vim/visualstudioinvoke.vim'' and add ''+"runtime visualstudioinvoke.vim"'' before ''$(ItemFileName)''.

-	'''The Shortcut:''' In Visual Studio, Tools -> Options -> Keyboard:	+	'''The Shortcut:''' In Visual Studio, Tools -> Options -> Environment -> Keyboard:
	*''Command:'' ExternalCommand1 (it's easiest if you move your Vim external tool to be the first, otherwise use the correct index).		*''Command:'' ExternalCommand1 (it's easiest if you move your Vim external tool to be the first, otherwise use the correct index).
	*''Shortcut key:'' <F1>		*''Shortcut key:'' <F1>

Commenting out a range of lines

2012-05-10T11:30:03Z

Reverted edits by 222.247.172.70 (talk | block) to last version by Fritzophrenic

← Older revision		Revision as of 11:30, May 10, 2012
Line 144:		Line 144:

	[[User:Maedox\|Maedox]] 15:18, January 13, 2011 (UTC)		[[User:Maedox\|Maedox]] 15:18, January 13, 2011 (UTC)
-	[[Category:source:http://www.diablo3-us.com source:http://www.diabloshoping.com]]

← Older revision		Revision as of 12:15, May 16, 2012
Line 228:		Line 228:
	*{{script\|id=54\|text=ConvertBase}} plugin to convert to/from various numeric bases		*{{script\|id=54\|text=ConvertBase}} plugin to convert to/from various numeric bases
	*[http://www.stringfunction.com/hex-decimal.html Convert Hexadecimal to Decimal Number] online tool to convert hex to dec		*[http://www.stringfunction.com/hex-decimal.html Convert Hexadecimal to Decimal Number] online tool to convert hex to dec
		+	* [https://www.codeproject.com/Articles/350252/From-one-to-another-number-system/ From one to another number system], ''article related to creating computer program for conversion of number from one to another number system with source code written in C#''

	==Comments==		==Comments==

← Older revision		Revision as of 01:05, May 16, 2012
Line 168:		Line 168:
	</pre>		</pre>

-	See [[VimTip453\|Use Taglist with LaTeX files]] for another example that adds support for LaTeX.	+	Other examples, including for LaTeX, are in the [http://vim-taglist.sourceforge.net/extend.html documentation] for the {{script\|id=273\|text=taglist}} plugin.

	==Creating a tags file using ctags==		==Creating a tags file using ctags==
Line 205:		Line 205:
	*[[VimTip79\|79 Use grep to get a clickable list of function names]]		*[[VimTip79\|79 Use grep to get a clickable list of function names]]
	*[[VimTip404\|404 Tags for Mixed Assembly and C]]		*[[VimTip404\|404 Tags for Mixed Assembly and C]]
-	*[[VimTip453\|453 Use Taglist with LaTeX files]]
	*[[VimTip558\|558 Using TagList for ANT build files]]		*[[VimTip558\|558 Using TagList for ANT build files]]
	*[[VimTip568\|568 Use temporary tags file when browsing new source]]		*[[VimTip568\|568 Use temporary tags file when browsing new source]]

← Older revision		Revision as of 16:43, May 14, 2012
Line 19:		Line 19:
	:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)		:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)
	:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)		:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)
		+	::: No, that is not possible. Voom does not configure folding or any other settings in the source buffer. That should be done by filetype-specific plugins. There is the "R" command: in the Tree buffer you can select some nodes and hit "R" to select corresponding Range in the source buffer. Then you can create fold with "zf" if &foldmethod is manual. [[User:Vlad.irnov\|Vlad.irnov]] 16:43, May 14, 2012 (UTC)

← Older revision		Revision as of 15:43, May 14, 2012
Line 18:		Line 18:
	I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)		I've got following plugins installed: vim-paster (upload documents to pastebin-services e.g. via :%Paste), vim-nerdcommenter (toggle comments), vim-nerdtree (file explorer), vim-taglist (source code browser), vim-live-latex-preview, vim-supertab vim-spell-de. I hope these plugins won't conflict vim-voom in this aspect?! --[[Special:Contributions/79.227.131.123\|79.227.131.123]] 13:24, May 14, 2012 (UTC)
	:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)		:This is strange. If you see folds in the Tree buffer then you should be able to toggle the current node's folding with <Space>. Standard Vim commands za, zM, zR, etc. should work as usual. [[User:Vlad.irnov\|Vlad.irnov]] 14:26, May 14, 2012 (UTC)
		+	:: Oh okay, maybe I'm mistaken with that. I thought one could also contract the node of the main text buffer. E.g. if I have an function in Python I would like to contract and expand the content of it. Isn't that possible with this plugin? --[[User:Onnuex\|Onnuex]] 15:43, May 14, 2012 (UTC)

← Older revision		Revision as of 10:22, May 14, 2012
Line 16:		Line 16:
	*[[/201112\|December 2011]]		*[[/201112\|December 2011]]
	*[[/201111\|November 2011]]		*[[/201111\|November 2011]]
-	*[[/201110\|October 2011]]
-	*[[/201109\|September 2011]]

	<div style="background:#f0f0f0; margin-top:0.5em; padding:0 10px 0 10px; border:1px solid #888888;">		<div style="background:#f0f0f0; margin-top:0.5em; padding:0 10px 0 10px; border:1px solid #888888;">
	''Discussion on the following has been completed.''		''Discussion on the following has been completed.''
		+	*[[/201110\|October 2011]]
		+	*[[/201109\|September 2011]]
	*[[/201108\|August 2011]]		*[[/201108\|August 2011]]
	*[[/201107\|July 2011]]		*[[/201107\|July 2011]]