Tim Stack
Tim Stack
Well, this slipped through the cracks... sorry. I don't know if you care any more, but I wanted to mention that if you leave the field out of the `line-format`,...
It looks like the response to the "device attributes" escape sequence (`\e[c`) was not recognized. Warp is responding with just `\e[?62c` whereas, I think, other terminals will include some extra...
lnav v0.13.1 has been released and it seems to work fine on Warp v0.2025.09.03.08.11.stable_02, so this can probably be closed.
There's kinda two options: 1. Make the input file a proper JSON-Lines file where there is only a single JSON object per line. Would you be able to move the...
You might be able to workaround by setting `TERM` to `xterm-256color`. Sounds like the alacritty terminfo file is missing. Not sure if it's an issue with the snap build or...
@gigaimage I was able to replicate this and it seems like the DA1 response from the terminal might've changed and it was not recognized by lnav.
@AndydeCleyre > I'm experiencing the same problem with Rio terminal Can you try a recent beta release to see if the problem persists -- https://github.com/tstack/lnav/releases/tag/v0.13.0-beta4
Sounds like things are working better now, going to close. Open a new issue if the latest releases are problematic.
That is your terminal's visual bell. The terminal probably has a setting for it.
> I also couldn't find a way to execute non-SQL commands when a log event occurs. Are you trying to execute an lnav command or a shell program? Most of...