Clang Complete - Revision history

Pew at 08:18, 3 January 2019

2019-01-03T08:18:16Z

Pew: Undo revision 4263 by imported>Pew (talk)

2019-01-03T08:18:03Z

Undo revision 4263 by [[Special:Contributions/imported>Pew|imported>Pew]] ([[User talk:imported>Pew|talk]])

imported>Pew: Replaced content with "Category:Pending deletion"

2018-01-03T16:42:33Z

Replaced content with "Category:Pending deletion"

imported>Pew at 08:49, 2 January 2018

2018-01-02T08:49:27Z

150.135.211.199 at 01:16, 10 April 2014

2014-04-10T01:16:27Z

imported>Mjh: Categorization

2013-02-03T06:43:28Z

Categorization

imported>Mutantmonkey: Reverted edits by 91.121.27.33 (talk) to last revision by 198.82.99.126

2012-09-14T11:02:36Z

Reverted edits by 91.121.27.33 (talk) to last revision by 198.82.99.126

Show changes

91.121.27.33: Tips on Finding a Trustworthy Realtor

2012-09-14T08:52:58Z

Tips on Finding a Trustworthy Realtor

Show changes

198.82.99.126: /* Other Include Paths */

2012-09-13T17:08:37Z

‎Other Include Paths

198.82.99.126: /* Installation */

2012-09-13T17:07:05Z

‎Installation

@@ Line 1: / Line 1: @@
 == Clang Complete ==
 Clang Complete is an addon to the popular text editor [[vim]]. It allows the user to use clang to do a lightweight compile/parse of their code, in order to allow extremely accurate code autocompletion. Alternatives out there ([[gcc_complete]]/[[ctags]]) either use hackish methods (modified compilers) or do manual parsing of the file. Clang was built with ease of IDE integration built-in, so Clang Complete simply builds on that feature.
@@ Line 90: / Line 88: @@
 [[Category:Howtos]]
 [[Category:Software]]

← Older revision		Revision as of 08:18, 3 January 2019
Line 1:		Line 1:
−	[[Category:~~Pending deletion~~]]	+	TODO: How does this relate to VTLUUG?
		+
		+	== Clang Complete ==
		+	Clang Complete is an addon to the popular text editor [[vim]]. It allows the user to use clang to do a lightweight compile/parse of their code, in order to allow extremely accurate code autocompletion. Alternatives out there ([[gcc_complete]]/[[ctags]]) either use hackish methods (modified compilers) or do manual parsing of the file. Clang was built with ease of IDE integration built-in, so Clang Complete simply builds on that feature.
		+
		+	== Installation ==
		+	First off, you obviously need to install [[clang]], the C/C++/ObjectiveC compiler. Use your favorite package manager (or compilation tools) to make/install clang.
		+
		+	The installation of Clang Complete requires a version of vim that supports python(3) addons. At the moment, Arch Linux's default vim build lacks the ability to use python extensions, and gvim lacks support for python3. In order to check if your vim install supports these, do:
		+
		+	<pre>vim --version \| grep -i python</pre>
		+
		+	If you get a result and it contains the following, you can skip reinstalling python. Otherwise, you have to reinstall vim. (Note: if you see this with -, as in -python/dyn -python3/dyn, you have to reinstall)
		+
		+	<pre>+python/dyn +python3/dyn</pre>
		+
		+	Now we get to recompile vim from source. If you have a fun distro-specific tool such as [[ABS]], feel free to use that. Otherwise, pull the sources from http://www.vim.org/sources.php and follow along.
		+
		+	You can compile/install vim as usual. The sole special thing that need be done for this compilation is that, when you call ./configure, you need to ensure the following flags are present:
		+	<pre>--enable-python3interp=dynamic --enable-pythoninterp=dynamic</pre>
		+
		+	and the following are absent
		+	<pre>--disable-python3interp --disable-pythoninterp</pre>
		+
		+	Otherwise Clang Complete will fail.
		+
		+
		+	Now that we have the necessary version of vim installed, you need to clone the most recent sources of Clang Complete into a new directory using the following command:
		+	<pre>git clone https://github.com/Rip-Rip/clang_complete.git</pre>
		+
		+	Now to install it, do:
		+	<pre>cd clang_complete
		+	make install
		+	</pre>
		+
		+	And it should now be installed. Before you rush off and see how great it is, I suggest you look at the documentation to see what configuration options you want. Personally, I use the following:
		+	<pre>
		+	" Clang Complete Settings
		+	let g:clang_use_library=1
		+	" if there's an error, allow us to see it
		+	let g:clang_complete_copen=1
		+	let g:clang_complete_macros=1
		+	let g:clang_complete_patterns=0
		+	" Limit memory use
		+	let g:clang_memory_percent=70
		+	" Remove -std=c++11 if you don't use C++ for everything like I do.
		+	let g:clang_user_options=' -std=c++11 \|\| exit 0'
		+	" Set this to 0 if you don't want autoselect, 1 if you want autohighlight,
		+	" and 2 if you want autoselect. 0 will make you arrow down to select the first
		+	" option, 1 will select the first option for you, but won't insert it unless you
		+	" press enter. 2 will automatically insert what it thinks is right. 1 is the most
		+	" convenient IMO, and it defaults to 0.
		+	let g:clang_auto_select=1
		+
		+	set conceallevel=2
		+	set concealcursor=vin
		+	let g:clang_snippets=1
		+	let g:clang_conceal_snippets=1
		+	" The single one that works with clang_complete
		+	let g:clang_snippets_engine='clang_complete'
		+	</pre>
		+
		+	Now you're all set and ready to go! Enjoy autocomplete
		+
		+	== Other Include Paths ==
		+	So, you want to use something other than the standard libraries? Maybe Qt? Maybe Gtk? You've probably noticed autocomplete works for none of these without special configuration.
		+
		+	In order to specify other folders for autocomplete to search for headers, you need to place them (one per line, prefixed directly with '-I') into a .clang_complete file in the current working directory. (This file directly appends each line to the clang command, so if you need to use the C99 standard for a project, for example, you can do -std=c99 on a line of its own).
		+
		+	An example of this file using the c++0x standard, and including Qt headers and libs from the current directory, is:
		+	<pre>
		+	-std=c++0x
		+	-I/usr/include/QtGui/
		+	-I/usr/include/QtCore/
		+	-I.
		+	</pre>
		+
		+	== Troubleshooting ==
		+	Clang Complete depends on a mostly working environment to work. It will generally not autocomplete from broken header files, etc. So, type the following into vim to see if it's your code or clang complete that is messed up:
		+	<pre>#include <string>
		+
		+	int main()
		+	{
		+	std::string s;
		+	s.
		+	}
		+	</pre>
		+
		+	If autocomplete pops up when you press the '.', it's your code/configuration that's not functioning properly. If autocomplete fails to pop up even when you press <C-x><C-u> (autocomplete), then the install probably has an issue. See [Other Include Paths] for more information if Clang Complete isn't working on a certain library.
		+
		+	[[Category:Howtos]]
		+	[[Category:Programming]]
		+	[[Category:Software]]

← Older revision		Revision as of 16:42, 3 January 2018
Line 1:		Line 1:
−	~~TODO: How does this relate to VTLUUG?~~	+	[[Category:Pending deletion]]
−
−	~~== Clang Complete ==~~
−	Clang Complete is an addon to the popular text editor [[vim]]. It allows the user to use clang to do a lightweight compile/parse of their code, in order to allow extremely accurate code autocompletion. Alternatives out there ([[gcc_complete]]/[[ctags]]) either use hackish methods (modified compilers) or do manual parsing of the file. Clang was built with ease of IDE integration built-in, so Clang Complete simply builds on that feature.
−
−	~~== Installation ==~~
−	~~First off, you obviously need to install [[clang]], the C/C++/ObjectiveC compiler. Use your favorite package manager (or compilation tools) to make/install clang.~~
−
−	The installation of Clang Complete requires a version of vim that supports python(3) addons. At the moment, Arch Linux's default vim build lacks the ability to use python extensions, and gvim lacks support for python3. In order to check if your vim install supports these, do:
−
−	~~<pre>vim --version \| grep -i python</pre>~~
−
−	If you get a result and it contains the following, you can skip reinstalling python. Otherwise, you have to reinstall vim. (Note: if you see this with -, as in -python/dyn -python3/dyn, you have to reinstall)
−
−	~~<pre>+python/dyn +python3/dyn</pre>~~
−
−	Now we get to recompile vim from source. If you have a fun distro-specific tool such as [[ABS]], feel free to use that. Otherwise, pull the sources from http://www.vim.org/sources.php and follow along.
−
−	~~You can compile/install vim as usual. The sole special thing that need be done for this compilation is that, when you call ./configure, you need to ensure the following flags are present:~~
−	~~<pre>--enable-python3interp=dynamic --enable-pythoninterp=dynamic</pre>~~
−
−	~~and the following are absent~~
−	~~<pre>--disable-python3interp --disable-pythoninterp</pre>~~
−
−	~~Otherwise Clang Complete will fail.~~
−
−
−	~~Now that we have the necessary version of vim installed, you need to clone the most recent sources of Clang Complete into a new directory using the following command:~~
−	~~<pre>git clone https://github.com/Rip-Rip/clang_complete.git</pre>~~
−
−	~~Now to install it, do:~~
−	~~<pre>cd clang_complete~~
−	~~make install~~
−	~~</pre>~~
−
−	~~And it should now be installed. Before you rush off and see how great it is, I suggest you look at the documentation to see what configuration options you want. Personally, I use the following:~~
−	~~<pre>~~
−	~~" Clang Complete Settings~~
−	~~let g:clang_use_library=1~~
−	~~" if there's an error, allow us to see it~~
−	~~let g:clang_complete_copen=1~~
−	~~let g:clang_complete_macros=1~~
−	~~let g:clang_complete_patterns=0~~
−	~~" Limit memory use~~
−	~~let g:clang_memory_percent=70~~
−	~~" Remove -std=c++11 if you don't use C++ for everything like I do.~~
−	~~let g:clang_user_options=' -std=c++11 \|\| exit 0'~~
−	~~" Set this to 0 if you don't want autoselect, 1 if you want autohighlight,~~
−	~~" and 2 if you want autoselect. 0 will make you arrow down to select the first~~
−	~~" option, 1 will select the first option for you, but won't insert it unless you~~
−	~~" press enter. 2 will automatically insert what it thinks is right. 1 is the most~~
−	~~" convenient IMO, and it defaults to 0.~~
−	~~let g:clang_auto_select=1~~
−
−	~~set conceallevel=2~~
−	~~set concealcursor=vin~~
−	~~let g:clang_snippets=1~~
−	~~let g:clang_conceal_snippets=1~~
−	~~" The single one that works with clang_complete~~
−	~~let g:clang_snippets_engine='clang_complete'~~
−	~~</pre>~~
−
−	~~Now you're all set and ready to go! Enjoy autocomplete~~
−
−	~~== Other Include Paths ==~~
−	~~So, you want to use something other than the standard libraries? Maybe Qt? Maybe Gtk? You've probably noticed autocomplete works for none of these without special configuration.~~
−
−	In order to specify other folders for autocomplete to search for headers, you need to place them (one per line, prefixed directly with '-I') into a .clang_complete file in the current working directory. (This file directly appends each line to the clang command, so if you need to use the C99 standard for a project, for example, you can do -std=c99 on a line of its own).
−
−	~~An example of this file using the c++0x standard, and including Qt headers and libs from the current directory, is:~~
−	~~<pre>~~
−	~~-std=c++0x~~
−	~~-I/usr/include/QtGui/~~
−	~~-I/usr/include/QtCore/~~
−	~~-I.~~
−	~~</pre>~~
−
−	~~== Troubleshooting ==~~
−	Clang Complete depends on a mostly working environment to work. It will generally not autocomplete from broken header files, etc. So, type the following into vim to see if it's your code or clang complete that is messed up:
−	~~<pre>#include <string>~~
−
−	~~int main()~~
−	{
−	~~std::string s;~~
−	s.
−	}
−	~~</pre>~~
−
−	If autocomplete pops up when you press the '.', it's your code/configuration that's not functioning properly. If autocomplete fails to pop up even when you press <C-x><C-u> (autocomplete), then the install probably has an issue. See [Other Include Paths] for more information if Clang Complete isn't working on a certain library.
−
−	~~[[Category:Howtos]]~~
−	~~[[Category:Programming]]~~
−	~~[[Category:Software]]~~
−	[[Category:~~Needs restoration~~]]

@@ Line 1: / Line 1: @@
 == Clang Complete ==
 Clang Complete is an addon to the popular text editor [[vim]]. It allows the user to use clang to do a lightweight compile/parse of their code, in order to allow extremely accurate code autocompletion. Alternatives out there ([[gcc_complete]]/[[ctags]]) either use hackish methods (modified compilers) or do manual parsing of the file. Clang was built with ease of IDE integration built-in, so Clang Complete simply builds on that feature.
@@ Line 90: / Line 92: @@
 [[Category:Programming]]
 [[Category:Software]]

@@ Line 16: / Line 16: @@
 You can compile/install vim as usual. The sole special thing that need be done for this compilation is that, when you call ./configure, you *need* to ensure the following flags are present:
-<pre>--enable-python3interp --enable-pythoninterp</pre>
+<pre>--enable-python3interp=dynamic --enable-pythoninterp=dynamic</pre>
 and the following are absent
-<pre>--diable-python3interp --disable-pythoninterp</pre>
+<pre>--disable-python3interp --disable-pythoninterp</pre>
 Otherwise Clang Complete will fail.

← Older revision		Revision as of 06:43, 3 February 2013
Line 86:		Line 86:

	If autocomplete pops up when you press the '.', it's your code/configuration that's not functioning properly. If autocomplete fails to pop up even when you press <C-x><C-u> (autocomplete), then the install probably has an issue. See [Other Include Paths] for more information if Clang Complete isn't working on a certain library.		If autocomplete pops up when you press the '.', it's your code/configuration that's not functioning properly. If autocomplete fails to pop up even when you press <C-x><C-u> (autocomplete), then the install probably has an issue. See [Other Include Paths] for more information if Clang Complete isn't working on a certain library.
		+
		+	[[Category:Howtos]]
		+	[[Category:Programming]]
		+	[[Category:Software]]

@@ Line 66: / Line 66: @@
 In order to specify other folders for autocomplete to search for headers, you need to place them (one per line, prefixed directly with '-I') into a .clang_complete file in the current working directory. (This file directly appends each line to the clang command, so if you need to use the C99 standard for a project, for example, you can do -std=c99 on a line of its own).
-An example of this file using the c++0x standard, and including Qt libraries and libs from the current directory, is:
+An example of this file using the c++0x standard, and including Qt headers and libs from the current directory, is:
 <pre>
 -std=c++0x
@@ Line 73: / Line 73: @@
 -I.
 </pre>
 == Troubleshooting ==
 Clang Complete depends on a mostly working environment to work. It will generally not autocomplete from broken header files, etc. So, type the following into vim to see if it's your code or clang complete that is messed up:

@@ Line 13: / Line 13: @@
 <pre>+python/dyn +python3/dyn</pre>
-Now we get to recompile vim from source. If you have a fun distro-specific tool such as [[ABS]], feel free to use that. Otherwise, pull the sources from [[[http://www.vim.org/sources.php]]] and follow along.
+Now we get to recompile vim from source. If you have a fun distro-specific tool such as [[ABS]], feel free to use that. Otherwise, pull the sources from http://www.vim.org/sources.php and follow along.
 You can compile/install vim as usual. The sole special thing that need be done for this compilation is that, when you call ./configure, you *need* to ensure the following flags are present: