3mao / vimpdb

Automatically exported from code.google.com/p/vimpdb
0 stars 0 forks source link

cannot even loading in vim 7.1 #3

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
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 kingsf...@gmail.com on 12 Apr 2008 at 9:56

GoogleCodeExporter commented 8 years ago
hi!

even i'm facing the same issue on ubuntu, vim 7.1. kindly let me know if you 
find a
solution.

regd,
arun.

Original comment by tomar.a...@gmail.com on 29 Sep 2008 at 4:11

GoogleCodeExporter commented 8 years ago
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?

Original comment by phxx...@gmail.com on 7 Oct 2008 at 8:53

GoogleCodeExporter commented 8 years ago
It's seems that it can not work on vim7.2.

Original comment by kyte...@gmail.com on 17 Oct 2008 at 3:31

GoogleCodeExporter commented 8 years ago
Check for eol-style, I fixed that converting eol-chars from dos to unix in both 
plugin files.

Original comment by gritsay....@gmail.com on 21 Nov 2008 at 9:43

GoogleCodeExporter commented 8 years ago
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

Original comment by tjelvar....@gmail.com on 31 Jan 2009 at 7:38

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
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.

Original comment by kentberg...@gmail.com on 11 Jun 2009 at 3:35

GoogleCodeExporter commented 8 years ago
For OS X you need:

:set fileformat=mac

Original comment by JohnFBe...@gmail.com on 18 Aug 2009 at 7:54

GoogleCodeExporter commented 8 years ago
dos2unix on all the files works too

Original comment by christoph.rauch@gmail.com on 10 Mar 2010 at 8:18

GoogleCodeExporter commented 8 years ago
FYI, unix fileformat works fine in OSX as well.

Original comment by kru...@gmail.com on 30 Aug 2010 at 4:25

GoogleCodeExporter commented 8 years ago
Here is another fix:

    tr '\r' '\n' < vimpdb.py > vimpdb.py
    tr '\r' '\n' < vimpdb.vim > vimpdb.vim

Original comment by christangrant on 20 Mar 2011 at 2:51