The small inconsistency there was intentional, but I have a couple of suggestions to fix it.
The problem is this: the second column in the output of snap interfaces, the Plug one, will often have multiple entries (e.g. all plugs connected to :x11, for example). If we display it first, we end up with a very wide column first pushing the second column too far apart for the eye to be able to comfortably related the two.
So, I see two possible ways to fix this, and perhaps we can implement both of them:
1. Instead of aggregating plugs on a single line, we can break them down so that each line has a single slot and plug pair.
2. We can tweak "snap connect" so that it accepts its arguments in any order. This works fine because a snap cannot have a plug and a slot with the same name, so any pair is necessarily unambiguous.
The small inconsistency there was intentional, but I have a couple of suggestions to fix it.
The problem is this: the second column in the output of snap interfaces, the Plug one, will often have multiple entries (e.g. all plugs connected to :x11, for example). If we display it first, we end up with a very wide column first pushing the second column too far apart for the eye to be able to comfortably related the two.
So, I see two possible ways to fix this, and perhaps we can implement both of them:
1. Instead of aggregating plugs on a single line, we can break them down so that each line has a single slot and plug pair.
2. We can tweak "snap connect" so that it accepts its arguments in any order. This works fine because a snap cannot have a plug and a slot with the same name, so any pair is necessarily unambiguous.