Index | Thread | Search

From:
Frederic Cambus <fred@statdns.com>
Subject:
Re: [new] lnav 0.12.1
To:
Landry Breuil <landry@openbsd.org>
Cc:
ports@openbsd.org
Date:
Fri, 3 May 2024 14:45:39 +0200

Download raw body.

Thread
  • Landry Breuil:

    [new] lnav 0.12.1

  • On Fri, Apr 26, 2024 at 10:41:46AM +0200, Landry Breuil wrote:
    
    > > On my machine it creates ~/.config/lnav, not ~/.lnav, and removing the
    > > ~/.config/lnav directory unfortunately doesn't change anything, it still
    > > crashes early at startup.
    > 
    > it probably does funky things depending on $TERM.
    > 
    > it works fine within tmux where TERM=screen, it crashes in
    > xfce4-terminal (where here TERM=xterm-256color) but works fine if i
    > manually set TERM=xterm.
    > 
    > same thing with alacritty, it crashes if TERM=alacritty (the default)
    > but works fine with 'TERM=xterm lnav'
    > 
    > you seem to be a guy with interest in low-level terminal stuff :) grep
    > -r TERM yields many things in lnav's code... and there seem to be
    > related issues upstream, cf https://github.com/tstack/lnav/issues/570
    > and https://github.com/tstack/lnav/issues/1192 at least. But it shouldnt
    > crash like this :)
    > 
    > in the meantime, here's a port of 0.12.2, still building here... it
    > might give better results, or not.
    
    This version does indeed solves the issues, it runs perfectly in the
    terminals I previously tested with, and it exits gracefully in case
    TERM is set to an unknown option:
    
    $ TERM=puffy lnav
     error: unable to open TUI
     reason: the terminfo database could not be found
    
    Looks good to me for import now, OK fcambus@.
    
    
    
  • Landry Breuil:

    [new] lnav 0.12.1