Prune has a handful of options which you can configure so that you don't have to set them each time you run. With versions 6 and 7 you had to create a text file and enter the details yourself, but since version 8 this has become a whole lot easier as Prune can save the settings for you.
So you shouldn't need to know anything about the configuration mechanism as long as you use Prune's functions to set the settings you want (eg file locations, GPS device name etc), and then choose "Save settings" from the Settings menu. If you accept the default file location then all your settings should be reloaded next time you launch Prune.
If you do want to tweak the settings file yourself, or wish to choose a different filename, then this page describes how it works.
By default, Prune will try to load a file called .pruneconfig from the current directory (note the dot at the start of the filename). If this file isn't there, it doesn't matter, it'll just be ignored and Prune will use default settings as before. The file won't be created for you if it doesn't exist.
If you save the settings from Prune, it will suggest this file location for you. If you want to use another location for this file, or another filename, then you'll have to tell Prune where it is when you start it next time. You can do this with an extra commandline parameter, like this:
java -jar prune.jar --configfile=h:/gps/pruneconfig.txt
You can obviously set this in any shortcuts or aliases that you're currently using so you don't have to type it in every time. If you specify a file like this and Prune can't find it or can't read it, you'll get a warning message in the console.
You shouldn't need to know the file structure unless you want to manually edit it. But just in case you do, the configuration file is a simple text file, so you can edit it with any editor like Notepad, Kate or gedit. Each line in the file represents a configuration setting, with the format like a java properties file:
key=value
The key should exactly match one of the recognised parameters shown below. Any unrecognised keys will just be ignored.
The file can contain any number of settings, in any order. You can have just one in there or all possible settings.
The following list shows some of the settings which can be defined in the file, in any order:
usb: