-
Notifications
You must be signed in to change notification settings - Fork 72
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 blocked with no output #135
Comments
Forgot to run make for 2010892 to install new vimcat into vimpager.
Yeah I bundle everything in vimpager so that it's self contained, I forgot to run |
Thanks. I noticed the new |
That's just my umask on the machine I happen to run uuencode on, the perms on the root /tmp directory itself are safe so it doesn't really matter. |
Thank you. |
Perhaps I was too quick to close #134, however
vimcat filename
does work on my system now, unlikevimpager filename
, which blocks with no tty echo; The display issue is exactly as in #134. I can't attach a log file because the trick of adding-V21/tmp/vimlog
in the vimcat script doesn't work anymore, which actually led me to a work-around and, I think, a clue as to what the issue could be.Long story short: changed /usr/bin/vimpager line 523 like so
and now
vimpager filename
works as it should - and-V21/tmp/vimlog
creates a log file.I presume the fix you made in 2010892 didn't carry over to function
vimcat_script
, which seems to serve a frozen version of the vimcat script to the vimpager script. What's that for? Some sort of self-installing method for systems that have vimpager but not vimcat installed? Just curious.The text was updated successfully, but these errors were encountered: