PureBoard

C:\Dokumente und Einstellungen\Falko\Anwendungsdaten\PureBasic\PureBasic.prefs

C:\Dokumente und Einstellungen\John\Anwendungsdaten\PureBasic\PureBasic.prefs

C:\Dokumente und Einstellungen\Lisa\Anwendungsdaten\PureBasic\PureBasic.prefs

Commandline options for the IDE

The PureBasic IDE allows you to modify the paths and files being used from the commandline. This allows you to create several shortcuts that start the IDE with different configurations for different users, or for different projects.

Possible commandline options are:


/P <Preferences file> loads/saves all the configuration to/from the given file.
/T <Templates file> loads/saves the code templates from/to the given file.
/A <tools file> loads/saves the configuration of the external tool from/to this file.
/S <Source path> overwrites the "Source path" setting from the preferences
/E <Explorer path> starts the Explorer tool with the given path
/L <Line number> moves the cursor to the given line number in the last opened file
/NOEXT disables the registering of the .pb extension in the registry.
/LOCAL puts all preferences in the PureBasic directory instead of the user profile location.
/PORTABLE the same as /LOCAL and /NOEXT combined

The default files for /P /T and /A are saved in the %APPDATA%\PureBasic\ directory on the system.

The /NOEXT command is useful when you have several different PB versions at once (for testing of beta versions for example), but want the .pb extension to be associated with only one of them. The /PORTABLE command can be used to keep all configuration inside the local directory to easily copy PureBasic to different computers (or run it from USB sticks for example).

You can also put filenames of source files to load on the commandline. You can even specify wildcards for them. (so with "*.pb" you can load a whole directory.)

[HKEY_CLASSES_ROOT\Applications\PureBasic.exe\shell\open\command]
@="\"C:\\Programme\\PureBasic\\PureBasic.exe\" \"%1\"