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!
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!
FS#63968 - [vim-nerdtree] problem with CHANGELOG.md file placing
Attached to Project:
Community Packages
Opened by viktor (dviktor) - Monday, 30 September 2019, 20:17 GMT
Last edited by Levente Polyak (anthraxx) - Monday, 30 September 2019, 21:08 GMT
Opened by viktor (dviktor) - Monday, 30 September 2019, 20:17 GMT
Last edited by Levente Polyak (anthraxx) - Monday, 30 September 2019, 21:08 GMT
|
DetailsDescription:
6.1.0 version misplaces CHANGELOG.md Additional info: * 6.1.0 * https://github.com/scrooloose/nerdtree/issues/1044 Steps to reproduce: Start vim and open NERDTree (I use .vimrc method). Change to NERDTree split (Ctrl+W, Ctrl+Left). Enter ? and press Enter. You get the following error: Error detected while processing function nerdtree#ui_glue#invokeKeyMap[1]..78[50]..77[5]..<SNR>29_displayHelp[2]..235[1] ..256[12]..237[2]..nerdtree#version: line 1: E484: Can't open file /usr/share/vim/vimfiles/CHANGELOG.md line 5: E684: list index out of range: 0 Press ENTER or type command to continue Seems like CHANGELOG.md is installed in wrong place: $ pacman -Ql vim-nerdtree | grep CHANGELOG.md vim-nerdtree /usr/share/doc/vim-nerdtree/CHANGELOG.md while NERDTree expects it be in /usr/share/vim/vimfiles/CHANGELOG.md |
This task depends upon
Closed by Levente Polyak (anthraxx)
Monday, 30 September 2019, 21:08 GMT
Reason for closing: Fixed
Additional comments about closing: 6.1.0-2
Monday, 30 September 2019, 21:08 GMT
Reason for closing: Fixed
Additional comments about closing: 6.1.0-2
Comment by Levente Polyak (anthraxx) -
Monday, 30 September 2019, 21:08 GMT
Its still an upstream issue, howver i added a workaround for the meanwhile