-----Original Message-----
From: <owner-gameoftrees@openbsd.org <mailto:owner-gameoftrees@openbsd.org> <mailto:owner-gameoftrees@openbsd.org <mailto:owner-gameoftrees@openbsd.org>>> on behalf of Stefan Sperling <stsp@stsp.name <mailto:stsp@stsp.name> <mailto:stsp@stsp.name <mailto:stsp@stsp.name>>>
Date: Friday, 10 July 2026 at 23:02
To: "gameoftrees@openbsd.org <mailto:gameoftrees@openbsd.org> <mailto:gameoftrees@openbsd.org <mailto:gameoftrees@openbsd.org>>" <gameoftrees@openbsd.org <mailto:gameoftrees@openbsd.org> <mailto:gameoftrees@openbsd.org <mailto:gameoftrees@openbsd.org>>>
Subject: fix reload of tog log work tree base commit marker


> 
> When run in a work tree, tog remembers the work tree's base commit ID
> at startup and displays a ~ or a * next to this commit in the log view.
> 
> 
> Problem: If the work tree is updated to a different base commit while
> tog is running, tog will keep showing a marker on the previously cached
> base commit, even if the log view is reloaded with Ctrl-L.
> 
> 
> With the patch below, tog updates the base commit marker during Ctrl-L.


thanks for fixing this!


> 
> While here, drop the unused repo argument of set_tog_base_commit().
> 
> 
> ok?


ok jamsek


> 
> make tog log view reload work tree base commit info during Ctrl-L refresh
> 
> 
> M tog/tog.c | 40+ 16-
> 
> 
> 1 file changed, 40 insertions(+), 16 deletions(-)
> 
> 
> commit - d982353621b77ce15a0c2304c8dd4ab4bf58d377
> commit + 4660133613429582d220b8d883b5b138a3cb1b0c
> blob - f4120d83d6a20bb1906c735a5037e405bdfb9790
> blob + fa1d997063a644a4ac763e75014f65aff610f0f3
> --- tog/tog.c
> +++ tog/tog.c
>




-- 
Mark Jamsek <https://bsdbox.org>