Skip to content

Commit 295922e

Browse files
andoriyujyn514
authored andcommitted
remove ctag section
1 parent 8f98dac commit 295922e

File tree

1 file changed

+0
-27
lines changed

1 file changed

+0
-27
lines changed

src/building/suggested.md

-27
Original file line numberDiff line numberDiff line change
@@ -71,33 +71,6 @@ Task] instead:
7171

7272
[Build Task]: https://code.visualstudio.com/docs/editor/tasks
7373

74-
## Configuring `ctags`
75-
76-
One of the challenges with rustc is that the RLS can't handle it, since it's a
77-
bootstrapping compiler. This makes code navigation difficult. One solution is to
78-
use `ctags`.
79-
80-
`ctags` has a long history and several variants. Exuberant Ctags seems to be
81-
quite commonly distributed but it does not have out-of-box Rust support. Some
82-
distributions seem to use [Universal Ctags][utags], which is a maintained fork
83-
and does have built-in Rust support.
84-
85-
The following script can be used to set up Exuberant Ctags:
86-
[https://github.com/nikomatsakis/rust-etags][etags].
87-
88-
`ctags` integrates into emacs and vim quite easily. The following can then be
89-
used to build and generate tags:
90-
91-
```console
92-
$ rust-ctags src/lib* && ./x.py build <something>
93-
```
94-
95-
This allows you to do "jump-to-def" with whatever functions were around when
96-
you last built, which is ridiculously useful.
97-
98-
[etags]: https://github.com/nikomatsakis/rust-etags
99-
[utags]: https://github.com/universal-ctags/ctags
100-
10174
## Check, check, and check again
10275

10376
When doing simple refactorings, it can be useful to run `./x.py check`

0 commit comments

Comments
 (0)