Git Product home page Git Product logo

vimpdb's People

Watchers

 avatar  avatar

vimpdb's Issues

Make doc from readme.txt

What steps will reproduce the problem?
1. Configure VimPdb to take readme as doc
2. Show keystrokes and description
3.

Probably this might already be working. 

Original issue reported on code.google.com by [email protected] on 25 Jan 2011 at 10:01

Is there a way to see script output?

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

Original issue reported on code.google.com by [email protected] on 25 Jun 2009 at 4:31

cannot even loading in vim 7.1

What steps will reproduce the problem?
1. Just loading vim

What is the expected output? What do you see instead?
Nothing. No error output.

What version of the product are you using? On what operating system?
VimPdb.tar      0.1 w/ vim 7.1 GNU/Debian

Please provide any additional information below.
I am not sure this plugin work in vim 7.X.

Error message:

Error detected while processing /home/user/.vim/plugin/VimPdb.vim:
line   19:
E492: Not an editor command: import sys
line   20:
E319: Sorry, the command is not available in this version: python
sys.path.insert(0, r"/home/user/.vim/plugin")
line   21:
E492: Not an editor command: import VimPdb
Error detected while processing function PdbInitialize:
line   11:
E319: Sorry, the command is not available in this version: ^Ipython import sys
line   12:
E319: Sorry, the command is not available in this version: python
sys.path.insert(0, r"")
line   13:
E319: Sorry, the command is not available in this version: ^Ipython import
VimPdb
line   15:
E319: Sorry, the command is not available in this version: ^Ipython << EOF
line   16:
E492: Not an editor command: import vim
line   17:
E492: Not an editor command: import threading
line   18:
E492: Not an editor command: import time
line   19:
E492: Not an editor command: import re
line   21:
E492: Not an editor command: reload(VimPdb)
line   24:
E488: Trailing characters: # The VimPdb instance used for debugging.
="=" [New File]
Cannot open file "="
VimPdb.VimPdb()"VimPdb.VimPdb()" [New File]
Cannot open file "VimPdb.VimPdb()"
line   25:
E480: No match: _pdb
="vim.eval('g:stack_entry_format')" [New File]
Cannot open file "vim.eval('g:stack_entry_format')"
line   26:
E480: No match: _pdb.stack_entry_format
="vim.eval('g:stack_entry_prefix')" [New File]
Cannot open file "vim.eval('g:stack_entry_prefix')"
line   27:
E480: No match: _pdb.stack_entry_prefix
="vim.eval('g:current_stack_entry_prefix')" [New File]
Cannot open file "vim.eval('g:current_stack_entry_prefix')"
line   28:
E480: No match: _pdb.current_stack_entry_prefix
="vim.eval('g:stack_entries_joiner')" [New File]
Cannot open file "vim.eval('g:stack_entries_joiner')"
line   29:
E480: No match: _pdb.stack_entries_joiner
line   32:
E492: Not an editor command: def vim_pdb_start_debug(stop_immediately, args):
E486: Pattern not found: im_pdb
stop_immediately,"stop_immediately," [New File]
Cannot open file "stop_immediately,"
args)"args)" [New File]
Cannot open file "args)"
line   34:
E480: No match: _pdb.start_debugging(vim.current.buffer.name,
line   37:
E492: Not an editor command: def parse_command_line(line):"=" [New File]
line   40:
E121: Undefined variable: line
E116: Invalid arguments for function len(line) > 0):
E15: Invalid expression: (len(line) > 0):
line   44:
E488: Trailing characters: ^I^I^I^I# No ending quotation mark found.
line   48:
E488: Trailing characters: ^I^I^I# Treat anything between the two quotation
marks as one argument.
line   55:
E488: Trailing characters: ^I^I^I# No whitespace found - save the argument
until the end of the line.
line   60:
E488: Trailing characters: ^I^I^I# Whitespace in the beginning of the line
- skip it.
line   69:
E171: Missing :endif


Original issue reported on code.google.com by [email protected] on 12 Apr 2008 at 9:56

Please support Python 3.x.

What steps will reproduce the problem?
1. Can't debug any Python 3.x program.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?

Python 3.x

Please provide any additional information below.

This tool is great, but it not work on Python 3.x.
If I want to using it on Python 3.x, Do I need to re-write vimpdb.py, or just a 
small hack?

Original issue reported on code.google.com by [email protected] on 10 Mar 2012 at 2:49

Using "vim_server_script = vim" doesn't work - no file shown

What steps will reproduce the problem?
1. Change vim_server_script in your .vimpdbrc file to vim rather than gvim
2. Open a file and start a trace

What is the expected output? What do you see instead?
A new vim instance opens when the breakpoint is hit but no file is shown. The 
interactive debug session doesn't start.

What version of the product are you using? On what operating system?
Vimpdb 0.4.5 / Ubuntu 11.04

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 22 Sep 2011 at 10:20

Pluign fails to load

What steps will reproduce the problem?
1. Extract to ~/.vim/plugin/
2. Run Vim
3.

What is the expected output? What do you see instead?

When starting Vim given the following error:

Error detected while processing ~/.vim/plugin/VimPdb.vim:
line    9:
E492: Not an editor command: ^M

for many of the lines in VimPdb

What version of the product are you using? On what operating system?
Ubuntu 7.10


Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 12 Jan 2008 at 9:43

Gvim exits when a second breakpoint is set in vimpdb with "fatal IO error"

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.


Original issue reported on code.google.com by eric.kedji on 24 May 2009 at 11:05

Please use VCS

What steps will reproduce the problem?
1. what is the sense of having project on Google Code and not use any of the 
offerend VCS systems (SVN, hg, or most likely git)?
2.
3.

What is the expected output? What do you see instead?
I would expect that when i look at the Source tab I see all revisions of the 
code.

For interested I have my git repo at http://luther.ceplovi.cz/git/vimpdb.git

Original issue reported on code.google.com by [email protected] on 15 Oct 2013 at 4:13

PEP8ize Python code

What steps will reproduce the problem?
1. see attached
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.



Original issue reported on code.google.com by [email protected] on 15 Oct 2013 at 4:15

Highlighting not working

What steps will reproduce the problem?
1. Start debugging
2. Current line not hihglighted
3. Create breakpoint
4. Breakpoint not highlighted.

Mac bim on OS/X 10.6.7


Original issue reported on code.google.com by [email protected] on 18 May 2011 at 5:19

Failed to start debugging

1) Documentation accessible via :help is missing
2) VimPdb.vim definitely must be in unix line endings format (:set ff=unix)
3) When started in GUI (gvim), pressed the F5, got the message "Xlib:
unexpected async reply (sequence 0x9cb)!". It seems like a threading
problem, all X11 events must be processed within the main thread.

Original issue reported on code.google.com by [email protected] on 17 Oct 2007 at 8:07

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.