Sync docs after noting AppData & .tuxpaint are hidden...
...and ways to access them.
This commit is contained in:
Bill Kendrick
parent
e2f33a491b
commit
5797769eb8
31 changed files with 477 additions and 92 deletions
|
|
@ -231,7 +231,7 @@
|
|||
<p>
|
||||
Your personal Tux Paint folder is stored in your personal "Application Data". For example, on newer Windows:
|
||||
<blockquote>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code></nobr> </blockquote>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code></nobr> </blockquote>
|
||||
</p>
|
||||
</dd>
|
||||
|
||||
|
|
@ -246,7 +246,7 @@
|
|||
<dt><strong>Linux and Unix</strong></dt>
|
||||
<dd>
|
||||
<p>
|
||||
Your personal Tux Paint files go into a 'hidden directory' found in your account's home directory: <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/</code>"</nobr>. </p>
|
||||
Your personal Tux Paint files go into a 'hidden directory' found in your account's home directory: <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/</code>"</nobr>. </p>
|
||||
<p>
|
||||
Don't forget the period ("<code>.</code>") before the "<code>tuxpaint</code>"! </p>
|
||||
</dd>
|
||||
|
|
@ -256,7 +256,7 @@
|
|||
To add your own brushes, stamps, 'starters,' templates, and fonts, create subdirectories under your personal Tux Paint directory named "<code><b>brushes</b></code>", "<code><b>stamps</b></code>", "<code><b>starters</b></code>", "<code><b>templates</b></code>", "<code><b>fonts</b></code>", respectively. </p>
|
||||
|
||||
<p>
|
||||
(For example, if you created a brush named <nobr>"<code style='background: #EEE;'>flower.png</code>"</nobr>, you would put it in <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/brushes/</code>"</nobr> under Linux or Unix.) </p>
|
||||
(For example, if you created a brush named <nobr>"<code style='background: #EEE;'>flower.png</code>"</nobr>, you would put it in <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/brushes/</code>"</nobr> under Linux or Unix.) </p>
|
||||
</section><!-- H2: Personal Files -->
|
||||
</section><!-- H1: Where Files Go -->
|
||||
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
January 6, 2025 </p>
|
||||
January 9, 2025 </p>
|
||||
</center>
|
||||
|
||||
<table border="2"
|
||||
|
|
@ -363,7 +363,13 @@
|
|||
</dt>
|
||||
|
||||
<dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code>"</nobr> </dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
|
||||
<br/>
|
||||
(Note: The "<nobr><code style='background: #EEE;'>AppData</code></nobr>" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>File Explorer</cite>).) <br/>
|
||||
<br/>
|
||||
You can use the <nobr><code style='background: #EEE;'>%APPDATA%</code></nobr> variable as a shorthand, i.e. <nobr>"<code style='background: #EEE;'>%APPDATA%\Tuxpaint\Saved</code>"</nobr>. <br/>
|
||||
<br/>
|
||||
You can use the <b><code>[⊞ (Windows)]</code></b> + <b><code>[R]</code></b> key combination to bring up the <cite>Run</cite> command window, and then type the path and hit <b><code>[Enter / Return]</code></b>. </dd>
|
||||
|
||||
<dt>
|
||||
<cite>macOS</cite>
|
||||
|
|
@ -377,7 +383,11 @@
|
|||
</dt>
|
||||
|
||||
<dd>
|
||||
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code>"</nobr> </dd>
|
||||
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code>"</nobr> <br/>
|
||||
<br/>
|
||||
(Note: The ".tuxpaint" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>GNOME Files</cite> or <cite>Dolphin</cite>).) <br/>
|
||||
<br/>
|
||||
You can use the <nobr><code style='background: #EEE;'>$HOME</code></nobr> variable as a shorthand, i.e. <nobr>"<code style='background: #EEE;'>$HOME/.tuxpaint/saved</code>"</nobr>. </dd>
|
||||
|
||||
<dt>
|
||||
<cite>Haiku</cite>
|
||||
|
|
@ -537,7 +547,7 @@
|
|||
Or use Tux Paint Config. and make sure "Enable Sound Effects" (under "Video & Sound") is not checked. </li>
|
||||
|
||||
<li>
|
||||
Alternatively, recompile Tux Paint with sound support disabled. (See above, and the 'Install' documentation. </li>
|
||||
Alternatively, recompile Tux Paint with sound support disabled. (See above, and the 'Install' documentation.) </li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
|
|
@ -666,7 +676,7 @@
|
|||
If Tux Paint aborts with the message: "You're already running a copy of Tux Paint!", this means it has been launched in the last 30 seconds. (On Unix/Linux, this message would appear in a terminal console if you ran Tux Paint from a command-line. On Windows, this message would appear in a file named "<code>stdout.txt</code>" in the same folder where <code>TuxPaint.exe</code> resides (e.g., in <nobr>"<code style='background: #EEE;'>C:\Program Files\TuxPaint\</code>"</nobr>). </p>
|
||||
|
||||
<p>
|
||||
A lockfile (e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/lockfile.dat</code>"</nobr> on Linux and Unix, <nobr>"<code style='background: #EEE;'>userdata\lockfile.dat</code>"</nobr> on Windows) is used to make sure Tux Paint isn't run too many times at once (e.g., due to a child impatiently clicking its icon more than once). </p>
|
||||
A lockfile (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/lockfile.dat</code>"</nobr> on Linux and Unix, <nobr>"<code style='background: #EEE;'>userdata\lockfile.dat</code>"</nobr> on Windows) is used to make sure Tux Paint isn't run too many times at once (e.g., due to a child impatiently clicking its icon more than once). </p>
|
||||
|
||||
<p>
|
||||
Even if the lockfile exists, it contains the 'time' Tux Paint was last run. If it's been more than 30 seconds, Tux Paint should run fine, and simply update the lockfile with the current time. </p>
|
||||
|
|
@ -776,7 +786,7 @@
|
|||
|
||||
<blockquote>
|
||||
<p>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
@ -820,7 +830,7 @@
|
|||
|
||||
<blockquote>
|
||||
<p>
|
||||
<nobr><code style='background: #EEE;'>/home/username/.tuxpaintrc</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code></nobr> </p>
|
||||
</blockquote>
|
||||
|
||||
<p>
|
||||
|
|
@ -855,7 +865,7 @@
|
|||
</blockquote>
|
||||
|
||||
<p>
|
||||
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr> file: </p>
|
||||
...then you can reenable sound by either adding this option to your own <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr> file: </p>
|
||||
|
||||
<blockquote>
|
||||
<p>
|
||||
|
|
|
|||
|
|
@ -751,7 +751,7 @@
|
|||
</header>
|
||||
|
||||
<p>
|
||||
If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer, and look for a file called "<code>stderr.txt</code>" in your personal saving folder for TuxPaint which is normaly <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code>"</nobr>. </p>
|
||||
If, when you double-click on the shortcut to run Tux Paint, nothing happens, it is probably because some of these command-line options are wrong. Open an Explorer, and look for a file called "<code>stderr.txt</code>" in your personal saving folder for TuxPaint which is normaly <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code>"</nobr>. </p>
|
||||
|
||||
<p>
|
||||
It will contain a description of what was wrong. Usually it will just be due to incorrect character-case (capital 'Z' instead of lowercase 'z') or a missing (or extra) '-' (dash). </p>
|
||||
|
|
|
|||
|
|
@ -169,7 +169,7 @@
|
|||
</header>
|
||||
|
||||
<p>
|
||||
<nobr><code style='background: #EEE;'>/home/username/.tuxpaintrc</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code></nobr> </p>
|
||||
</div>
|
||||
|
||||
<section class="indent"><!-- H3: System-Wide Configuration File -->
|
||||
|
|
@ -216,7 +216,7 @@
|
|||
</header>
|
||||
|
||||
<p>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\tuxpaint.cfg</code></nobr> </p>
|
||||
|
||||
<p>
|
||||
You can use NotePad or WordPad to create this file. Be sure to save it as Plain Text, and make sure the filename doesn't have ".txt" at the end... </p>
|
||||
|
|
@ -1785,11 +1785,11 @@
|
|||
<dt>Linux / Unix</dt>
|
||||
<dd>
|
||||
Under a hidden directory in your home directory:<br/>
|
||||
<nobr><code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code></nobr> </dd>
|
||||
<nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code></nobr> </dd>
|
||||
|
||||
<dt>Windows</dt>
|
||||
<dd>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code></nobr> </dd>
|
||||
<nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code></nobr> </dd>
|
||||
|
||||
<dt>macOS</dt>
|
||||
<dd>
|
||||
|
|
@ -1823,7 +1823,7 @@
|
|||
|
||||
<ul>
|
||||
<li>Linux & Unix — If available, wherever your desktop environment is configured for pictures to be stored, based on your XDG (X Desktop Group) configuration. (Try running the command-line "<code style="white-space: nowrap;">xdg-user-dir PICTURES</code>" to find out.)<br>
|
||||
Typically (in an English locale), this will be a "<code>Pictures</code>" subdirectory in your home directory (i.e., <nobr>"<code style='background: #EEE;'>/home/username/Pictures</code>"</nobr>).<br>
|
||||
Typically (in an English locale), this will be a "<code>Pictures</code>" subdirectory in your home directory (i.e., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures</code>"</nobr>).<br>
|
||||
Tux Paint will fall back to using that typical directory, if no XDG configuration can be read, or nothing is set for "<code>XDG_PICTURES_DIR</code>". </li>
|
||||
<li>Windows - <nobr>"<code style='background: #EEE;'>My Pictures</code>"</nobr> directory for each user (normaly <nobr>"<code style='background: #EEE;'>C:\Users\username\My Pictures</code>"</nobr>)<br>You can directly open the folder as follows: <ul>
|
||||
<li>Press "[Windows]+[R]" key to open "Run ..." dialogue.</li>
|
||||
|
|
@ -1836,11 +1836,11 @@
|
|||
</ul>
|
||||
|
||||
<p class="note">
|
||||
<span title="Information">💡</span> <strong>Note:</strong> When the defaults are used, a new "<code>TuxPaint</code>" subdirectory will be created and used. (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures/TuxPaint</code>"</nobr>) When the "<code>--exportdir</code>" option is used, the exact path specified will be used (no "<code>TuxPaint</code>" subdirectory is created). </p>
|
||||
<span title="Information">💡</span> <strong>Note:</strong> When the defaults are used, a new "<code>TuxPaint</code>" subdirectory will be created and used. (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures/TuxPaint</code>"</nobr>) When the "<code>--exportdir</code>" option is used, the exact path specified will be used (no "<code>TuxPaint</code>" subdirectory is created). </p>
|
||||
<p>
|
||||
The directory itself (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures/TuxPaint</code>"</nobr>) will be created, if it doesn't exist. </p>
|
||||
The directory itself (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures/TuxPaint</code>"</nobr>) will be created, if it doesn't exist. </p>
|
||||
<p>
|
||||
If the <em>parent</em> directory (e.g., <nobr>"<code style='background: #EEE;'>/home/username/Pictures</code>"</nobr>) also does not exist, Tux Paint will attempt to create it as well (but not any directories higher than that). </p>
|
||||
If the <em>parent</em> directory (e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/Pictures</code>"</nobr>) also does not exist, Tux Paint will attempt to create it as well (but not any directories higher than that). </p>
|
||||
|
||||
<p>
|
||||
Example: <code>exportdir=/home/penguin/TuxPaintExports</code> </p>
|
||||
|
|
@ -1944,10 +1944,10 @@
|
|||
|
||||
<dl>
|
||||
<dt>Linux / Unix</dt>
|
||||
<dd><nobr><code style='background: #EEE;'>/home/username/.tuxpaint/</code></nobr></dd>
|
||||
<dd><nobr><code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/</code></nobr></dd>
|
||||
|
||||
<dt>Windows</dt>
|
||||
<dd><nobr><code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\</code></nobr></dd>
|
||||
<dd><nobr><code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\</code></nobr></dd>
|
||||
|
||||
<dt>macoS</dt>
|
||||
<dd><nobr><code style='background: #EEE;'>/Users/<i>username</i>/Library/Application Support/TuxPaint/</code></nobr></dd>
|
||||
|
|
@ -2373,7 +2373,7 @@
|
|||
</header>
|
||||
|
||||
<p>
|
||||
If any of the above options are set in a system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), you may override them in your own personal configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr>) </p>
|
||||
If any of the above options are set in a system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), you may override them in your own personal configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr>) </p>
|
||||
|
||||
<p>
|
||||
For true/false options, like "<code>noprint</code>" and "<code>grab</code>", you can simply say they equal 'no' in your personal configuration file: </p>
|
||||
|
|
@ -2550,7 +2550,7 @@
|
|||
This prevents the system-wide configuration file (e.g. <nobr>"<code style='background: #EEE;'>/etc/tuxpaint/tuxpaint.conf</code>"</nobr> on Linux), from being read. </p>
|
||||
|
||||
<p>
|
||||
Only your own configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaintrc</code>"</nobr> on Linux) — if it exists — will be used. </p>
|
||||
Only your own configuration file (e.g. <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaintrc</code>"</nobr> on Linux) — if it exists — will be used. </p>
|
||||
</dd>
|
||||
</dl>
|
||||
|
||||
|
|
|
|||
|
|
@ -102,7 +102,7 @@
|
|||
</p>
|
||||
|
||||
<p>
|
||||
January 6, 2025 </p>
|
||||
January 9, 2025 </p>
|
||||
</center>
|
||||
</header>
|
||||
<table border="2"
|
||||
|
|
@ -1706,7 +1706,13 @@
|
|||
</dt>
|
||||
|
||||
<dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\username\AppData\Roaming\TuxPaint\saved\</code>"</nobr> </dd>
|
||||
In the user's "AppData" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>C:\Users\<i>username</i>\AppData\Roaming\TuxPaint\saved\</code>"</nobr> <br/>
|
||||
<br/>
|
||||
(Note: The "<nobr><code style='background: #EEE;'>AppData</code></nobr>" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>File Explorer</cite>).) <br/>
|
||||
<br/>
|
||||
You can use the <nobr><code style='background: #EEE;'>%APPDATA%</code></nobr> variable as a shorthand, i.e. <nobr>"<code style='background: #EEE;'>%APPDATA%\Tuxpaint\Saved</code>"</nobr>. <br/>
|
||||
<br/>
|
||||
You can use the <b><code>[⊞ (Windows)]</code></b> + <b><code>[R]</code></b> key combination to bring up the <cite>Run</cite> command window, and then type the path and hit <b><code>[Enter / Return]</code></b>. </dd>
|
||||
|
||||
<dt>
|
||||
<cite>macOS</cite>
|
||||
|
|
@ -1720,7 +1726,11 @@
|
|||
</dt>
|
||||
|
||||
<dd>
|
||||
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/username/.tuxpaint/saved/</code>"</nobr> </dd>
|
||||
In the user's "home directory" folder:<br> e.g., <nobr>"<code style='background: #EEE;'>/home/<i>username</i>/.tuxpaint/saved/</code>"</nobr> <br/>
|
||||
<br/>
|
||||
(Note: The ".tuxpaint" folder is hidden (not visible) by default. You can enter the path manually in the location bar of your file browser (e.g., <cite>GNOME Files</cite> or <cite>Dolphin</cite>).) <br/>
|
||||
<br/>
|
||||
You can use the <nobr><code style='background: #EEE;'>$HOME</code></nobr> variable as a shorthand, i.e. <nobr>"<code style='background: #EEE;'>$HOME/.tuxpaint/saved</code>"</nobr>. </dd>
|
||||
|
||||
<dt>
|
||||
<cite>Haiku</cite>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue