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#72126 - [vim-fugitive] ftplugin directory of version 3.4 is not copied
Attached to Project:
Community Packages
Opened by Tamir Zahavi-Brunner (tamirzb) - Monday, 13 September 2021, 17:38 GMT
Last edited by Toolybird (Toolybird) - Sunday, 14 May 2023, 03:14 GMT
Opened by Tamir Zahavi-Brunner (tamirzb) - Monday, 13 September 2021, 17:38 GMT
Last edited by Toolybird (Toolybird) - Sunday, 14 May 2023, 03:14 GMT
|
DetailsDescription:
vim-fugitive was recently updated from version 3.2 to version 3.4. The issue is that the ftplugin directory, which is needed by fugitive, was added in version 3.3, but it wasn't added to the list of files packaged in the PKGBUILD when updating to version 3.4. This means that some of the git blame functionality doesn't work (as that's the only thing is directory is used for). Steps to reproduce: 1. Open a git-tracked file with vim 2. Run :Git blame 3. Try to use a git blame mapping, such as g? |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 14 May 2023, 03:14 GMT
Reason for closing: Fixed
Additional comments about closing: vim-fugitive 3.4-2
Sunday, 14 May 2023, 03:14 GMT
Reason for closing: Fixed
Additional comments about closing: vim-fugitive 3.4-2
Comment by Tamir Zahavi-Brunner (tamirzb) -
Monday, 13 September 2021, 19:26 GMT
Note that actually, as mentioned by tpope (https://github.com/tpope/vim-fugitive/issues/1835#issuecomment-918444850), the tar.gz downloaded from GitHub should only have the relevant files, so perhaps changing this copy to simply copy everything (cp -r -t "${_installpath}" *) would be the best solution in order to avoid similar issues in the future?