update paths for nicrc

Author: 6007135

docs/FAQ.md

@@ -20,10 +20,10 @@ export THEOS=/usr/local/theos
 If this is undesirable, you can tell NIC to revert to symlinking `theos`:
 
 ```console
-$ echo 'link_theos = "1"' >> ~/.nicrc
+$ echo 'link_theos = "1"' >> ~/.config/theos/nicrc
 ```
 
-See [here](/docs/NIC.html#nicrc) for more details on `.nicrc`.
+See [here](/docs/NIC.html#nicrc) for more details on `nicrc`.
 
 ## How do I use Swift in my projects?
 This information has moved to the [Swift](/docs/Swift.html) page.

docs/NIC-Syntax.md

@@ -41,7 +41,7 @@ Each NIC template <span class="required">requires</span> a control file. The con
 - <span class="optional">optional</span>
 - Prompts the user for additional information, which will be stored in *variable*.
 - Optionally supports the inclusion of a default value, which the user can accept by entering nothing.
-- The user is given a chance to override the prompt variable with their <code class="highlighter-rouge">~/.nicrc</code>.
+- The user is given a chance to override the prompt variable with their <code class="highlighter-rouge">nicrc</code>.
 
 <code class="highlighter-rouge"><strong>constrain</strong> "<span class="required">path</span>" to <span class="required">constraint</span></code>
 
@@ -62,7 +62,7 @@ Each NIC template <span class="required">requires</span> a control file. The con
 - The NIC templates that ship with Theos use the `package` constraint to avoid creating unnecessary `control` files.
 
 `link_theos`
-- Used in some templates to include an optional link to theos. Set/overridden by `link_theos` in the user's `~/.nicrc`.
+- Used in some templates to include an optional link to theos. Set/overridden by `link_theos` in the user's `nicrc`.
 - The NIC templates that ship with Theos use this constraint to avoid creating unnecessary `theos/` symlinks.
 
 ### Example <code class="highlighter-rouge">NIC/control</code>
@@ -130,7 +130,7 @@ The `NIC` object represents the current template.
     - Prompt the user for additional information, attaching the user's response to the provided NIC variable.
     - The default value is optional.
     - If *$variable* is not specified, `NIC->prompt(...)` will return the user's response, and will not store it in the template.
-    - The key difference between `prompt(...)` and `NIC->prompt(...)` is that the user is given a chance to override the prompt variable with their `~/.nicrc`.
+    - The key difference between `prompt(...)` and `NIC->prompt(...)` is that the user is given a chance to override the prompt variable with their `nicrc`.
 
 - <code class="highlighter-rouge">NIC->setConstraint(<span class="required">$constraint</span>)</code>
 

docs/NIC.md

@@ -97,8 +97,13 @@ The templates included in this legacy templates module:
 * **notification_center_widget-7up**: an iOS 7 – 9 Notification Center Today widget.
 * **xpc_service**: a C-based [XPC](https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingXPCServices.html) service.
 
-## .nicrc
-NIC reads configuration data from `~/.nicrc`. This file uses a simple key-value format, `key = "value"`. Values must be enclosed in quotes, even if it is a number.
+## nicrc
+NIC configuration data can be stored in a config file to pre-fill values for templates. A simple key-value format is used: `key = "value"`. Values must be enclosed in quotes, even if it is a number.
+
+The first matching file is sourced:
+1. `$(XDG_CONFIG_HOME)/theos/nicrc`
+2. `$(HOME)/.config/theos/nicrc`
+3. `$(HOME)/.nicrc`
 
 ### Instance Metadata
 * **`package_prefix`** *string*. The prefix to use by default for reverse DNS package identifiers. The default is `com.yourcompany`. For example, setting `package_prefix = "ws.hbang"` and creating a new project called "Example Instance" will make the default package identifier `ws.hbang.exampleinstance`.