Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefs changes should propagate to all terms, maybe? #80

Open
RyanHope opened this issue Jan 29, 2012 · 1 comment
Open

Prefs changes should propagate to all terms, maybe? #80

RyanHope opened this issue Jan 29, 2012 · 1 comment

Comments

@RyanHope
Copy link
Owner

Right now if there are multiple cards open and prefs are changed from one of the cards those changes are reflected on that term. If you then switch to a different card and open the prefs they will reflect the settings but the term will not. I am not sure what the proper behavior should be exactly but it seems like something needs to be done here.

@dtzWill
Copy link
Collaborator

dtzWill commented Jan 29, 2012

While I'm not sure of the implications (what communication do we have across different cards?), universal settings seems easiest.

The idea of per-card settings is nice, but seems to be more trouble than it's worth (how would one 'restore' such settings--track the card index?). A better idea, if anyone wants to go in this direction, might be to allow users to have preference 'profiles' that they can managed (and changes are set universally to all users of that profile), with of course a default profile. Then, if they like spawning a second terminal with a different set of preferences they can do so and just change the profile after launch. Or something.

Anyway, brainstorming aside (my 'idea' is almost certainly not worth implementing any time soon) I vote we simply lock all cards to using the same 'global' settings, and universally update the cards when they are changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants