You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Having a single profile for exporting configurations across machines means both machines have to have same setup (i.e. same apps and hardware like number of screens). Otherwise the export might break the importing machine.
Describe the solution you'd like
Having multiple profiles (or nested profiles) could allow saving/exporting the configurations as separate files, or a single zip file with subdirectories for each profile.
While importing, you could import only the files that you are interested in or the whole file but present an interactive shell to select what parts (subprofiles) you want to import.
Describe alternatives you've considered
Today I would need to switch profiles manually by updating the config file before each save/export and store/manage the profiles myself somewhere and hope I don't save with the wrong profile.
Additional context
I distro hop seldomly, so I can use the export just fine between hops with the same computer and programs. But I also have a laptop which has different number of screens, resolution and installed programs. I would like to partially share my PC config with my laptop without losing the capability of distro hoping with the full config.
The text was updated successfully, but these errors were encountered:
Just to clarify since you call profiles the actual saved configurations. When I say profiles, I refer to the schema stored in konsave's config file. If I can have multiple schemas, I can generate different profiles or a smarter profile that can then be imported partially
JurgenCruz
changed the title
Multiple profile support
Multiple profile schema support
Feb 3, 2024
Having a single profile for exporting configurations across machines means both machines have to have same setup (i.e. same apps and hardware like number of screens). Otherwise the export might break the importing machine.
This is a problem that I have encountered a lot of times myself. The solution you've provided is also quite neat but I'm thinking of more solutions. Stay tuned for this. I'll start working on issues during summer break (June-July), so let's see what I can come up with to solve this :)
Prayag2
changed the title
Multiple profile schema support
[Feature Request] Multiple profile schema support
May 18, 2024
Thanks! that is great news. I actually went ahead and wrote my own tool from scratch, but I also like when you have different options of achieving the same thing. 😃
Is your feature request related to a problem? Please describe.
Having a single profile for exporting configurations across machines means both machines have to have same setup (i.e. same apps and hardware like number of screens). Otherwise the export might break the importing machine.
Describe the solution you'd like
Having multiple profiles (or nested profiles) could allow saving/exporting the configurations as separate files, or a single zip file with subdirectories for each profile.
While importing, you could import only the files that you are interested in or the whole file but present an interactive shell to select what parts (subprofiles) you want to import.
Describe alternatives you've considered
Today I would need to switch profiles manually by updating the config file before each save/export and store/manage the profiles myself somewhere and hope I don't save with the wrong profile.
Additional context
I distro hop seldomly, so I can use the export just fine between hops with the same computer and programs. But I also have a laptop which has different number of screens, resolution and installed programs. I would like to partially share my PC config with my laptop without losing the capability of distro hoping with the full config.
The text was updated successfully, but these errors were encountered: