Per-project config settings #5168
Comments
|
I'd love the ability to specify a configuration directory on the command line... the use case I have in mind is using a separate configuration when invoked via git's Is that a part of this feature? Should it be? Should this be a separate enhancement request? |
|
👍 |
|
👍 in the form of core support for EditorConfig. |
|
👍 Lack of per-project settings when moving between projects with different tab spacing is a real pain. |
|
👍 on the different tab spacing pain. |
|
A must-have. |
|
👍 must-have feature |
|
+1 |
|
Yes, please |
|
Would be useful in deed. 👍 |
|
+1 |
|
You can use this extension. |
|
+1 Atom Project Manager is definitely a good thing for this purpose. However, it still requires the projects to be added to the user's configurations. Maybe what could be better is some kind of project file that can be committed into version control in the source tree. Then developers of the same project could do something like |
|
@tschijnmo Exactly! Sublime Text allows you to place a project.json file within the project root folder with all the project specific settings. This file can become part of your source control so everyone has the same settings. |
|
+1 |
|
👍 this would actually be a very good idea! |
|
+1 |
1 similar comment
|
👍 |
|
A project file isn't the core-level solution here. Atom understands a single layer of configuration right now. Atom needs to be able to understand layered configuration (2-layer but still multi-layer). The primary problem with existing solutions (eg. project manager) is they just modify the global configuration on project load. If you were to touch the global configuration at all (even just hiding the menu bar) it would actually commit the current configuration as the new global configuration. The core solution can be as simple as |
|
+1 |
|
I am part of a group of students at Cornell University working on creating a package for this feature by utilizing the changes made in this pull request: #16845 Although the referenced pull request is still only included in the beta build, we hope that when it is included in the stable version of Atom, our package will be able to fully support per-project config settings by utilizing a local project config file. |
|
@tyleri - Does your PR manage merging configs - can you have base settings, and then the per-project configs override/merge with? For example:
Would Project 1 get |
|
@JustinAiken: Question better asked under the PR methinks? In this issue, it could easily get lost... |
|
@JustinAiken From my testing, it seems like the per-project configs override the base settings. In your example, Project 1 would get The package we are developing may or may not follow this behavior - we are still in the midst of testing and will be asking for feedback from the open source community in the coming weeks. |
|
My team is wrapping up development on the package that I spoke about above. These coming two weeks we are conducting user tests and would greatly appreciate if you could help demo our package and provide feedback. This would take 30-45 minutes to install and use the package, and then we would ask for some feedback so we can make changes. Please email me at tyi3@cornell.edu if you’re interested! |
|
@tyleri any info on whether or not this will allow us to save custom window layout per project? For instance, I currently have this setup for a LaTeX project And having this be setup automaticaly as soon as the project is open would be really useful, rather than having to redo it all everytime the project is open again |
|
This would also be very useful for me as well. |
|
Just to report back here, I got a chance to Skype with Tyler. They did a nice job. There are a few bugs to squash but it was in good shape last week. @LookItsBlu I did not test that out, but I don't think it will. It's basically anything that's in this atom config |
|
I am the faculty sponsor for the project that @tyleri and team have been working on. Their work has been released as the Atomic Management package: https://atom.io/packages/atomic-management Please install the package and let us know how it works. We know there will be some initial issues, so please feel free to submit an issue or a pull request. Thanks again for everybody that helped make this package a reality! |
|
I suggest not to add comments like "Thanks!" "I'm gonna try it!" because if a lot of them come they would act like spam and force users to disable notifications which could be useful to track for issues on the package |
|
@harmsk I'm sure that this new package is good, but is it proposed that this should become the standard (i.e. officially sanctioned) package for config management in atom? As per my above comments, that is the most important objective. Without being recognised as the standard, it is not feasible for other packages to be able to integrate and thus is of very limited utility. |
|
Why not just use https://atom.io/packages/editorconfig? |
It was actually my first idea coming from Sublime, but I'm afraid for me doesn't work as needed. To be precise: I have projects with files encoded in UTF-8 and projects with ISO-8859-1. This can be handled by EditorConfig's
|
|
Would absolutely love this to be a thing. It's useful enough to be core functionality, we shouldn't have to install a separate package for this. |
This comment has been minimized.
This comment has been minimized.
|
What is the state of this now 4.5 years later? |
|
@Tails everybody went to VSCode 😞 |
not everybody 👅 |
|
Just published Here's an example config for {
"prettier-atom": {
"formatOnSaveOptions": {
"enabled": true
}
}
}This is all thanks to the API @philipfweiss added in #16845 back in Early 2018 🙇 |
|
@steelbrain - how does it do w/ merging config settings? For example, if I have |
|
@JustinAiken It behaves much like VSCode config, in that it only ever loads up whatever is at the workspace root. If you want it to respect the config in |
|
I see we have
|
|
seems, no updates for last 3 years ... |
|
I love this reminder on how long ago it is already that I last used Atom because of exactly this issue. |
No description provided.
The text was updated successfully, but these errors were encountered: