Closed GoogleCodeExporter closed 9 years ago
Confirmed :( As a quick workaround, append a slash ('/') to the output path.
Original comment by Steve8x8
on 1 Jan 2014 at 10:36
I can confirm that appending a slash works. Thanks for a quick reply!
Original comment by kalvd...@gmail.com
on 1 Jan 2014 at 11:08
Thank you. This gives me some time to give the whole code section a thorough
review and overhaul: to be honest, I never liked the way filenames are
constructed very much (though automatic filenames are a nice thing to have,
with all the other options making the command-line hard to read (and keep
complete).
Obviously, one of my recent code modifications broke this somewhat fragile
thing (and while a small fix already exists on my local disk, I'd like to give
it another two thoughts at least).
I will have to run some tests in a Windows environment (assuming that MacOSX
and Linux are close enough to each other) how to identify directories, and if
necessary create them.
Undoubtedly the TUI item is named "output directory" so it should in any case,
training slash or not, be treated as such.
Stay tuned...
Original comment by Steve8x8
on 2 Jan 2014 at 7:41
Patch set committed to SVN (as r1553).
This set of patches also tries to check for directory writability, and warns if
something looks suspicious.
Please try to break it ;)
Original comment by Steve8x8
on 2 Jan 2014 at 12:27
Even after r1553, it took a number of commits to iron out the worst oversights
:(
Version 3.19.2 should be clean now.
Original comment by Steve8x8
on 6 Jan 2014 at 1:49
Original issue reported on code.google.com by
kalvd...@gmail.com
on 31 Dec 2013 at 11:32