Terminal number not only for the current instance

Bug #1671761 reported by Javi Cruz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Terminator
Triaged
Low
Unassigned

Bug Description

The bug #314909 that was fixed in previous versions, seems to be broken. After upgrading the version of terminator to terminator-1.91-1.fc24 (from version 0.98-3.fc24, on fedora 24 using GNOME3) , the functionality that allowed to write the terminal number only of the current instance is not working as before, not takes in account all the open terminals you may have.

For example, if I'm running 2 instances of terminator, with 3 terminals in each, in the past, I was able to execute the insert terminal number and will write 1,2 and 3 in the active instance, after the upgrade, it writes 4,5 and 6.

This removes the usefulness of this feature, because if I open a different instance to connect to several servers at the same time, I want to use the sequence of the terminals in the active instance, not taking in account all the other terminals in the non active instance.

Revision history for this message
Javi Cruz (javi-cruz) wrote :

I have seen that in a previous version there were different process for each instance, while with the new version there is only one process for all the instances, and the instances seems to be threads. I think that unless it is done on purpose, the problem is that is counting all the terminals as belonging to only one instance.

Revision history for this message
Javi Cruz (javi-cruz) wrote :

Another collateral issue related with this, seems to be that in the old version, when you were doing a Broadcast All, the broadcast was only for the terminals in the current instance (or window), now affects to all the instances you have open.

Javi Cruz (javi-cruz)
description: updated
Revision history for this message
Stephen Boddy (stephen-j-boddy) wrote :

As per the other broadcast use case, this can temporarily be worked around by disabling the DBus in the preferences. You lose some things as a result (higher resource usage, no remotinator, no other application can make DBus calls to Terminator). It is fair to say that at some point I'm going to have to do some kind of reworking to make some of the features work a bit better with the DBus active.

Changed in terminator:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.