For example, I would like to always exclude .scss in the deployment options. This seems to be a per project setting. Is there a way to change the default files, so that I can always include or exclude certain types of files?
Never mind. I found the answer by going to File -> Default Settings -> Deployment -> Options
Related
With Atomineer Pro Doc for VS, is it possible to have the (some?) settings/preferences saved in the current $(SolutionDir) directory? I realize that there is an option to save/use the prefs.xml file from locations other than the default by setting the Search Paths under General Settings / Preference Storage, but those look to be requiring absolute paths, while my question is specifically about being able to define such paths relative to the current solution/project file.
Yes, it's easy to do this - you just need to use the variable %projectPath% or %solutionPath% in your search paths to make them relative to the current project or solution.
This allows you to use different settings for every project/solution you work in, and also to check the settings into source control so they can be shared across your team easily.
Can I disable / enable the set of rules that are shown by SonarLint for VS? How?
A similar question was already asked in Is there some graphical way to create my own configuration file on SonarLint? but I wasn't able to follow the answer, i.e. did not find the Project/References/Analyzers node in the Solution Explorer, to be able to edit the active rule set file. Can you help me out on this one?
Here is how to open the active rule set of a project:
From there, you'll be able to enable and disable rules:
The path to the rule set file to be used is saved within your .csproj file under the <CodeAnalysisRuleSet>...</CodeAnalysisRuleSet> tag. You can reference the same rule set file from multiple projects, and store the rule set along with your project sources in Git / TFVC if you'd like all developers to share the same rule set.
I've synced my User folder with sublime settings.
But what if I want to use different settings for different machines? For example, in settings of terminal package I define path to Git Bash, and it's
"terminal": "C:/Program Files (x86)/Git/bin/sh.exe"
on one machine, and
"terminal": "C:/Program Files/Git/bin/sh.exe"
on another.
I've tried to use default settings, but they refresh all the time.
Maybe look into this package: https://packagecontrol.io/packages/PackageSync
I've never used it, but according to the README,
PackageSync provides the following user configurable settings:
...
ignore_files [array]
The list of files to ignore when backing up.
So you would want to create a PackageSync.sublime_settings file that has this in it:
{
"ignore_files": "Terminal.sublime_settings"
}
This isn't ideal since it prevents the enitre file from syncing, not just that one entry (the "terminal": "C:/Program Files (x86)/Git/bin/sh.exe" entry), but it should work. (Disclaimer: I have not tried this myself)
Alternative: Possible workaround:
You could also just use the line "terminal" : "~/my_custom_terminal_shortcut" in your settings and then create a ~/my_custom_terminal_shortcut file on each computer that links to the appropriate location
Is it possible to include a file in per-project settings that's been excluded by Sublime Text's global settings?
For example, the global settings have mandated that "*.obj" files (intending files output by a build process) be excluded. Without changing those global settings, I cannot seem to include .obj files (these being 3d model files) in my project. Putting file_exclude_patterns in the "settings" section doesn't override, and adding a file_include_patterns key to the paths section simply filters every other file type out, and yet the .obj files still aren't included! (Apparently exclusion filters are applied after inclusion filters.)
So do I have to change global settings for this then??
I just came across exactly the same problem for exactly the same files.
The only solution seems to be to override the setting in your user settings, minus the "*.obj" wildcard. If you need to exclude those files in other projects or folders within projects, you'll have to specify the setting in your project settings.
Those are asked during the installation, but are not anywhere in config files\tables to change afterwards
EDIT:
The changelog states the following:
[#MODX-760], [#MODX-1080], [#MODX-1528] Added setup option to set new_file_permissions and new_folder_permissions in welcome view
[#MODX-760], [#MODX-1528] Removed new_file_permissions and new_folder_permissions system settings from setup
Seems kinda weird to me to do that... I am still in need to change them, though.
It appears that these should be in your MODX System Settings although I wasn't able to locate them in any of my own MODX installs (all Revo 2.1+). There's a chance they might be redundant or are for some reason not being properly created during installation (in which case it might be an installer bug).
You might be able to override them by adding those settings, like so:
Key: new_folder_permissions
Value: 0755
Do that and then try creating a new folder using the File Manager. Let us know if the correct permissions are then being used. If so I'll look at opening up a bug report for the installer.
They are not in System Settings, as they default to the PHP umask values, as they should. If you want to override them, you can do so by adding the settings "new_file_permissions" or "new_folder_permissions" to your System Settings.
apache/webuser needs to write to:
core/cache
core/export
core/config/config.inc.php [change back after install]
core/packages
core/components
assets/components
EDIT Sorry, take a look here: core/model/modx/processors/system/filesys/folder/create.php
they appear to be hard coded in that file.