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
err: Test_terminal_vt420 #14595
Comments
The error message in the |
The error message in the `Q:` part seem incomplete.
no, just `Not found in termcap: term=vt420`
…--
shane.xb.qian
|
So where is your terminfo? do you have vt420 in there? |
You may need to install an additional package to get the vt420 term definition (e.g., in Debian it's the ncurses-term package). |
You may need to install an additional package to get the vt420 term definition (e.g., in Debian it's the ncurses-term package).
oh, thanks, yes, but the point was the test may need to check vt420 if was there, which made it be more robust, it would be ran not only at current CI.
// this was a message to author of #14542 @ant0sha
…--
shane.xb.qian
|
Hm, but |
Hm, but `ncurses-term` depends on `ncurses-base` which is an essential package. So I would think one can expect it to be there. In any case, I don't think it makes sense to keep this issue open.
`ncurses-base` was an essential package, but `ncurses-term` looks not,
so this test potentially would be failed, specially the test specifically was for vt420.
…--
shane.xb.qian
|
yes, but it depends on an essential package. Unless you mess with the dependencies, you should have it. In any case, it seems like an issue with that particular environment |
as James said it is an additional package in debain, it should be same as Ubuntu, which default it did not have vt420.
so if that code of that test would check if it had vt420 there firstly should be more robust.
// or you had to assume everyone would install nucurs-term.
…--
shane.xb.qian
|
You have it reversed. ncurses-base is essential, so it will be installed. ncurses-term provides additional, less frequently needed definitions, so it may not be installed. Not sure if there's a better way to check for the term definition (or how portable it is, especially on the BSDs), but one possibility is to only run the test if |
Indeed. So I guess we need something along those lines here: diff --git a/src/testdir/test_terminal3.vim b/src/testdir/test_terminal3.vim
index 223bcc537..588a9e010 100644
--- a/src/testdir/test_terminal3.vim
+++ b/src/testdir/test_terminal3.vim
@@ -935,6 +935,12 @@ func Test_terminal_vt420()
CheckRunVimInTerminal
" For Termcap
CheckUnix
+ let a = system('infocmp vt420')
+ if v:shell_error
+ " reset v:shell_error
+ let a=system('true')
+ throw 'Skipped: vt420 terminfo not available'
+ endif
let rows=15
call writefile([':set term=vt420'], 'Xterm420', 'D')
|
thanks very much.
// just not sure if BSD had `infocmp`, otherwise seems good.
…--
shane.xb.qian
|
Problem: vt420 terminfo entry not found Solution: check existence of terminfo vt420 and infocmp command related: vim#14595 Signed-off-by: Christian Brabandt <cb@256bit.org>
Problem: vt420 terminfo entry not found Solution: check existence of terminfo vt420 and infocmp command related: vim#14595 Signed-off-by: Christian Brabandt <cb@256bit.org>
Steps to reproduce
Q:
A:
#14542 @ant0sha
Expected behaviour
no err
Version of Vim
9.1.354
Environment
linux
Logs and stack traces
No response
The text was updated successfully, but these errors were encountered: