blocks|key|3162017|text|我正确地设置了path，然后将find用于大多数事情。有时我只是依赖于标签。标签允许制表符补全，但find不允许。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3162018|在我的vimrc中：|3162019|set+path=src/**;c:/work,scripts/**;c:/work|code-block|syntax|javascript|3162020|然后|3162021|:find+foobar.cpp|3162022|如果它存在于我当前目录附近的某个src/文件夹下(递归向上查找，直到命中c:/+foobar.cpp+)，则会显示它，然后检查脚本层次结构。|3162023|:tag+FooBar|3162024|直接跳到该类的定义，因为我使用ctag来标记我的C源代码，并且我还编写了一个脚本来为内部DSL生成标记。|3162025|entityMap^0|7|4|F|4|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|15|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|17|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|18|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|19|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|X|$]]

I set <code>path</code> properly then use <code>find</code> for most things. Sometimes I just rely on the tags. The tags allow tab-completion, but find does not.

in my vimrc:

<pre><code>set path=src/**;c:/work,scripts/**;c:/work
</code></pre>

then

<pre><code>:find foobar.cpp
</code></pre>

Will turn up foobar.cpp if it exists under a src/ folder somewhere around my current directory (recursing up to find it until c:/work is hit) and then check the scripts hierarchy.

<pre><code>:tag FooBar
</code></pre>

just jumps me right to the definition of that class, as I use ctags to tag my C source code and I also wrote a script to generate tags for an in-house DSL.

blocks|key|4572379|text|我使用NerdTree，我可以用它管理几乎所有的事情。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4572380|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/scrooloose/nerdtree^0|3|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I use <a href="https://github.com/scrooloose/nerdtree" rel="nofollow">NerdTree</a> and I can manage almost everything with it.

blocks|key|3161909|text|我通常使用的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161910|用于打开新文件的|3161911|：带制表符完成的:e，或:Ex+(打开当前文件目录中的资源管理器)。用于在缓冲区列表(:ls)中的文件之间跳转的|ordered-list-item|offset|length|style|CODE|3161912|：标记列表插件，或:b及其制表符完成。请注意，对于:b，制表符完成适用于子字符串。例如，如果buffer+list中有两个文件:+module.h和module.cpp，则可以键入:b+cpp，tab将完成module.cpp。非常方便！|3161913|3161914|对于制表符补全，我也推荐必备的野生菜单(:set+wildmenu+:set+wildmode=full)|3161915|entityMap^0|0|0|8|2|C|3|17|3|0|9|2|P|2|2I|6|0|0|K|D|Y|I|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|T|8|@$G|U|H|V|I|J]|$G|W|H|X|I|J]|$G|Y|H|Z|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@$G|11|H|12|I|J]|$G|13|H|14|I|J]|$G|15|H|16|I|J]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@$G|19|H|1A|I|J]|$G|1B|H|1C|I|J]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Q|$]]

What I'm using generally:

<ol>
<li>For opening new files: <code>:e</code> with tab-completion, or <code>:Ex</code> (open explorer in the directory of current file).</li>
<li>For jumping between files in the buffer list (<code>:ls</code>): the taglist plugin, or <code>:b</code> and its tab-completion. Note that for <code>:b</code>, tab-completion works for substrings. For example, if you have two files in buffer list: module.h and module.cpp, you can type <code>:b cpp</code> and tab will complete module.cpp. Very handy!</li>
</ol>

For tab-completion I also recommend the must-have wildmenu (<code>:set wildmenu</code> <code>:set wildmode=full</code>)

blocks|key|1100817|text|老实说？我很少按名称打开代码文件。在大多数情况下，我使用ctag和ctrl-]在文件之间导航(接着导航到文件之间的定义)，以及ctrl-t、ctrl-i和ctrl-o。在极少数情况下，我想按名称打开文件，这就是shell/explorer窗口的作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1100818|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Honestly? I rarely open a code file by name. For the most part I use ctags with ctrl-] to navigate around the files (following through to definitions between files), along with ctrl-t, ctrl-i, and ctrl-o. On the rare occasions I want to open a file by name, that's what a shell/explorer window is for.

blocks|key|4572321|text|许多人只是在bash命令行中使用普通的文件资源管理器，或者Windows资源管理器或其他任何工具，并根据需要打开文件。对于导航现有的源代码树，cscope和ctag都非常有用。我发现project+plugin对于类似集成开发环境的项目和文件导航非常有用:它往往是我导航源代码树的主要方式。结合使用ctag、cscope、command-t和ack，导航通常可以非常快。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|4572322|entityMap|0|LINK|mutability|MUTABLE|url|http://www.vim.org/scripts/script.php?script_id=69^0|2J|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Many people just use the normal file explorer in the bash command line or Windows Explorer or whatever and open files as necessary. For navigating existing source trees, cscope and ctags are both very useful. I find the <a href="http://www.vim.org/scripts/script.php?script_id=69" rel="nofollow">project plugin</a> really useful for IDE-like navigation of projects and files: it tends to be the main way I navigate my source tree. Combined with ctags, cscope, command-t and ack, navigation can generally be very fast.

blocks|key|3161867|text|“传统意义上的？”我已经使用:Sex很多年了。这和文件名的制表符补全并不会让它变得那么糟糕。即使在8或9深度的目录嵌套中，使用/mo跳转到目录"models"，然后点击o将其打开...等等。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3161868|我已经在一台机器上安装了Command-T，这很好，但是没有什么能比得上netrw的可靠性|3161869|entityMap^0|E|4|1R|3|2C|1|0|10|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|I|$]]

"Traditionally?" I've used <code>:Sex</code> for years. That and tab-completion for file-names doesn't make it that bad. Even in directory nestings 8 or 9 deep, using <code>/mo</code> to jump to the directory "models", hit then <code>o</code> to open it... etc etc.

I have installed Command-T on one machine, which is nice, but nothing beats the reliability of <code>netrw</code>

blocks|key|3161958|text|我也只使用基本的文件和缓冲区命令来管理我的项目。然而，我发现下面的插件也让事情变得更容易：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3161959|3161960|模糊查找器(使打开文件更愉快)|unordered-list-item|3161961|NERDTree+(已经提到，这是一个很好的目录资源管理器视图)|3161962|标记列表(用于在文件)|3161963|alternate.vim中导航(对于具有相应文件类型的编程语言，如C%2B%2B和.h+.cpp+|3161964|(使跟踪缓冲区更容易))|3161965|此外，只需将:bn和:bp重新映射为更容易的值，就可以使切换缓冲区更令人愉快。例如：|3161966|nmap+<C-n>+:bn<cr>|offset|length|style|CODE|3161967|nmap+<C-p>+:bp<cr>|3161968|最后，它没有被提及，但它与项目管理类型的东西有关，请务必查看内置的编译-编辑东西|3161969|3161970|：帮助快速修复|3161971|3161972|我发现很多第一次来vim的人都没有马上注意到它。|3161973|entityMap^0|0|0|0|0|0|0|0|0|0|I|0|0|I|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1A|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|1B|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|1C|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1D|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1E|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1F|8|@$R|1G|S|1H|T|U]]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@$R|1J|S|1K|T|U]]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1L|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]|$1|10|3|11|5|E|7|1N|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|1P|8|@]|9|@]|A|$]]|$1|15|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|16|$]]

I also only use the basic file and buffer commands for managing my projects. However, I found the following plugins make things easier as well:

<ul>
<li>Fuzzy Finder ( makes opening files more pleasant )</li>
<li>NERDTree ( already mentioned, does a nice directory explorer view )</li>
<li>Taglist ( useful for navigating in a file )</li>
<li>alternate.vim ( useful for programming languages such as C++ with corresponding file types .h and .cpp )</li>
<li>MiniBufExplorer ( makes keeping track of buffers easier )</li>
</ul>

Also, simply remapping :bn and :bp to something easier makes switching buffers more pleasant. For example: 

<code>nmap &lt;C-n&gt; :bn&lt;cr&gt;</code>

<code>nmap &lt;C-p&gt; :bp&lt;cr&gt;</code>

Lastly, it wasn't mentioned but it is related to project management type stuff, make sure to check out the built in compile-edit stuff

<ul>
<li>:help quickfix</li>
</ul>

I find that a lot people first coming to vim do not notice it right away.

blocks|key|1100882|text|我理解现在可能太晚了，但我希望这对某些人有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1100883|我们有一个相对较大的项目，大约有数千个C/C%2B%2B代码，php和shell脚本，配置文件和其他东西。|1100884|要浏览文件，我使用以下选项。|1100885|对于第一个，我使用简单的grep包装器，存储在我的.vimrc中来查找文件中的特定字符串：|offset|length|style|CODE|1100886|function+MyGrep(+pattern,+path,+case,+whole+)
++++execute+"normal!+GoSearch+text+"+.+a:pattern+.+"+in+"+.+a:path+.+"+and+subdirs,+case:+"+.a:case.+"+whole:+".a:whole
++++"E+-+extended+regexp,+l+-+display+filenames+only,+r+-+search+recursively
++++let+l:keys+=+"Elr"
++++if+a:case+==+0
++++++++"case-sensitive
++++++++let+l:keys+=+l:keys+.+"i"
++++endif
++++if+a:whole+!=+0
++++++++"whole+words+only
++++++++let+l:keys+=+l:keys+.+"w"
++++endif
++++let+l:cmd+=+"r!grep+-"+.+keys+.+"+-e+\""+.+a:pattern+."\"+"
++++let+l:cmd2+=+a:path+.+"+--exclude=*.ncb+--exclude=*.o+--exclude=*.d+--exclude-dir=.svn+--exclude-dir=.d+--exclude-dir=rc.d+--binary-files=without-match"
++++echo+l:cmd+.+l:cmd2
++++execute+l:cmd+.+l:cmd2
endfunction

com+-nargs=1+GrepHere++++++++++call+MyGrep(+<q-args>,+"./",+0,+0)
com+-nargs=1+GrepHereCaseWhole+call+MyGrep(+<q-args>,+"./",+1,+1)
com+-nargs=1+GrepHereCase++++++call+MyGrep(+<q-args>,+"./",+1,+0)
com+-nargs=1+GrepHereWhole+++++call+MyGrep(+<q-args>,+"./",+0,+1)|code-block|syntax|javascript|1100887|在windows上，我将vimgrep和changelist与以下命令一起使用(也在.vimrc中)：|1100888|command+-nargs=1+VGCodeHere+:vimgrep+/<args>/j+./**/*.{c,cpp,h,rc}+%7C+copen|1100889|这两个“greppers”都依赖于当前的工作目录，所以不要忘记正确设置它。我通常在Vim中打开一个新的未命名选项卡，并在那里使用这个搜索命令来转储我感兴趣的文件名、搜索结果、日志位置和其他信息。|1100890|Second，一个cscope实用工具和Vim插件-它是浏览项目中的文件、函数、符号的一种非常方便的方式，但如果你处理的是C/C%2B%2B源代码。|BOLD|1100891|Third，原生Vim技巧，例如|1100892|在文件系统子树中的某个位置打开filename.cpp的|1100893|:e+./**/filename.cpp。支持文件名completion.|unordered-list-item|1100894|:tabe+%25<.h打开相应的头文件(您可以使用内置文件系统browser|1100895|Ctrl-O，Ctrl-I在Vim跳转列表|1100896|中将.h扩展名更改为您要导航的任何内容|1100897|为了下一次从相同的Vim状态恢复，我使用会话。使用:mksession+sessionname.vis在Vim中保存会话，并使用session：vim+-S+sessionname.vis启动vim|1100898|entityMap^0|0|0|0|P|6|0|0|16|6|0|0|0|0|6|0|0|5|0|0|0|K|0|0|A|0|0|0|K|2|P|Q|20|M|0^^$0|@$1|2|3|4|5|6|7|1G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1I|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1J|8|@$H|1K|I|1L|J|K]]|9|@]|A|$]]|$1|L|3|M|5|N|7|1M|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1N|8|@$H|1O|I|1P|J|K]]|9|@]|A|$]]|$1|S|3|T|5|N|7|1Q|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1R|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1S|8|@$H|1T|I|1U|J|Y]]|9|@]|A|$]]|$1|Z|3|10|5|6|7|1V|8|@$H|1W|I|1X|J|Y]]|9|@]|A|$]]|$1|11|3|12|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|13|3|14|5|15|7|1Z|8|@$H|20|I|21|J|K]]|9|@]|A|$]]|$1|16|3|17|5|15|7|22|8|@$H|23|I|24|J|K]]|9|@]|A|$]]|$1|18|3|19|5|15|7|25|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|26|8|@]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|27|8|@$H|28|I|29|J|Y]|$H|2A|I|2B|J|K]|$H|2C|I|2D|J|K]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2E|8|@]|9|@]|A|$]]]|1F|$]]

I'm understand that it's may be too late, but I hope this would be useful for someone.

We have relatively large project on work of about thousand files of C/C++ code, php and shell
scripts, configs and other stuff. 

To navigate through files I use following options.

First, I use simple grep wrapper, stored in my <code>.vimrc</code> to find specific string in files:

<pre><code>function MyGrep( pattern, path, case, whole )
 execute "normal! GoSearch text " . a:pattern . " in " . a:path . " and subdirs, case: " .a:case. " whole: ".a:whole
 "E - extended regexp, l - display filenames only, r - search recursively
 let l:keys = "Elr"
 if a:case == 0
 "case-sensitive
 let l:keys = l:keys . "i"
 endif
 if a:whole != 0
 "whole words only
 let l:keys = l:keys . "w"
 endif
 let l:cmd = "r!grep -" . keys . " -e \"" . a:pattern ."\" "
 let l:cmd2 = a:path . " --exclude=*.ncb --exclude=*.o --exclude=*.d --exclude-dir=.svn --exclude-dir=.d --exclude-dir=rc.d --binary-files=without-match"
 echo l:cmd . l:cmd2
 execute l:cmd . l:cmd2
endfunction

com -nargs=1 GrepHere call MyGrep( &lt;q-args&gt;, "./", 0, 0)
com -nargs=1 GrepHereCaseWhole call MyGrep( &lt;q-args&gt;, "./", 1, 1)
com -nargs=1 GrepHereCase call MyGrep( &lt;q-args&gt;, "./", 1, 0)
com -nargs=1 GrepHereWhole call MyGrep( &lt;q-args&gt;, "./", 0, 1)
</code></pre>

On windows I use vimgrep and changelist with this command (also in <code>.vimrc</code>):

<pre><code>command -nargs=1 VGCodeHere :vimgrep /&lt;args&gt;/j ./**/*.{c,cpp,h,rc} | copen
</code></pre>

Both 'greppers' are depend on current working directory, so don't forget to set it properly.
I usually open a new unnamed tab in Vim and use this search commands there to dump there file 
names that I'm interested in, search results, logs locations and other info.

Second, a cscope utility and plug-in for Vim - it is Very convenient way to browse files,
functions, symbols in project, but if you dealing with C/C++ sources. 

Third, native Vim tricks, such as 

<ul>
<li><code>:e ./**/filename.cpp</code> to open filename.cpp somewhere in file system subtree. Supports &lt;Tab&gt; filename completion.</li>
<li><code>:tabe %&lt;.h </code>to open corresponding header file (you can change .h extension to whatever you like)</li>
<li><code>:Ex </code> to navigate, using built-in file system browser</li>
<li>Ctrl-O, Ctrl-I to go backwards and forward in Vim jump list</li>
</ul>

And to resume next time from the same Vim state I use sessions.
Save session in Vim with 
<code>:mksession sessionname.vis</code>
, and launch vim with session:
<code>vim -S sessionname.vis</code>

Having just moved from textmate to vim I'm curious. To be able to navigate my project efficiently I've installed command-t and ack.vim. These both seem like relatively new projects in the history of vim. What do people traditionally do to move around a project when they work in vim, do they just use the file explorer or is there some old school trick I don't know about?

What's the traditional way to navigate a project

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

刚刚从textmate迁移到vim，我很好奇。为了能够高效地导航我的项目，我安装了命令-t和ack.vim。在vim的历史上，这两个似乎都是相对较新的项目。当人们在vim中工作时，他们传统上会做些什么来移动项目，他们只是使用文件资源管理器，还是有什么我不知道的老把戏？

问浏览项目的传统方式是什么
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问浏览项目的传统方式是什么EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问浏览项目的传统方式是什么
EN