-
Notifications
You must be signed in to change notification settings - Fork 98
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
Error opening terminal: xterm-256color #46
Comments
This suggests that there is no terminfo entry for Could you try running Also just out of interest, which OS are you using? |
|
Ok, that's interesting. Do any other ncurses based programs display the same error? For example, does |
Nano, vim, etc all behave as expected (or they're gracefully degrading, but not that I can tell). I'm not sure if it's related, but under really rare circumstances, However, this |
It's hard to determine what GRV is doing that causes this error. The if (newterm(name, stdout, stdin) == 0) {
fprintf(stderr, "Error opening terminal: %s.\n", name);
ExitProgram(EXIT_FAILURE);
} The Googling the error |
Closing this issue for the following reasons:
As mentioned previously, this is likely to be specific to to the setup of your system in some way. |
@rgburke I have the same issue.
Some information about the environment:
Also I'm using latest version of oh-my-zsh (commit 6ace3cd18dd3cbc0e2631fa98051194b703fe4d7). I've noticed this occurs with bash too, even without a .bashrc.
|
@gnumoksha Thanks for the info. Could you run grv under strace and upload the output here. For example:
will produce a |
The dump was generated in other computer but with similar environment. |
@gnumoksha Thanks for providing the strace output. The issue should now be fixed. Please download a fresh copy of the grv binary:
The following is an explanation of the issue. The lines below hinted at what the problem was:
The ncurses library statically compiled into the released version of grv was finding the terminfo definition at |
@gnumoksha Thanks for confirming it works. Issue #39 is due to a bug in libgit2 for which libgit2/libgit2#4528 was raised. However it doesn't seem like it will be fixed soon as there doesn't appear to be a straight forward solution. So grv may have to revert to running a |
@rgburke I see. But it is a nice project, good job! |
I don't seem to have issues with other applications but
grv
does not want to work for me:The text was updated successfully, but these errors were encountered: