choose-w misaligned (regression)

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Is this related to bug 1875109? A fix for that bug is in the works and is ready for testing. Perhaps you could test that proposed package to see if it fixes your issue?

I'm setting Importance to Low because this bug as reported affects only unusual end user configurations. I therefore don't expect expert help on this bug soon. Feel free to continue using this bug to coordinate efforts, and if you find a specific fix, then we'd be happy to help you land it.

no not related to that bug. i rewrote the description, is it more clear now? frankly i expect this affects virtually everyone, and most folks are just trying to ignore the annoyance.

Hi,

What you describe appears to be an upstream change and it can't be considered as a bug in Ubuntu. There are several threads with requests similar to yours with proposed workarounds which I hope you'll find helpful:

https://github.com/tmux/tmux/issues/1115
https://github.com/tmux/tmux/issues/1977
https://unix.stackexchange.com/questions/400009/how-to-get-tmux-to-only-show-windows-when-using-choose-tree

I'm marking this bug report as Incomplete for the moment. If you agree this is not actually a bug in Ubuntu then please change the report status to Invalid, otherwise comment back, change the report status back to New and we'll look at it again. Thanks!

agreed, an upstream issue, and agree, those threads are the same issue.

however your comment seems to advocate the idea that launchpad isn't a venue for bugs in software distributed by ubuntu. while i understand that idea, i think the majority opinion, even the design intention, is that launchpad is a venue of choice even for bugs that originate upstream, and it's very common for launchpad bugs to refer to other bug database entries, especially upstream ones.

imo the threads you mention justify this bug being marked 'confirmed'.

Hello gregrwn and thanks for confirming those threads are about this very issue.

There's certainly place in Launchpad for upstream bugs, provided that they're recognized as such. In this case it doesn't seems that upstream recognizes the new behavior as a bug (this is why in comment 4 I refer to it as an "upstream change", and not to an "upstream bug"). Given that upstream doesn't recognize the change as a bug, and that the change doesn't affect Ubuntu users so badly to justify permanently diverging from upstream to make the package behave differently from what upstream intended, it is difficult to consider this "a bug in Ubuntu".

I think the most appropriate status for this report is Opinion ("Doesn't fit with the project, but can we discussed"). This is not to dismiss your report, but rather not to set false expectations.

A solution is available, with a updated copy of tmux, and a recipe, see:

http://github.com/tmux/tmux/issues/2636#issuecomment-817542083

Thanks for that pointer! AIUI the commit implementing the functionality you were looking for is:

https://github.com/tmux/tmux/commit/cd208c9d72df79a34024df6b8eb8f984613de8ef

which has been first released in tmux 3.2a. That's not (yet) in Ubuntu (not even in the current devel release), but it's already in Debian testing. This means the functionality will land in Ubuntu with the next sync from Debian, during the 22.04 development cycle.

The bug doesn't qualify for a SRU (see [1]), but good to know it will be address in time for the next LTS. (An updated package could be provided via a backports, but first we need the a newer tmux to land in Ubuntu.)

I'm updating the bug status a bit to reflect all of this.

[1] https://wiki.ubuntu.com/StableReleaseUpdates#When

Jammy now ships tmux 3.2a, so I'm marking the devel task as Fix Released, but adding Focal, Hirsute and Impish as Triaged with Importance: Wishlist.

Hirsute is no longer in support.

Impish has reached end of standard support.

this was resolved, see https://github.com/tmux/tmux/issues/2636#issuecomment-817542083