Kang-Che Sung (宋岡哲)

@fpletz I've adapted some part of your patch to the new PR, #1698. Would you please help test it out to see whether it works? It can supersede this PR.

@fasterit The point is when the mouse cursor is outside the selected item. The user would expect the right mouse button triggers an event of _the item on the mouse...

> 2. there is no best-practice / design / UX expectation for ncurses and right mouse buttons > 3. some DEs will hijack it anyways for context menus The user...

Can the OP (@eMPee584) clarify what problem this PR is trying to fix? Without a report of an issue, I can't understand why this PR is needed.

> ```c++ > extern "C" { > auto src1(void* p1, size_t old_len, size_t new_len) -> void* { > void* p2 = malloc(new_len); > memcpy(p2, p1, old_len); > free(p1); > return...

> > > extern "C" { > > > auto src1(void* p1, size_t old_len, size_t new_len) -> void* { > > > void* p2 = malloc(new_len); > > > memcpy(p2,...

How about another case? Suppose you call `src1(p1, 0, 8)`, and that the allocation of `p2` fails within the `src1` function. The `realloc` function is supposed to keep the original...

> ```c++ > extern "C" { > auto src1(void* p1, size_t old_len, size_t new_len) -> void* { > void* p2 = malloc(new_len); > memcpy(p2, p1, old_len); > free(p1); > return...

I fear the option of `--enable-nvidia-jetson` will make future board-specific customizations add similar configure options. That would make things unmaintainable.

Another problem is the conflict with #1620, which is an attempt to unify the GPU meter structure to one interface.