Bug 952758 - Possible regression in mouse drags/moves of buffer split lines
Summary: Possible regression in mouse drags/moves of buffer split lines
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vim
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Karsten Hopp
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-16 15:48 UTC by Jan Pokorný [poki]
Modified: 2013-05-22 01:26 UTC (History)
1 user (show)

Fixed In Version: vim-7.3.944-1.fc18
Clone Of:
Environment:
Last Closed: 2013-05-22 01:26:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jan Pokorný [poki] 2013-04-16 15:48:37 UTC
Following compares vim-enhanced as in Fedora 17 and 18:

Test command:
$ vim --noplugin '+set mouse=n' '+e /tmp/a' +vsp

F17: vim-enhanced-7.3.682-1.fc17.x86_64
- one can drag the splitting line and move it left and right

F18: vim-enhanced-7.3.712-1.fc18.x86_64
- no ability to move


Seems to be a regression and in case of multiple buffers, I'd prefer
this functionality to work.

Note that differences in terminals don't matter, I tried crosschecking
through ssh with the same results.

Comment 1 Jan Pokorný [poki] 2013-04-16 15:50:31 UTC
> $ vim --noplugin '+set mouse=n' '+e /tmp/a' +vsp

+set mouse=a
is actually what I used and should cover more cases in general.

Comment 2 Jan Pokorný [poki] 2013-04-17 12:49:08 UTC
Strictly viewed, I'd say it is a regression however it is easily solvable
once you know what to look for.

My solution was to append
> set ttymouse=xterm2
to ~/.vimrc

Note that "sgr" as the value works for me as well, and it is even
an implicit value I am getting with in Fedora 17 (package referenced
above).


For completeness, t_RV variable in vim is implicitly set to "^[[>",
which seems to do the job as expected in my environment:

$ echo -ne "\033[>c"
$ 1;2802;0c
  ^ response (2nd field should be patch number, denoted "extra" in vim (?))


From the quick look, I think that the problem could be caused directly
by the first patch from delta between F17 and F18 releases that
mentions mouse: 7.3.699.  Here, I can see that some code that sets
"sgr" or "xterm2" for ttym if the patch number is higher than 276
and 95 respectively was simply removed.

Karsten, could you please have a look at this?
In the meantime, I can suggest my workaround (which, in the less optimal
case, could be even hardwired to the distributed package).

Comment 3 Jan Pokorný [poki] 2013-04-18 13:51:58 UTC
Applying/getting up to patch 745 [1] might fix the problem.

[1] ftp://ftp.vim.org/pub/vim/patches/7.3/7.3.745

Comment 4 Jan Pokorný [poki] 2013-04-19 12:26:22 UTC
Can confirm vim-7.3.785-1.fc19 [2] build (i.e., including patch 745)
fixes this buggy requirement of manual ttym specification.


As an aside, I installed all non-debuginfo packages for my arch from [2],
and while vim works flawlessly, I cannot run gvim:

$ gvim -D
E25: GUI cannot be used: Not enabled at compile time

Doesn't look like something likely to be caused by using gvim compiled
for F19 on F18.  Or is this a cause?

Comment 5 Jan Pokorný [poki] 2013-04-19 12:27:03 UTC
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=380909

Comment 6 Jan Pokorný [poki] 2013-04-19 12:32:20 UTC
> $ gvim -D
> E25: GUI cannot be used: Not enabled at compile time

Good news, gvim works well since vim-7.3.797-1.fc19 [3] again.

[3] https://koji.fedoraproject.org/koji/buildinfo?buildID=381550

---

Karsten, if the issue doesn't warrant for an update in F18, this bug
can be closed I guess.  Things seem to be just fine in F19 since [3].

Comment 7 Karsten Hopp 2013-04-19 17:24:44 UTC
I'll update vim to the latest patchlevel soon, I just need to wait for a related issue to get resolved.

Comment 8 Fedora Update System 2013-05-14 13:55:33 UTC
vim-7.3.944-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/vim-7.3.944-1.fc18

Comment 9 Fedora Update System 2013-05-15 03:28:57 UTC
Package vim-7.3.944-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing vim-7.3.944-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8213/vim-7.3.944-1.fc18
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2013-05-22 01:26:29 UTC
vim-7.3.944-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.