小弟以前是做产品经理的，最近转行学开发了 C的基础 和 linux下面C开发 也学了点。
以后打算做linux下C开发这一块。不知道这一块目前怎么样。
还有 就是都是跟着书敲代码，开发环境 就是一个虚拟机centos6.5 里面用VIM 写代码 然后 make编译运行 VIM 也没装任何插件。 GDB也处于半懂不懂的状态。
想问一下 各位前辈 一般工作中 大家工作环境都是什么样的呢？
高洛峰2017-04-17 15:28:26
Use vim for the command line, and QT creator or codeblocks for the graphical interface.
You can also use VS2015 to connect to the Linux host through ssh for development and debugging.
It is also very convenient if vim is configured well. Although the learning cost is a bit high.
A vim configuration with Chinese comments
http://www.cnblogs.com/oloroso/p/4670165.html
It is better to install vim-youcompleteme than using ctags.
I recently discovered that the Visual Studio Code editor is also very easy to use and has very powerful functions. After installing the plug-in, it is enough for general development.
巴扎黑2017-04-17 15:28:26
I use codeblocks under Ubuntu. But the most enjoyable thing is to use VS on Windows, obtain the code through the shared directory of the virtual machine, and compile and test it on the virtual machine.
巴扎黑2017-04-17 15:28:26
Mixed with vim sublime3
It is embedded itself, and GDB is basically not used. An editor is enough.
伊谢尔伦2017-04-17 15:28:26
Does the centos you installed have a desktop? If it is the desktop version, you can try the clion, codeblocks, qtcreator, and sublime mentioned above. If not, I really don’t recommend you use vim to read the code directly on centos. Although many people believe that vim is good because it is good at using it, I don’t think that being good at programming has anything to do with which editor you use. Vim is quite unfriendly to novices. It takes a lot of time to get familiar with various plug-ins and commands. The frustration during the process may make you lose interest in programming.
You can try to install the Samba service on the virtual machine, and then map the code path to a network hard disk on Windows, so that you can view the code on Windows, compile on the virtual machine, various IDEs, various editors, Whichever one is easier to use, I recommend source insight
