Hari Krishna Dara wrote:
I have not observed this before, but I don't usually put file
breakpoints. Couple of ideas to try are:
- Try the new ":breakadd here" command where you want to stop. It might
work just fine.
- Generate an exception at this line and observe what line number Vim
will rep
Benji Fisher wrote:
On Tue, Jul 25, 2006 at 11:14:09AM -0400, Charles E Campbell Jr wrote:
Hello!
I was trying :breakadd file 484 */visincr.vim and got
Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
Entering Debug mode. Type "cont" to continue.
/home/cec/.vim/autoload/visinc
On Tue, 25 Jul 2006 at 11:14am, Charles E Campbell Jr wrote:
> Hello!
>
> I was trying :breakadd file 484 */visincr.vim and got
>
> Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
> Entering Debug mode. Type "cont" to continue.
> /home/cec/.vim/autoload/visincr.vim
> line 638: fun!
On Tue, Jul 25, 2006 at 11:14:09AM -0400, Charles E Campbell Jr wrote:
> Hello!
>
> I was trying :breakadd file 484 */visincr.vim and got
>
> Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
> Entering Debug mode. Type "cont" to continue.
> /home/cec/.vim/autoload/visincr.vim
> line
Hello!
I was trying :breakadd file 484 */visincr.vim and got
Breakpoint in "/home/cec/.vim/autoload/visincr.vim" line 484
Entering Debug mode. Type "cont" to continue.
/home/cec/.vim/autoload/visincr.vim
line 638: fun! s:Hex2Dec(hex)
The "Breakpoint in..." line looks right; however, why does t
