vimpdb - Project Hosting on Google Code

Last 30 days Mar 10, 2010 issue 3 (cannot even loading in vim 7.1) commented on by christoph.rauch - dos2unix on all the files works too dos2unix on all the files works too Feb 19, 2010 issue 2 (Pluign fails to load) commented on by chaos42 - On Mac: open in Hex Fiend, do a find and replace all on 0D 0A to 0A On Mac: open in Hex Fiend, do a find and replace all on 0D 0A to 0A Older Dec 05, 2009 issue 4 (Gvim exits when a second breakpoint is set in vimpdb with "f...) commented on by kirzhanov - GVim exits with an error, vim from terminal runs nicely. Version 7.2, Ubuntu 9.10. GVim exits with an error, vim from terminal runs nicely. Version 7.2, Ubuntu 9.10. Dec 04, 2009 issue 4 (Gvim exits when a second breakpoint is set in vimpdb with "f...) commented on by stevvooe - Any news on this? Pretty useless plugin at this point. Any news on this? Pretty useless plugin at this point. Aug 18, 2009 issue 3 (cannot even loading in vim 7.1) commented on by JohnFBell3 - For OS X you need: :set fileformat=mac For OS X you need: :set fileformat=mac Aug 17, 2009 issue 2 (Pluign fails to load) commented on by etienne.kevin - On Linux: $ dos2unix VimPdb.vim On Linux: $ dos2unix VimPdb.vim Jun 25, 2009 issue 5 (Is there a way to see script output?) reported by ibragim.youldachev - Is there a way to see debugging script output? I.e. I would like to be able to see stdout when executing 'print "Hello, World!"' line. For now F4 on the 'print "Hello, World!"' line generates the following message: PyntaxError: unexpectedEOFgwhileeparsingg(<string>, line 1). VIM 7.2.209 Is there a way to see debugging script output? I.e. I would like to be able to see stdout when executing 'print "Hello, World!"' line. For now F4 on the 'print "Hello, World!"' line generates the following message: PyntaxError: unexpectedEOFgwhileeparsingg(<string>, line 1). VIM 7.2.209 Jun 10, 2009 issue 3 (cannot even loading in vim 7.1) commented on by kentbergstrom5 - Comment 5 fixes the problem. Its just an incompatibility between file formats. You can also use the command line: vim +"set ff=unix" +wq VimPdb.vim This solves the problem. Comment 5 fixes the problem. Its just an incompatibility between file formats. You can also use the command line: vim +"set ff=unix" +wq VimPdb.vim This solves the problem. Jun 10, 2009 issue 3 (cannot even loading in vim 7.1) commented on by kentbergstrom5 - I'm using Vim 7.2, and python is definitely supported ('hello world' example works). THE Fix in comment 5 doesn't seem to work. I'm using Vim 7.2, and python is definitely supported ('hello world' example works). THE Fix in comment 5 doesn't seem to work. May 26, 2009 issue 4 (Gvim exits when a second breakpoint is set in vimpdb with "f...) commented on by YuviPanda - For me, just pressing F5 on even "Hello World" gives the same error. Same platform. For me, just pressing F5 on even "Hello World" gives the same error. Same platform. May 24, 2009 issue 4 (Gvim exits when a second breakpoint is set in vimpdb with "f...) reported by eric.kedji - What steps will reproduce the problem? 1. Install vimpdb, and start gvim on a python file with a couple of assignements 2. Press F5 to start debugging 3. Set a break point on a line (foo = 2 for example) with F2 4. Set a break point on another line (bar = 3 for example) with F2 What is the expected output? What do you see instead? The second line should be highlighted in red as the first, to indicate the presence of a breakpoint. Instead, Gvim exits within half a second (approximately) with this error printed on the console: gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. What version of the product are you using? On what operating system? I use the latest vimpdb, with Gvim 7.2.79, on Ubuntu 9.04 Please provide any additional information below. What steps will reproduce the problem? 1. Install vimpdb, and start gvim on a python file with a couple of assignements 2. Press F5 to start debugging 3. Set a break point on a line (foo = 2 for example) with F2 4. Set a break point on another line (bar = 3 for example) with F2 What is the expected output? What do you see instead? The second line should be highlighted in red as the first, to indicate the presence of a breakpoint. Instead, Gvim exits within half a second (approximately) with this error printed on the console: gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. What version of the product are you using? On what operating system? I use the latest vimpdb, with Gvim 7.2.79, on Ubuntu 9.04 Please provide any additional information below. Jan 30, 2009 issue 3 (cannot even loading in vim 7.1) commented on by tjelvar.olsson - I just had the same problem. Not a case of python not being built in (:python print 'hello world' works), but a case of eol-file incompatibility. FIX (using vim) :set fileformat=unix :w I just had the same problem. Not a case of python not being built in (:python print 'hello world' works), but a case of eol-file incompatibility. FIX (using vim) :set fileformat=unix :w Nov 21, 2008 issue 3 (cannot even loading in vim 7.1) commented on by gritsay.anton - Check for eol-style, I fixed that converting eol-chars from dos to unix in both plugin files. Check for eol-style, I fixed that converting eol-chars from dos to unix in both plugin files. Nov 15, 2008 issue 2 (Pluign fails to load) commented on by simone.soldateschi - @mr.m.s.stevenson thx, it works :) @mr.m.s.stevenson thx, it works :) Oct 16, 2008 issue 3 (cannot even loading in vim 7.1) commented on by kytexzy - It's seems that it can not work on vim7.2. It's seems that it can not work on vim7.2. Oct 07, 2008 issue 1 (Failed to start debugging) commented on by phxx.de - @stefan.eletzhofer: Have you reached a usable point with PdbIDE and the vim server mode? @stefan.eletzhofer: Have you reached a usable point with PdbIDE and the vim server mode? Oct 07, 2008 issue 2 (Pluign fails to load) commented on by phxx.de - Or try to use an alternativ archiv-programm. E.g. "ark" for the KDE Desktop. Or try to use an alternativ archiv-programm. E.g. "ark" for the KDE Desktop. Oct 07, 2008 issue 3 (cannot even loading in vim 7.1) commented on by phxx.de - This sounds like you didn't have a vim version with builtin python support. I also use ubuntus vim version but there is definitly python enabled. Try to execut this in vim: :python print "hello world" Do you get an error message? This sounds like you didn't have a vim version with builtin python support. I also use ubuntus vim version but there is definitly python enabled. Try to execut this in vim: :python print "hello world" Do you get an error message?

issue 4 (Gvim exits when a second breakpoint is set in vimpdb with "f...) reported by eric.kedji - What steps will reproduce the problem? 1. Install vimpdb, and start gvim on a python file with a couple of assignements 2. Press F5 to start debugging 3. Set a break point on a line (foo = 2 for example) with F2 4. Set a break point on another line (bar = 3 for example) with F2 What is the expected output? What do you see instead? The second line should be highlighted in red as the first, to indicate the presence of a breakpoint. Instead, Gvim exits within half a second (approximately) with this error printed on the console: gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. What version of the product are you using? On what operating system? I use the latest vimpdb, with Gvim 7.2.79, on Ubuntu 9.04 Please provide any additional information below.

What steps will reproduce the problem? 1. Install vimpdb, and start gvim on a python file with a couple of assignements 2. Press F5 to start debugging 3. Set a break point on a line (foo = 2 for example) with F2 4. Set a break point on another line (bar = 3 for example) with F2 What is the expected output? What do you see instead? The second line should be highlighted in red as the first, to indicate the presence of a breakpoint. Instead, Gvim exits within half a second (approximately) with this error printed on the console: gvim: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0. What version of the product are you using? On what operating system? I use the latest vimpdb, with Gvim 7.2.79, on Ubuntu 9.04 Please provide any additional information below.

Last 30 days

Older