parent folder in connection name
Some time ago you implemented a feature I asked for, where you show the parent name of a connection in the tab group. This helps if you have all your subconnections named "SSH" and you have more than one of them open.
I just realised, that this doesn't help if the connection itself is a parent. I have quite a number of clients with the same naming scheme, like srv001, srv002 etc. and if I open mutiple of these connections it looks like this:
all these connections are in folders named for the client so it woul be super helpful to have the option to display the parent folder as well.
Maybe you can implement it semi-intelligent so that the parent folder name only appears if more than one tab with the same connection name is open (you could do it for this option as well);
All Comments (10)
Hello,
An internal improvement ticket was opened and I've asked the engineers if the implementation you requested could be done.
I will update you once I receive word from them.
Best Regards,
with the new release out of the way, any chance to get this implemented?
Hello,
We have increased the priority and will try to add this for 2023.2 (or a minor update of 2023.1).
Regards,
Hubert Mireault
Hello perler,
You can currently display folders in the tab groups by adding it with the Column Chooser. Does this work for you?
Regards,
Jafran Majeau
b127c250-e461-475e-b787-c2f54b5f0dfe.png
ok, but this doesn't really work, when you have the tab groups vertically, especially as this shows the whole folder path and not just the parent:
c1e0e88c-2dc1-439e-8566-4338f1a057a9.png
Hello,
We've added a new option Show folder name on duplicate named entries in Tab Groups in the same section as the previous feature. This should provide the behaviour you are looking for, and it should be available for 2023.2.7.
Regards,
Jafran Majeau
ok, I enabled it in 2023.2.9 but it doen'st seem to work?
7f647b80-870a-4bd9-82bd-a2e97fb573be.png
Hello,
Our engineering department is currently investigating this matter.
We will be in touch as soon as we will have an update to provide.
Best regards,
James Lafleur
Hello,
We've found and fixed the problem. This should be available for the 2023.3 version.
Regards,
Jafran Majeau
Hello again,
We've managed to push up the version for the fix to 2023.2.13.
Regards,
Jafran Majeau