David Fishburn wrote: > > On May 29 2008, 10:41 am, Andy Wokula<[email protected]> wrote: > >> Charles E Campbell Jr schrieb: >> >> >>> Hello! >>> >>> I'm working on some plugins, and recently one has started issuing >>> beeps. I'm not sure why; there's no message attached, and its been >>> eluding my efforts (comment out blocks of code, see if thebeepstops). >>> >>> Is there a Better Way to find what causes these beeps? Ideally there'd >>> be a v:xyz variable of some sort that contained a filename&linenumber >>> string for the lastbeep. I don't even need a message -- just where. >>> >>> Regards, >>> Chip Campbell >>> >> :setdebug=beep >> >> will do that. The command-line shows a "Beep" message, but the >> :mess >> history also includes a line number like for usual errors. >> >> func! TestBeep() >> normal! 0 >> normal! h >> endfunc >> >> :call TestBeep() >> :mess >> >> Error detected while processing function TestBeep: >> line 2:Beep! >> > > Andy, couldn't figure out how to not sent this to you directly via the > vim_use google group. > > I too am running into an unexplained beep (which causes my code to > stop executing) and I am trying to find the source of it. > > When I do the above and run it I get: > YR:Enter character:a > Beep! > > So no line numbers or any other reference. > > Anything else I can turn on to track it down? Or increase verbosity > levels? > Thank you for the help -- I'd tried set debug=beep myself and wasn't getting any line numbers. I don't recall if I typed :mess, though.
Regards, Chip Campbell --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
