Is there seriously no global settings in the IntelliJ IDEs in the year 2017?!
I spent all this time toggling settings while working in my project only to find out it was project-specific settings.
Then I went to apply them globally by accessing Project Defaults and setting those.
But when I went to make a new project, and move a file into its directory, all my "Project Default" settings stopped working and were replaced. Why is loading a file from one directory into a project via the IDE's Move File option something that would discard default settings? A _fresh_ project with no settings set, and a file not from a previous project get combined, and they magically discard default project settings? With what, some conjuration of random stuff pulled from the void? I didn't waste my time trying to figure it out; I was too busy trying to calm my anger at the prospect of setting my settings for a _third_ time!
This is a hateful UX. Why are you making the default settings UX so complicated? Set & forget, you know? Having version-controlled and project-specific settings are great! But why are you insisting I use them by _default_?
Is this is some kind of generalized UX design justification? You're making my productivity worse by depriving me of basic UX expected across most modern and legacy IDEs. If I have one of the IntelliJ IDEs dedicated to a single language, why the are you expecting me to change my settings every project as my default intended desire?
Please sign in to leave a comment.
Please file a bug at https://youtrack.jetbrains.com/issues/IDEA and describe what specific default settings stopped working for you. Attach IDE configuration (File | Export Settings) and a sample project to reproduce. Thank you.
Sorry Serge, but I'm not going to pour over the settings for that; I'm too angry and frustrated to play Bug-Hunt for you when you won't even address my questions.
I understand your frustration, but more details would be appreciated so that we can reproduce and fix it.
Please address why settings default to Project-specific settings instead of Global/default? That is a question I asked that requires no bug-hunting from my end. This is a bad UX, especially the language-specific JetBrains IDEs. Are things like code style Inspections nested too deeply inside other settings that don't play well at the global level? If so, I strongly suggest they be de-coupled. It's a really bad out-of-the-box UX. Why is it like this?
Ok, at least you've specified that you are talking about the code style settings, please see the related issues:
https://youtrack.jetbrains.com/issue/IDEA-106966
https://youtrack.jetbrains.com/issue/IDEA-154618
https://youtrack.jetbrains.com/issue/IDEA-170928
https://youtrack.jetbrains.com/issue/IDEA-165100
Code style can be stored either in a project or in IDE settings, you can see IDE on the right of the profile name if it's stored globally. Modifying this profile will affect all the projects that are set to use the same IDE profile:
Thanks, Serge; I;m going to guess that I somehow triggered this:https://youtrack.jetbrains.com/issue/IDEA-154618
ISSUE 1
If you have a project open, "Copy to Project" moves (rather than copies" an inspection profile's XML file from {idea.home}/config/inspections to .idea/inspections. This means that that inspection profile is no longer available to all the projects that use it. When you reopen those projects, they just switch to "Default".
What worries me is that this other part of the issue has been around since at least _2013_, which is why I've emphasized the year in the subject for this question.
If this isn't going to be addressed anytime soon I would like to know. A four-year old major UX bug in a pay-wall product is not the level of quality, support, or turnaround time that I expected. That's not on JetBrain's product line, but my own personal expectations. I just need state of affairs clarified if you can since I see no meaningful action taking place in those bugs for their Comments or History.
There is a private comment from the responsible developer stating that ISSUE 1 was addressed on 14 Apr 2016.
Addressed as in fixed, or addressed as in, someone acknowledged this bug circa a year ago and hasn't done anything since?
Addressed as fixed: https://github.com/JetBrains/intellij-community/commit/16166c8584b3ae0741d309cc705219506ca84184.
Thanks, Serge!!