Re: Setting Up Debugging
Tom Purl wrote: I'm having a problem with netrw, but before I can properly troubleshoot it, I need to fix debugging. What I would basically like to do is use Vim normally (without having a bunch of debug messages pop up) while all of the messages are written to a file. Here's what I have in my ~/.vimrc: let verbosefile = /tmp/vim_debug.out set viminfo='50,1000,s100 :verbose set viminfo? I copied this set of commands a couple of months ago to help troubleshoot a different problem. Shouldn't these commands still work, or am I missing something? I suggest using the Dfunc/Decho/Dret debugging system already part of netrw. Once you have the plugin installed, vim netrw.vim :DechoOn :wq The latest version of netrw uses DechoTabOn, which means that debugging output will go to a separate tab. You can save the resulting output to a file whenever you wish, and the display won't be affected (other than seeing the presence of two tabs). You can get the Decho plugin from: http://vim.sourceforge.net/scripts/script.php?script_id=120 -or- http://mysite.verizon.net/astronaut/vim/index.html#DECHO (this latter one is always the most up-to-date) You'll need an up-to-date version of vimball to extract plugins that I've generated since August 1, 2006: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs see Vimball Archiver (the most up-to-date version is here) You'll need to completely remove all older vestiges of vimball from your runtimepath. Under Linux, that usually means cd /usr/local/share/vim/vim70 /bin/rm plugin/vimball*.vim autoload/vimball*.vim Under Windows, check your runtimepath to determine where your vim 7.0's runtime directories are: vim :echo rtp :q should give you a clue. Regards, Chip Campbell
Re: Setting Up Debugging
I suggest using the Dfunc/Decho/Dret debugging system already part of netrw. Once you have the plugin installed, vim netrw.vim :DechoOn :wq The latest version of netrw uses DechoTabOn, which means that debugging output will go to a separate tab. You can save the resulting output to a file whenever you wish, and the display won't be affected (other than seeing the presence of two tabs). You can get the Decho plugin from: http://vim.sourceforge.net/scripts/script.php?script_id=120 -or- http://mysite.verizon.net/astronaut/vim/index.html#DECHO (this latter one is always the most up-to-date) You'll need an up-to-date version of vimball to extract plugins that I've generated since August 1, 2006: http://vim.sourceforge.net/scripts/script.php?script_id=1502 -or- http://mysite.verizon.net/astronaut/vim/index.html#VimFuncs see Vimball Archiver (the most up-to-date version is here) Thanks for the quick reply Dr. Chip! I tried installing both the latest version of netrw and Decho, but I'm seeing a weird problem. Here's the process that I used to install these plugins: vim plugin.vba.gz so % And here's what the plugins look like on the file system (Linux) after running said process: [EMAIL PROTECTED] ~/.vim $ find . -type f -name *Decho* ./doc/Decho.txt?[[[1 ./plugin/Decho.vim?[[[1 ./syntax/Decho.vim?[[[1 [EMAIL PROTECTED] ~/.vim $ find . -type f -name *netrw* ./doc/pi_netrw.txt?[[[1 ./plugin/netrwPlugin.vim?[[[1 ./syntax/netrw.vim?[[[1 ./autoload/netrw.vim?[[[1 ./autoload/netrwFileHandlers.vim?[[[1 ./autoload/netrwSettings.vim?[[[1 Has anyone ever seen anything like this before? Thanks again! Tom Purl
Re: Setting Up Debugging
Thanks for the quick reply Dr. Chip! I tried installing both the latest version of netrw and Decho, but I'm seeing a weird problem. Here's the process that I used to install these plugins: vim plugin.vba.gz so % And here's what the plugins look like on the file system (Linux) after running said process: [EMAIL PROTECTED] ~/.vim $ find . -type f -name *Decho* ./doc/Decho.txt?[[[1 ./plugin/Decho.vim?[[[1 ./syntax/Decho.vim?[[[1 [EMAIL PROTECTED] ~/.vim $ find . -type f -name *netrw* ./doc/pi_netrw.txt?[[[1 ./plugin/netrwPlugin.vim?[[[1 ./syntax/netrw.vim?[[[1 ./autoload/netrw.vim?[[[1 ./autoload/netrwFileHandlers.vim?[[[1 ./autoload/netrwSettings.vim?[[[1 Has anyone ever seen anything like this before? Yes -- its due to an out-of-date vimball plugin. You need to get an up-to-date version of vimball (v18 or later), and to remove any previous vimball remnants. Ok, I just wanted to make sure. My computer has been doing some weird things lately, and I wanted to narrow it down. Also, it's impossible to search for the term [[[1 in Google, so it was hard for me troubleshoot *that* problem. Thanks again! Tom Purl
