Bug 271959 - editors/vim: 9.0.1503 file fialogs broken.
Summary: editors/vim: 9.0.1503 file fialogs broken.
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Adam Weinberger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-12 01:39 UTC by Tomasz "CeDeROM" CEDRO
Modified: 2023-06-12 21:45 UTC (History)
4 users (show)

See Also:
bugzilla: maintainer-feedback? (adamw)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz "CeDeROM" CEDRO 2023-06-12 01:39:47 UTC 
Hello world :-)

I noticed that recent vim-9.0.1503 has broken file browsing dialogs (when opening a file with :E command).

I am using basic textmode console version. I have main window divided into several subwindows in horizonal and vertical in order to edit/view several files in one editor. When opening the file manager dialog with :E command the file browser dialog should show only in active subwindow but it shows in other subwindows too overriding their contents. This bug is a blocker :-)

It was not the case for port version 9.0.1441. 

Does anyone has this problem too?

Would that be possible to update vim port to latest release 9.0.1627 to see if the bug was fixed in the meantime? :-)

Thanks :-)
Tomek
Comment 1 Tomasz "CeDeROM" CEDRO 2023-06-12 01:49:29 UTC 
Filed a bug at vim github in order to see if this is a known issue:

https://github.com/vim/vim/issues/12527
Comment 2 troy 2023-06-12 04:18:21 UTC 
I am unable to reproduce on the same setup (I also commented on the github ticket)

I have tried ports as well as directly with git tag v9.0.1503.  Have used zsh and your terminal emulator as well as in the console.

I'm wondering if there are library differences, what does ldd /usr/local/bin/vim show on your system?
Comment 3 Tatsuki Makino 2023-06-12 08:22:35 UTC 
Hello.
I am not a vim user :) , however...

If you are using xterm, try this back to 379.
Something is wrong with the part about multibyte characters from xterm-380.

Is it relevant?
Comment 4 commit-hook freebsd_committer freebsd_triage 2023-06-12 13:15:10 UTC 
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=5018cba81365bc233328d6b9bce750256afaa5e6

commit 5018cba81365bc233328d6b9bce750256afaa5e6
Author:     Adam Weinberger <adamw@FreeBSD.org>
AuthorDate: 2023-06-12 13:13:50 +0000
Commit:     Adam Weinberger <adamw@FreeBSD.org>
CommitDate: 2023-06-12 13:13:50 +0000

    editors/vim: Update to 9.0.1627

    PR:             271959

 editors/vim/Makefile | 2 +-
 editors/vim/distinfo | 6 +++---
 2 files changed, 4 insertions(+), 4 deletions(-)
Comment 5 Adam Weinberger freebsd_committer freebsd_triage 2023-06-12 13:19:57 UTC 
First and foremost: I always intend to update vim on the first of every month. If I don't, it's almost always because I forgot, so please don't hesitate to open a PR about it! I've updated vim to 1627.

I couldn't reproduce the problem you described, but I was able to reproduce the behavior in comment #1. I can confirm that that issue is fixed in 1627.

Please give the new version a try and let me know whether it fixes the problem for you.
Comment 6 Tomasz "CeDeROM" CEDRO 2023-06-12 21:45:51 UTC 
Thank you Adam! That fixes the problem :-)

The issue was known and fixed in recent releases :-)

https://github.com/vim/vim/issues/12304