Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors when returning to insert mode #14

Closed
GoogleCodeExporter opened this issue Feb 25, 2016 · 7 comments
Closed

Errors when returning to insert mode #14

GoogleCodeExporter opened this issue Feb 25, 2016 · 7 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. We are in normal mode and have edited some stuff in other buffers before
2. Then return to the buffe with conque terminal.
3. Press i to change to insert mode

What is the expected output? What do you see instead?
It is expected return to insert mode but I got lots of errors.
I have attached a screenshot to make it easier.
This happens sometimes and unfortunately I don't have an exact steps to
reproduce the bug.
thanks


What version of the product are you using? On what operating system?
Conque 1.0
Gvim 7.1.242
Fedora Core


Please provide any additional information below.


Original issue reported on code.google.com by pablog...@gmail.com on 26 May 2010 at 12:09

Attachments:

@GoogleCodeExporter
Copy link
Author

Hi, thanks for taking the time to fill out a bug report.

Next time it happens, could you provide the last part of the error list? The
screenshot you sent shows the top of the error stack trace, but the actual error
message will be at the bottom of the stack.

You can most easily get to the bottom by the following these steps anytime 
after you
got that error:

1. Type ":messages" to display your most recent error messages
2. Press "G" to go to the bottom of the error list
3. Copy and paste the last 5 or so messages into this bug

Thanks!

Original comment by nicora...@gmail.com on 26 May 2010 at 2:52

@GoogleCodeExporter
Copy link
Author

Hey nico, thanks for the messages calrification.
Here is the traceback I got:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 231, in write
  File "<string>", line 311, in read
  File "<string>", line 1098, in set_cursor
vim.error: cursor position outside buffer
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
Traceback (most recent call last):
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
  File "<string>", line 1, in <module>
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
  File "<string>", line 319, in auto_read
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
  File "<string>", line 311, in read
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
  File "<string>", line 1098, in set_cursor
Error detected while processing CursorHoldI Auto commands for "<buffer=2>":
vim.error: cursor position outside buffer   

Hope it helps

Original comment by pablog...@gmail.com on 26 May 2010 at 3:21

@GoogleCodeExporter
Copy link
Author

I believe this is from a bug in the python integration, which has since been 
fixed in
Vim 7.2.

r202 should catch these errors for people using an older version of Vim.

Original comment by nicora...@gmail.com on 27 May 2010 at 4:37

@GoogleCodeExporter
Copy link
Author

Thanks Nico.
Since currently conque 1.0 doesn't includee a file names conque_screen.py in 
autoload.
Should I copy this file to my current installation?

Original comment by pablog...@gmail.com on 27 May 2010 at 4:51

@GoogleCodeExporter
Copy link
Author

I've been putting off conque 1.1 for long enough now. It will be released 
sometime
today with this fix included.

Original comment by nicora...@gmail.com on 27 May 2010 at 4:53

@GoogleCodeExporter
Copy link
Author

Fix released with 1.1

Original comment by nicora...@gmail.com on 28 May 2010 at 5:58

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Thanks updated to conque 1.1

Original comment by pablog...@gmail.com on 31 May 2010 at 12:14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant