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

Configuration #1069

Open
noughtmare opened this issue Mar 5, 2018 · 1 comment
Open

Configuration #1069

noughtmare opened this issue Mar 5, 2018 · 1 comment

Comments

@noughtmare
Copy link
Member

noughtmare commented Mar 5, 2018

First of all I want to make clear that by configuration I mean simple configuration like font size or enabling line numbers.

I've done some thinking and I came to the conclusion that there are multiple places where things can be configured:

This list might not even be complete. I think we can do better! I suspect there is a more uniform way to handle configuration.

There are some points where I think we can improve the current situation:

  • Make a uniform configuration data type that can be used instead of the ad-hoc configurations listed above.
  • Think of a mechanism for handling and configuring the precedence of these configurations.
  • Use extensible records for configuration instead of the DynamicState type (for example using Data types à la carte).
  • Read configurations from a file so that users no longer have to restart their editor to change a minor setting.
@junjihashimoto
Copy link
Contributor

I do not care about multi-configurations and extensible records, if we can validate the configurations.
But I hope serializable and not serializable data are separated. Not serializable data is like IO-actions.
I am trying last one(configuration-file) like this.
The configuration file can not include keymap, as the map is not serializable data.

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