Fulltext results:
- doomsday @guide:2.3:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- doomsday @guide:2.2:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- doomsday @guide:2.1:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[guide/configuration|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- readme_macos @guide:2.1
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki. <html><a name="environ"></a></html> ===== Environme
- readme_macos @guide:2.2
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki. <html><a name="environ"></a></html> ===== Environme
- readme_macos @guide:2.3
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[guide/configuration|syntax of the file]] is documented in the wiki. <html><a name="environ"></a></html> ===== Environme
- doomsday @guide:2.0:man
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ///etc/doomsday/paths // : <html><a name="paths_file"></a></html> System-level paths configuration (''basedir'', ''libdir'', ''iwaddir''). This is checked after //~/.doomsday/paths //. The [[Configuration#Unix_system-level_config_files|syntax of the file]] is documented in the wiki. ; //~/.doomsday/de... ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''
- customizing_snowberry @snowberry
- ===== Configuration files ====== //See also:// [[snowberry_configuration_file_syntax]] The term //configuration file// is used here to refer to many kinds of files: * The .[[conf]] files tha... plugin bundles. Addons and plugins can customize Snowberry by providing [[metadata|their own configuration data]]. For example, an addon can define settings... gs_tab]] when the addon is selected for loading. Snowberry has its own format for configuration files. It is a text-based format reminiscent of D
- readme_macos @guide:2.0
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... files: ; //~/.doomsday/paths // : Customized file path configuration (''basedir'', ''libdir'', ''iwaddir''). The [[Configuration#Unix_system-level_config_files|syntax of the file]] is documented in the wiki. <html><a name="environ
- readme_windows @guide:2.2
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... //runtime/doomsday.out // : Log message output file. ; //runtime/savegames/ // : Folder containin
- readme_windows @guide:2.3
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... //runtime/doomsday.out // : Log message output file. ; //runtime/savegames/ // : Folder containin
- readme_windows @guide:2.1
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... //runtime/doomsday.out // : Log message output file. ; //runtime/savegames/ // : Folder containin
- readme_windows @guide:2.0
- just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... ed in Audio Settings (see <html><a href="#config">Configuration</a></html>). ; ''-verbose'' | ''-v'' : Print ... //runtime/doomsday.out // : Log message output file. ; //runtime/savegames/ // : Folder containin
- plugin @snowberry
- le is to make it easier for other modules to read file contents considering configuration, profile and meta data files. * paths.py – offe... d decide a name for your plug-in. The name of the file is important in a sense that Snowberry looks in and loads (in runtime) the files and dir... tories in an alphabetical order. From these files Snowberry then loads the possible user interface widgets to be shown in the application when appropriate. Snowberry plugins folder already contains some built-in plu
- localizing_snowberry @snowberry
- lization is available to use ====== See also ====== * [[snowberry_configuration_file]] * [[customizing_snowberry]]