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

lnav not compatible with warp terminal anymore #1434

Closed
spe888 opened this issue Mar 25, 2025 · 1 comment
Closed

lnav not compatible with warp terminal anymore #1434

spe888 opened this issue Mar 25, 2025 · 1 comment
Labels

Comments

@spe888
Copy link

spe888 commented Mar 25, 2025

lnav version
v0.12.4 is the latest

Other Details:
COLORTERM=truecolor
LC_CTYPE=UTF-8
TERM=xterm-256color
TERM_PROGRAM=WarpTerminal
TERM_PROGRAM_VERSION=v0.2025.03.12.08.02.stable_03
Terminal Name: Warp
Terminal Version: v0.2025.03.12.08.02.stable_03

Describe the bug
Starting lnav fails to start:

✘ error: unable to open TUI
 reason: unable to initialize notcurses Unknown error: 316
 = help: The TERM value of “xterm-256color” is not known.  Check for your terminal in https://github.com/dankamongmen/notcurses/blob/master/TERMINALS.md or use “xterm-256color”

To Reproduce
Steps to reproduce the behavior:
Install lnav using brew brew install lnav, then start lnav lnav, and the error happens. But lnav worked on a older version before i upgraded a while ago (can't remember the version i had before).

@spe888 spe888 added the bug label Mar 25, 2025
@tstack
Copy link
Owner

tstack commented Mar 25, 2025

This was mentioned in #1413 and I think it's fixed on the top-of-tree now.

@tstack tstack closed this as completed Mar 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants