Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#27224 - [vim 7.3.353-1] mouse support broken after using shell with :!

Attached to Project: Arch Linux
Opened by Janna Martl (jmartl109) - Tuesday, 22 November 2011, 07:22 GMT
Last edited by Eric Belanger (Snowman) - Sunday, 27 November 2011, 23:51 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Eric Belanger (Snowman)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Mouse input is ignored after using the shell via <esc>:! even though I have set mouse=a.
I think this is a compilation issue: see NOTE below.

Additional info:
* package version(s): gvim 7.3.353, OK in 7.3.338; does not affect the GUI
* config and/or log files etc.: I can reproduce this using a ~/.vimrc containing only
set nocompatible
set mouse=a

NOTE: I'm reporting this here, and not to upstream, because I downloaded the PKGBUILD etc. from ABS, and running
make distclean; ./configure; make
in the appropriate directory produced a version without the bug, but running
make distclean; make
produced a version that has the bug.

Steps to reproduce:
$vim
Insert some text, hit escape, :! enter to access shell, enter to return to vim. Now try to move the cursor by using the mouse to click on some character. Nothing happens, even though mouse=a is set.
This task depends upon

Closed by  Eric Belanger (Snowman)
Sunday, 27 November 2011, 23:51 GMT
Reason for closing:  Fixed
Additional comments about closing:  vim-7.3.353-2
Comment by Eric Belanger (Snowman) - Wednesday, 23 November 2011, 06:15 GMT
Looks like upstream bug as I can't make it work by rebuilding. I submitted a bug report: http://code.google.com/p/vim/issues/detail?id=31
Comment by Janna Martl (jmartl109) - Wednesday, 23 November 2011, 07:14 GMT
Thanks for looking into this. To clarify about the compiling, what I did was:
cd /var/abs/extra/vim/
makepkg
cd src/vim-7.3.353/src/
./configure
make

Now at this point what I have is one binary /var/abs/extra/vim/src/vim-7.3.353/src/vim that does not have the bug, and one binary /var/abs/extra/vim/pkg/vim/usr/bin/vim (created by the initial makepkg) that does have bug.
Comment by Jan de Groot (JGC) - Wednesday, 23 November 2011, 11:28 GMT
When you re-run ./configure with different flags, it will not use the same configure flags that were used to build te package.

To Eric: you should add more information about this to the bugreport, the Vim people can't debug this problem without that information if it only happens with certain configure flags.

Loading...