View Single Post
Old 10-29-2021, 10:09 AM   #6
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 28,682
Karma: 205039118
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
Quote:
Originally Posted by Domenick View Post
and I set the MSDOS environment variable SIGIL_DEFAULT_TEMP_FOLDER to the same directory.
That step serves no purpose (though it shouldn't hurt anything). Sigil doesn't use any en var to define its scratch directory location.

<SIGIL_DEFAULT_TEMP_HOME> is just a placeholder we display in Sigil's preferences to mask the location of the default directory from neophytes. For whatever reason, people who didn't know what they were doing felt it was OK to meddle with Sigil temp files while Sigil had them locked. <SIGIL_DEFAULT_TEMP_HOME> was simply a step to discourage that a bit. It's not an environment variable.

Quote:
Originally Posted by Domenick View Post
It seems to me something must have persisted across 1.7, the uninstall, and into 1.8 because when attempting to add existing files in 1.7 and 1.8 it always came up in the previous manuscript's folder.
Like I said: it's the crash that's preventing the previous manuscript's directory from becoming the new default the next time. We have to figure out why it's crashing and the default folder thing will take care of itself.

Does the crash happen when trying to add ANY file from the location you were previously using. What I'm getting at is; have you ruled out the actual file that's being added as the problem? If other files (or other file types) load without crashing, is it possible there's something about the content of the files you're trying to add that's causing the crash, rather than their location?

Last edited by DiapDealer; 10-29-2021 at 11:28 AM.
DiapDealer is online now   Reply With Quote