Vim 和 Emacs 用户,如何像 Eclipse/Netbeans 一样有效地调试?
在阅读了《实用程序员》等书籍后,它强烈建议的一件事是选择一个文本编辑器并掌握它。我选择使用Emacs并坚持了大约半年。然而,让我不断回到成熟的 IDE 的一件事是调试。
在尝试通过命令行使用 xdebug 几周后,毫不奇怪,Netbeans/Eclipse 提供的调试工具远远优于 CLI。
那么,伙计们,有没有任何 Linux 工具可以让您放置断点并帮助在运行时可视化您的应用程序,或者有什么理由让我坚持通过 CLI 调试来忍受痛苦呢?
任何反馈表示赞赏!
After reading books like The Pragmatic Programmer, one thing it strongly suggested was to pick a text editor and master it. I chose to use Emacs and stuck with it for about half a year. However, the one thing that kept pulling me back to a full-fledged IDE was debugging.
After attempting to use xdebug via command-line for a couple of weeks, it was no surprise that the debugging tools that Netbeans/Eclipse provide are far superior to CLI.
So fellas, are there any Linux tools that allow you to place breakpoints and help visualize your application at run-time, or is there a reason why I should stick to suffering through CLI debugging?
Any feedback appreciated!
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
我整天使用 Vim 进行编码。但在调试时,我总是使用 IDE (Visual Studio) 的调试器,因为在调试时,我将鼠标悬停在某些变量上,编辑它们的值等等。这不是我需要强大编辑器来完成的任务。
这是我给你的建议:对于编码和编辑,请使用编辑器;使用(图形)调试器进行调试(DDD、Eclipse,随便)。更换工具并不是一种亵渎,只是使用错误的工具来完成任务。
I'm using Vim all day for coding. But when it comes to debugging, I always take the debugger of my IDE (Visual Studio) because while debugging, I take the mouse and hoover over some variables, edit their values and so on. That's not a task that I'd need a powerful editor for.
That's my advice to you: for coding and editing, take an editor; for debugging take a (graphical) debugger (DDD, Eclipse, whatever). It's not a sacrilege to switch tools, only to take the wrong tools for the task to be done.
像这样: http:// www.gnu.org/software/libtool/manual/emacs/GDB-Graphical-Interface.html#GDB-Graphical-Interface ?
教程:http://www.youtube.com/watch?v=vHOzMOzzxDA
Like this: http://www.gnu.org/software/libtool/manual/emacs/GDB-Graphical-Interface.html#GDB-Graphical-Interface ?
Tutorial : http://www.youtube.com/watch?v=vHOzMOzzxDA
相同的。我使用 IDE 来处理繁重的工作,使用 Emacs 来处理快速的工作。
精通轻量级编辑器的原因是当您知道自己想做什么时要灵活。打开这个文件,查找标签,编辑,magit-status,提交,推送。嘭。你不想要启动时间和时间当你达到目标时,不稳定会阻碍你的努力。大多数服务器上都安装了 Vim,如果您要在生产环境中进行编辑,您最好有一个目标。
另一方面,我发现 IDE(Aptana 对我来说是 PHP)对于“学习”很有用。调试、单步执行代码、分析代码、搜索(当有多个结果时,Eclipse 的树结果搜索超过 Emac 的 rgrep 的任何一天)。
我认为自己非常熟练地通过 ECB、geben、rgrep、ctags、magit 等使用 Emacs 作为成熟的 IDE。我专门使用它一年多了 — 但老实说,它阻碍了我的工作效率 —繁重的任务需要太多的步骤。现在我使用 Aptana & Emacs 一天中的效率大约是 50/50。
轻型编辑器用于轻型内容,重型编辑器用于重型内容
Same. I use IDEs for the heavy stuff and Emacs for quick stuff.
The reason to be proficient with a light-weight editor is to be nimble when you know what you want to do. Open this file, find-tag, edit, magit-status, commit, push. Bam. You don't want startup-time & instability to be cock-blocking your effort when you've got at goal. Vim is installed on most servers, and if you're editing on production, you'd better have a goal.
IDEs on the other hand (Aptana for me, PHP) I find are useful for "studying". Debugging, stepping through code, analyzing code, searching (Eclipse's tree-results search over Emac's rgrep ANY day when there are multiple results).
I consider myself quite proficient with using Emacs as a full-fledged IDE via ECB, geben, rgrep, ctags, magit, etc. I used it as such exclusively for over a year -- but in all honesty, it hindered my productivity -- the heavy tasks take too many steps. Now I use Aptana & Emacs really about 50/50 throughout the day.
Light editors for light stuff, Heavy editors for the heavy stuff
vim 中肯定有调试解决方案,请参阅 http://jaredforsyth.com/projects/vim-debug/,还有更多,但我没有尝试过,我倾向于从 ide 到 vim 来回切换。
there are definitely debugging solutions in vim see http://jaredforsyth.com/projects/vim-debug/, there are more but I haven't tried them, I tend to switch back and forth from an ide to vim.