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#31535 - [vimpager] Does not open files correctly as a root
Attached to Project:
Community Packages
Opened by Tommy (tommy) - Friday, 14 September 2012, 11:30 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 15 September 2012, 09:25 GMT
Opened by Tommy (tommy) - Friday, 14 September 2012, 11:30 GMT
Last edited by Florian Pritz (bluewind) - Saturday, 15 September 2012, 09:25 GMT
|
DetailsDescription:
After upgrading from vimpager-1.7.1-1-any to vimpager-1.7.2-1-any, it no longer correctly displays any file or the standard input (when piped to), when ran as a root. Typical scenario: # less any-file E282: Cannot read from "-E" Press ENTER or type command to continue 2 files to edit E282: Cannot read from "--cmd" Press ENTER or type command to continue Vim then opens with an empty buffer, statusbar containing: "let vimpager=1 | runtime! macros/less.vim" [New DIRECTORY] The second buffer contains the data to be viewed, with no syntax higlighting. Additional info: * package version(s) vimpager-1.7.2-1-any vim-7.3.659-1-x86_64 vim-runtime-7.3.659-1-x86_64 * config and/or log files etc. No custom configuration. (The root user does NOT even have a .vimrc file.) Steps to reproduce: # less any-file Interestingly, it works fine as a normal use but fails as a root. |
This task depends upon
Closed by Florian Pritz (bluewind)
Saturday, 15 September 2012, 09:25 GMT
Reason for closing: Fixed
Additional comments about closing: vimpager 1.7.3-1
Saturday, 15 September 2012, 09:25 GMT
Reason for closing: Fixed
Additional comments about closing: vimpager 1.7.3-1
Comment by Florian Pritz (bluewind) -
Friday, 14 September 2012, 18:46 GMT
Please report this issue on the upstream tracker: https://github.com/rkitover/vimpager/issues