RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1176367 - Leading slash when opening local path with vim fails to start Netrw dir browsing plugin
Summary: Leading slash when opening local path with vim fails to start Netrw dir brows...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vim
Version: 7.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Zdenek Dohnal
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
: 1126479 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-21 01:25 UTC by rob
Modified: 2019-05-17 15:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-17 15:59:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rob 2014-12-21 01:25:57 UTC
Description of problem:
When passing a directory string including leading-slash to vim (e.g. '$ vim /etc/') should open a directory listing provided by the Netrw plugin.
Instead vim states "Illegal file name" and fails to open a directory listing

Version-Release number of selected component (if applicable):
7.4.160-1.el7

How reproducible:
Every time

Steps to Reproduce:
1. With at least the below packages installed:
vim-common.x86_64                       2:7.4.160-1.el7                @base
vim-enhanced.x86_64                     2:7.4.160-1.el7                @base
vim-filesystem.x86_64                   2:7.4.160-1.el7                @base
vim-minimal.x86_64                      2:7.4.160-1.el7                @anaconda

Create a simple directory with files:

$ mkdir ~/testvim
$ touch ~/testvim/somefiles{1..5}

2. Attempt to open the ~/testvim directory for browsing within vim

$ vim ~/testvim/

Returns the error:
"~/testvim/" Illegal file name

The Netrw browsing panel is NOT presented.

3. Attempt without a leading slash WILL work:

$ cd ~/
$ vim testvim/

The Netrw browsing panel IS presented showing the five files

Actual results:
Netrw directory browser is NOT shown


Expected results:
Netrw directory browser IS shown

Additional info:
Also present in Fedora release 20 (Heisenbug) (F21 untested)

Comment 2 Karsten Hopp 2015-03-03 10:55:11 UTC
*** Bug 1126479 has been marked as a duplicate of this bug. ***

Comment 9 Zdenek Dohnal 2019-05-17 15:59:11 UTC
This bug was evaluated by the sub-system and was not considered as a priority for the release, so it's being closed now as WONTFIX. Feel free to re-open the bug if there is a business reason to deliver a fix for this issue.

The issue is fixed in RHEL 8.


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