New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vimpager doesn't work with ranger anymore #89
Comments
rkitover
added a commit
that referenced
this issue
Aug 24, 2014
Support the -- option to indicate the rest of the arguments is files, and support using it to pass files that begin with a dash, in both vimpager and vimcat.
This is fixed in master, I'm going to do a release hopefully fairly soon. |
Thank you very much. |
chauncey-garrett
pushed a commit
to chauncey-garrett/vim-vimpager
that referenced
this issue
Sep 23, 2014
# By Rafael Kitover (37) and others # Via Rafael Kitover * 'master' of https://github.com/rkitover/vimpager: (62 commits) moved test scripts to prototypes/, minor fix experimental uudecode awk programs experimental uudecode.pl for Perl 4 and 5 Ignore tput errors. set nomodeline fdl=9999 before file read rkitover#90 support files with leading dash and -- rkitover#89 integrate AnsiEsc git diff fix into vimpager save 731abf0 for upstream patch fix bg bleed in git diff for whitespace errors allow disabling AnsiEsc with var rkitover#88 C man, perldoc and misc improvements perldoc.vim from vimpager-perlmod by trapd00r fix compatibility with GNU sharutils uudecode rkitover#87 print warning if no uudecode binary only extract AnsiEsc if needed add sh fallback for uudecode bundle less.vim with our changes bundle AnsiEsc and redo logic of rkitover#81 (WIP) add SethMilliken to CONTRIBUTORS update CONTRIBUTORS ... Conflicts: Makefile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is described here: https://github.com/hut/ranger/issues/149. I think it makes sense to have a
--
seperator in vimpager as well. It seems to be a standard feature in other pagers. What do you think?The text was updated successfully, but these errors were encountered: