Download raw body.
tog: echo numeric prefix of compound key maps
On Mon, Jun 27, 2022 at 01:42:12PM +1000, Mark Jamsek wrote: > On 22-06-26 08:08pm, Christian Weisgerber wrote: > > On 2022-06-26, Mark Jamsek <mark@jamsek.com> wrote: > > > > > Similar to less(1), echo the numbers at the bottom of the screen as they > > > are typed when entering a compound key map (e.g., 123j). > > > > More specifically, less(1) shows the numbers on its status line, > > which just happens to be at the bottom. In tog, it's a the top... > > so maybe that's where the numbers should be echoed? > > I much prefer the current behaviour tbh (i.e., echo at the bottom). We > already echo the search term there (with the '/' key map), which is also > consistent with less(1). So I would rather commit this version, but if > you strongly feel otherwise I'm happy to send through another diff? I think it is fine at the bottom. It stands out visually which is what is most important. It matches the location of the search input prompt. If tog keeps echoing interactive input at the bottom when needed, the user experience will be consistent.
tog: echo numeric prefix of compound key maps