Fulltext results:
- 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''
- readme_macos @guide:2.0
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The packages will not be copied or m... 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
- readme_windows @guide:2.0
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The packages will not be copied or m... 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 ... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime
- 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''
- 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''
- readme_macos @guide:2.3
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... 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.
- readme_macos @guide:2.2
- arameters:<code> -iwad path1 path2</code> * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... 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.
- readme_macos @guide:2.1
- ed in the Doomsday Script command prompt. * The configuration file //~/.doomsday/paths // is checked for ''iwaddir''... "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... 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.
- readme_windows @guide:2.2
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- readme_windows @guide:2.1
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- readme_windows @guide:2.3
- "..." button under the tab title), or go to Data Files settings (see <html><a href="#config">Configuration</a></html>). The mods will not be copied or moved... just erases the contents of the //persist.pack // file that stores configuration variables and UI state. The affected variables in... esolution when in fullscreen mode. <html><a name="files"></a></html> ===== Files ===== Your runtime files are stored in a folder called //AppData\Local\De
- customizing_snowberry @snowberry
- ===== Configuration files ====== //See also:// [[snowberry_configuration_file_syntax]] The term //configuration file// is used... 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 Doomsd... y's [[ded_file]]s. In conf/ folder there is four configuration files that are used to configure Snowberry and Doomsday Engine: * [[appearance.conf]]: Snowberry appearance configuration; defines the styles of Snowberry UI labels * [[
- 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... ervices with which they find out the locations of configuration, profile and meta data files. * plugins.py – loads all the plugins from the... 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 directories in an alphabetical order. From these files Snowberry then loads the possible user interface widgets to be shown in