github/greenshot
1
0
Fork 0
mirror of https://github.com/greenshot/greenshot synced 2025-08-22 14:24:43 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update 2013-04-16-what-is-the-best-way-to-control-greenshots-configuration-at-install-time.markdown

Browse source
This commit is contained in:
mischl 2020-04-17 21:08:09 +02:00 • committed by GitHub
commit da1a562604
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
_faqs/2013-04-16-what-is-the-best-way-to-control-greenshots-configuration-at-install-time.markdown
View file

@ -30,7 +30,7 @@ Greenshot knows of 3 different files, which are loaded in the following order:
2. greenshot.ini: this is the normal file, with all the settings of the user, which is written by Greenshot. This overrules the settings in the greenshot-defaults.ini file.
3. greenshot-fixed.ini: has settings which will overrule all settings in the files above.
Greenshot will look for every mentioned file, in the described order, first in the same location as the executable (e.g. installation directory) and if there is not there than in %APPDATA%\Greenshot (e.g. ```C:\Users\USERNAME\AppData\Roaming\Greenshot\```).
Greenshot will look for every mentioned file, in the described order, first in the same location as the executable (e.g. installation directory) and if there is not there than in %APPDATA%\Greenshot (e.g. ```C:\Users\%USERNAME%\AppData\Roaming\Greenshot\```).
The configuration is build from zero, setting for setting, by using the following 4 steps: