edenzik / macvim

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

SQL syntax file causes insert mode navigation problems with the left and right arrow keys #252

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
Open a file (for example, the attached a.sql file), enter insert mode, and try 
to move the cursor horizontally with the arrow keys (left or right). Nothing 
happens.

What is the expected output? What do you see instead?
The cursor should move to the right or left.

What version of MacVim and OS X are you using (see "MacVim->About 
MacVim"
and  "Apple Menu->About This Mac" menu items, e.g. "Snapshot 40, 
10.5.6
Intel")?
Snapshot 51 on 10.6.2 Intel.

Please provide any additional information below.

Original issue reported on code.google.com by nerd...@gmail.com on 26 Jan 2010 at 7:27

Attachments:

GoogleCodeExporter commented 9 years ago
It works fine for me.  Have you gone through the steps of the ReportingBugs 
wiki page?

Original comment by bjorn.winckler@gmail.com on 31 Jan 2010 at 1:36

GoogleCodeExporter commented 9 years ago
I have found the culprit for me.
I removed my .vimrc, .vim/, etc. and reset the preferences, then created a new 
.vimrc 
with one line: 

filetype plugin on

It breaks navigating with the right and left arrows in insert mode.

Original comment by nerd...@gmail.com on 31 Jan 2010 at 4:22

GoogleCodeExporter commented 9 years ago
That means one of your plugins is to blame.  Try figuring out which and email 
the plugin maintainer about the 
problem.

Original comment by bjorn.winckler@gmail.com on 31 Jan 2010 at 12:06

GoogleCodeExporter commented 9 years ago
I have found the bug. It is in the sql plugin bundled with MacVim. There is 
already a bug filed with Debian at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560083

There is a patch at the bottom of the thread:

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=15;filename=sql.diff;att=1;bug=
560083

that contains a fix for the problem. I haven't tested the patch though.

Original comment by nerd...@gmail.com on 2 Feb 2010 at 2:35

GoogleCodeExporter commented 9 years ago
Hopefully the patch will make its way into the official Vim runtime 
files...until then you'll have to manually patch 
the problem (I always include the latest runtime files when I release a new 
snapshot).

Original comment by bjorn.winckler@gmail.com on 4 Feb 2010 at 9:21

GoogleCodeExporter commented 9 years ago

Original comment by bjorn.winckler@gmail.com on 24 Aug 2010 at 6:36