byobu forcibly stops 256colors from happening on screen

Bug #1173354 reported by Chow Loong Jin on 2013-04-26
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
byobu (Ubuntu)
Low
Unassigned

Bug Description

  affects ubuntu/byobu

In the following snippet from /usr/bin/byobu, SCREEN_TERM is set to "screen"
instead of "screen-256color" when facing a terminal that has 256 colors.

--------------------------------------------------------------------------------
  if $BYOBU_TEST tput >/dev/null; then
   if [ "$(tput colors 2>/dev/null || echo 0)" = "256" ]; then
    SCREEN_TERM="-T screen"
   fi
  fi
--------------------------------------------------------------------------------

--
Kind regards,
Loong Jin

Related branches

Dustin Kirkland  (kirkland) wrote :

I'm trying to reproduce your error...

What terminal are you using?

Changed in byobu (Ubuntu):
status: New → Incomplete
importance: Undecided → Low

On 09/05/2013 01:55, Dustin Kirkland wrote:
> I'm trying to reproduce your error...
>
> What terminal are you using?

gnome-terminal, with TERM=xterm-256color. The issue here is that there's some
inverted logic there when `tput colors` = 256, as mentioned in the description
-- when tput colors is 256, then SCREEN_TERM="-T screen" instead of "-T
screen-256color". Changing that line quoted in the description fixes the issue.

--
Kind regards,
Loong Jin

Launchpad Janitor (janitor) wrote :

[Expired for byobu (Ubuntu) because there has been no activity for 60 days.]

Changed in byobu (Ubuntu):
status: Incomplete → Expired
Changed in byobu (Ubuntu):
status: Expired → Triaged
Changed in byobu (Ubuntu):
status: Triaged → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package byobu - 5.47-0ubuntu1

---------------
byobu (5.47-0ubuntu1) saucy; urgency=low

  * No changes
  * Re-release due to some minor breakage in my release script
 -- Dustin Kirkland <email address hidden> Tue, 16 Jul 2013 18:19:08 -0500

Changed in byobu (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers