Allow usage of GUIDs for Dynamic Profile Parents
Summary
I'd like the ability to use a dynamic profile GUID as the designating identifier when setting a dynamic profile's parent.
Currently, if the name of a profile that is used as a parent is changed, the child becomes broken until they're manually updated with the new name. The existing implementation handles collisions between profile names oddly at present as well, but the documentation it reads as though the choice to use only names was made for ease of use, which is completely understandable.
Additionally supporting a parent profile by GUID could resolve these issues, and make iterm2 play nicely with IDE tools like iTerm2 Theme Sync1 ( or anything like it, which changes the profile name, but not profile GUID, when updating its synchronized theme. )
Alternatives
I'm not sure if there really is a better way to go about this.
Concerns
- This is more of an advanced-user feature request, so I'm not sure how useful it will be in the general case
- Looking at how theme management and parentage is currently designed2, I do not believe that performing a second lookup of the Dynamic Parent Name string against the profile GUID map would carry significant performance concerns, however that is admittedly the "fast & hacky" implementation approach.