comment on

It sounds as if you are using the debugger inside VIM (is there even an integration available?ł), but I think you are calling vim from the debugger. (right?)

AFAIR in the latter case you are able to customize an editor inside the debugger to edit multiple lines˛, wouldn't surprise me if Mac doesn't like VIM.°

Or are you talking about switching only the line edit commands from GNU (i.e. emacs) to VI?

IIRC there is a set option to do so.

see http://vim.wikia.com/wiki/Use_vi_shortcuts_in_terminal

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

°) understandably as an emacser ;-)

˛) seems what I remebered was the pager support, which doesn't really allow to edit the history though!

see

  DB<1> h |
|dbcmd        Run debugger command, piping DB::OUT to current pager.
||dbcmd        Same as |dbcmd but DB::OUT is temporarily select()ed as
+ well.
[download]

ł) a sure Fritz Mehner of course :) http://www.vim.org/scripts/script.php?script_id=556

In reply to Re: vim and debugger history by LanX
in thread vim and debugger history by jpl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks