notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

mkdir exportdir's parent, if necessary

Browse source 
Tux Paint's export features will fail if the parent
of the export directory didn't exist.  e.g., using the
default (either via XDG or hard-coded fallback) of
"~/Pictures/TuxPaint/", Tux Paint could not export if
"~/Pictures/" didn't exist yet.  It will now try to
mkdir it as well.  h/t Tim Dickson

Updated OPTIONS documents to explain this.

Also, documenting --exportdir in manpage (was missing!)
This commit is contained in:
Bill Kendrick 2021-01-13 22:48:29 -08:00
parent c2a4b9862a
commit c97932606f
9 changed files with 74 additions and 20 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/en/html/OPTIONS.html
View file

@ -25,7 +25,7 @@
</h2>
<p>
Copyright (c) 2002-2020 by various contributors; see
Copyright (c) 2002-2021 by various contributors; see
AUTHORS.txt<br>
<a href=
"http://www.tuxpaint.org/">http://www.tuxpaint.org/</a>
@ -1274,9 +1274,16 @@
and used. (e.g., "<code>~/Pictures/TuxPaint</code>")
When the "<code>--exportdir</code>" option is used, the
exact path specified will be used (no
"<code>TuxPaint</code>" subdirectory is created). It is
expected that the parent directory exists. (The
directory itself will be created, if it doesn't.)
"<code>TuxPaint</code>" subdirectory is created).
</p>
<p>
The directory itself (e.g., "<code>~/Pictures/TuxPaint</code>")
will be created, if it doesn't exist.
</p>
<p>
If the <em>parent</em> directory (e.g., "<code>~/Pictures</code>")
also does not exist, Tux&nbsp;Paint will attempt to create it
as well (but not any directories higher than that).
</p>
<p>