Skip to content
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

Closed
step- opened this issue Jan 31, 2016 · 4 comments
Closed

Vimpager blocked with no output #135

step- opened this issue Jan 31, 2016 · 4 comments

Comments

@step-
Copy link

step- commented Jan 31, 2016

Perhaps I was too quick to close #134, however vimcat filename does work on my system now, unlike vimpager 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

cp /usr/bin/vimcat vimcat; # vimcat_script

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.

rkitover added a commit that referenced this issue Jan 31, 2016
Forgot to run make for 2010892 to install new vimcat into vimpager.
@rkitover
Copy link
Owner

Yeah I bundle everything in vimpager so that it's self contained, I forgot to run make which installs everything into it, sorry, fixed now.

@step-
Copy link
Author

step- commented Jan 31, 2016

Thanks. I noticed the new vimcat_script creates vimcat with permissions 775, whereas the previous one was created 755. Is that change intentional?

@rkitover
Copy link
Owner

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.

@step-
Copy link
Author

step- commented Jan 31, 2016

Thank you.

@step- step- closed this as completed Jan 31, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants