[Lldb-commits] [PATCH] Vim Frontend for LLDB
daniel.malea at intel.com
Mon Feb 11 09:26:48 PST 2013
Thanks for the testing Jason! It's much appreciated. I committed the frontend to utils in r174892.
Regarding the command-output going away, I agree this is not ideal. When I have a bit more time (this was made on an "innovation sprint") I will look at adding that feature. It shouldn't be too difficult (to implement another subclass of VimPane).
Along the same lines, it would be good to have a window that displays inferior STDOUT… If someone is eager to implement this before I get a chance, take a look at vim_panes.py.
Unfortunately, I don't think this plugin can ever work if 'set compatible' is enabled…
Also, I should mention that since the plugin opens a bunch of vim "windows" to display information, it's necessary to quit all of them before vim exits; this can be done in one command with ":qa". Eventually, it would be nice if Vim would just ask you if you want to quit once there's no more source windows open.
Please keep the feedback coming :)
On 2013-02-08, at 9:28 PM, Jason Molenda <jmolenda at apple.com>
> That crazy cool. I learned vi a couple decades ago and when I was finally forced to use vim because I was tired of dragging nvi along, I just turned off all the modern features I could manage to and use it like traditional vi. So I'm having using this but it was pretty easy to get up & running. I'll definitely play around with it some more. Off-hand, the only problem I see is that the output to each command I use ('Ldisass -n main') is lost after I press return to end that command -- there isn't a proper console window with commands and output in it.
> I noticed that having 'set compatible' in my ~/.vimrc caused there to be errors in the python vim file.
> Please do add this to the repository when you have a chance. You might finally force me use vim like vim instead of like the vi I learned in the 80's. :)
> On Feb 8, 2013, at 2:31 PM, "Malea, Daniel" <daniel.malea at intel.com> wrote:
>> Hi all,
>> I recently had a little bit of time to develop a new frontend for LLDB inside the Vim editor. It works on Mac and Linux in both terminal and GUI (MacVim/GVim) flavours. Naturally, Linux support is limited by the bugs we are currently battling.
>> Main features:
>> - Access any LLDB CLI command in Vim by typing ":L<command>". Tab-completion works too!
>> - See source locations for breakpoints and the current PC with vim "marks" and highlights.
>> - Examine backtraces, locals, disassembly, registers, and breakpoints in dedicated Vim windows.
>> - See when in-scope variables and registers change by watching for (red) highlights.
>> Install instructions are included in utils/vim-lldb/README, and are pretty painless as I made the plugin pathogen<https://github.com/tpope/vim-pathogen>-friendly. You just need to create a symlink in your ~/.vim/bundle directory to point to the "vim-lldb" directory this patch creates.
>> If there's no objections, my intention is to commit this to LLDB trunk in the utils directory. I can also prepare a little blurb for the website with a screenshot<http://postimage.org/image/ih2s30n23/> or two...
>> If there's any Vim users willing to take the plunge, please let me know how it goes!
>> All the best,
>> lldb-commits mailing list
>> lldb-commits at cs.uiuc.edu
More information about the lldb-commits