Difference between revisions of "Save/Load page"

From TED Notepad
 
(16 intermediate revisions by the same user not shown)
Line 1: Line 1:
<noinclude>{{manversion|6.1.0.2|dialog|Settings:Save/Load}}__NOTOC__</noinclude>
+
<noinclude>{{manversion|6.3.1.0|dialog|Settings:Save/Load}}__NOTOC__</noinclude>
  
 
===={{field|Settings:Save/Load|New}}====
 
===={{field|Settings:Save/Load|New}}====
  
The '''{{field|Settings:Save/Load|Template file}}''' specifies path and file to be pre-loaded as template whenever a new document is created.
+
The '''{{field|Settings:Save/Load|Template file}}''' setting specifies path and file to be pre-loaded as template whenever a new document is created.
  
 
Note: The new document is still untitled. Saving it does not mean saving into the file specified as {{field|Settings:Save/Load|Template file}}.
 
Note: The new document is still untitled. Saving it does not mean saving into the file specified as {{field|Settings:Save/Load|Template file}}.
Line 9: Line 9:
 
===={{field|Settings:Save/Load|Loading}}====
 
===={{field|Settings:Save/Load|Loading}}====
  
The '''{{field|Settings:Save/Load|File size warning}}''' tells to issue a warning whenever a file bigger than this size is being loaded, simply to prevent accidental unwanted long loading times. Use zero to issue no such warnings anytime.
+
The '''{{field|Settings:Save/Load|File size warning}}''' setting tells to issue a warning whenever a file bigger than this size is being loaded, simply to prevent accidental unwanted long loading times. Use zero here to disable such warnings altogether.
  
 
Note: This value does not limit size of files loadable in TED Notepad, merely poses a friendly loading warning and a choice to interrupt a lengthy operation.
 
Note: This value does not limit size of files loadable in TED Notepad, merely poses a friendly loading warning and a choice to interrupt a lengthy operation.
  
The '''{{field|Settings:Save/Load|Only one instance of each file}}''' specifies, whether TED Notepad should check for other instances of the same file already opened. When this option is turned on, each file is cross-checked upon opening, and if it is already opened in another window of TED Notepad, a warning is issued, asking the user, whether to switch to the already opened window.
+
The '''{{field|Settings:Save/Load|Only one instance of each file}}''' setting specifies, whether TED Notepad should check for other instances of the same file already opened. When this option is turned on, each file is cross-checked upon opening, and if it is already opened in another window of TED Notepad, a warning is issued, asking the user, whether to switch to the already opened window.
  
The '''{{field|Settings:Save/Load|Warn when file is modified from outside}}''' specifies, whether a watch is to be set for every opened file. When this option is turned on, TED Notepad raises a warning each time the currently opened file is modified by some other application. It asks, whether to {{feature|Revert}} the file upon such event.
+
The '''{{field|Settings:Save/Load|Warn when file is modified from outside}}''' setting specifies, whether a watch is to be set for every opened file. When this option is turned on, TED Notepad raises a warning each time the currently opened file is modified by some other application. It asks, whether to {{feature|Revert}} the file upon such event.
  
 
Note: By reverting, you discard all unsaved modifications and load the new version of the file. The selection and actual scrolling will try to persist the loading, locating the same line in the new version of the file.
 
Note: By reverting, you discard all unsaved modifications and load the new version of the file. The selection and actual scrolling will try to persist the loading, locating the same line in the new version of the file.
Line 21: Line 21:
 
Note: For further details on how file {{feature|Encoding}} is handled upon reverting, see {{feature|Revert}}.
 
Note: For further details on how file {{feature|Encoding}} is handled upon reverting, see {{feature|Revert}}.
  
===={{field|Settings:Save/Load|Backup}}====
+
The '''{{field|Settings:Save/Load|Revert without asking}} (remember!)''' setting can be used to automatically {{feature|Revert}} every time outsdide modifications are detected without asking the user. This can prove convenient when viewing always-changing log files, however, {{feature|Revert}} always discards any unsaved modifications and loads the new version of the file from the disk. Not asking for permission to do this can easily lead to irrecoverable loss of data. There is no {{feature|Undo}} after {{feature|Revert}}! Make sure this is acceptable. And remember enabling this!
  
The '''{{field|Settings:Save/Load|Create backup files}}''' specifies, whether to create backup files by ''copying'' the previous version of the original file upon each save operation.
+
The '''{{field|Settings:Save/Load|Warn on loading binary files}}''' setting specifies, whether user should be warned upon loading binary files. While TED Notepad is fully capable of handling binary files, it is not a hex editor and should not be used to edit binary files without great caution.
  
The '''{{field|Settings:Save/Load|Keep multiple backups}}''' specifies, whether to create and keep more than one backup file. By default, backup file name is created by appending {{string|.~}} to the original file name and older backup files are overwritten by newer ones. However, with this setting turned on, upto 10 files are gradually created by appending {{string|.~0}} to {{string|.~9}} to the original file name. After using all 10 backup file names up, the oldest backup file is always replaced upon each save, effectivelly rotating them. Please note that in this case the backup file date/time must be used to locate the latest backup, not the backup file name.
+
The '''{{field|Settings:Save/Load|Auto-detect Unicode files}}''' setting specifies, whether Unicode detection via statistical analysis should be attempted on files without a {{defined|BOM}}. This will not apply to files with an explicit {{defined|BOM}}, and will only be attempted on files which fail UTF-8 recognition first.
  
The '''{{field|Settings:Save/Load|Store backup files in Temp}}''' specifies, whether to store all backup files in the {{field|Settings:Save/Load|Temp path}} instead of using the original file path. If the original file path is used, the name of a backup file resembles nicely the original file name for user convenience. However, if backup files are stored in the {{field|Settings:Save/Load|Temp path}}, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.
+
===={{field|Settings:Save/Load|Backup}} (to {{string|.~}} files)====
 +
 
 +
The '''{{field|Settings:Save/Load|Create backup files}}''' setting specifies, whether to create backup files by ''copying'' the previous version of the original file upon each save operation.
 +
 
 +
The '''{{field|Settings:Save/Load|Keep multiple backups}}''' setting specifies, whether to create and keep more than one backup file. By default, backup file name is created by appending {{string|.~}} to the original file name and older backup files are overwritten by newer ones. However, with this setting turned on, up to 10 files are gradually created by appending {{string|.~0}} to {{string|.~9}} to the original file name. After using all 10 backup file names up, the oldest backup file is always replaced upon each save, effectivelly rotating them. Please note that in this case the backup file date/time must be used to locate the latest backup, not the backup file name.
 +
 
 +
The '''{{field|Settings:Save/Load|Store backup files in Temp}}''' setting specifies, whether to store all backup files in the {{field|Settings:Save/Load|Temp path}} instead of using the original file path. If the original file path is used, the name of a backup file resembles nicely the original file name for user convenience. However, if backup files are stored in the {{field|Settings:Save/Load|Temp path}}, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.
  
 
Note: This file name mangling in the {{field|Settings:Save/Load|Temp path}} may change in the future, but it should always be possible to manually identify and link backup files to their originals, even after such changes.
 
Note: This file name mangling in the {{field|Settings:Save/Load|Temp path}} may change in the future, but it should always be possible to manually identify and link backup files to their originals, even after such changes.
  
The '''{{field|Settings:Save/Load|Use hidden backup files}}''' specifies, whether to create backup files with hidden file attribute. Hidden files usually do not get in the way, since they are not shown by file explorers, but can still be found and used if necessary.
+
The '''{{field|Settings:Save/Load|Use hidden backup files}}''' setting specifies, whether to create backup files with hidden file attribute. Hidden files usually do not get in the way, since they are not shown by file explorers, but can still be found and used if necessary.
  
 
Note: Backup files are never created as hidden if stored in the {{field|Settings:Save/Load|Temp path}}. It is expected that the {{field|Settings:Save/Load|Temp path}} is not going to ''get in the way'' itself.
 
Note: Backup files are never created as hidden if stored in the {{field|Settings:Save/Load|Temp path}}. It is expected that the {{field|Settings:Save/Load|Temp path}} is not going to ''get in the way'' itself.
  
===={{field|Settings:Save/Load|Auto-save}}====
+
The '''{{field|Settings:Save/Load|Delete backup file after save}}''' setting specifies, whether to delete the backup file after a successful save operation. With this setting turned on, backup files can be used to guard against disk failures without annoyingly lying around all over the place afterwards.
  
The '''{{field|Settings:Save/Load|Save recovery file every 5 mins}}''' specifies, whether to auto-save currently opened file every 5 minutes into a recovery file. The recovery file name is created by appending {{string|.$}} to the original file name. The auto-save operation is performed on background and occurs only, if there are unsaved modifications made to the document.
+
{{tip}} In combination with the {{field|Settings:Save/Load|Flush file buffers after save}} setting, one can remain confident that either the old version of the file is still present on the disk, or the new one has been fully written to the disk (presuming Windows duly flushes all written data when instructed).
 +
 
 +
===={{field|Settings:Save/Load|Auto-save}} (to {{string|.$}} files)====
 +
 
 +
The '''{{field|Settings:Save/Load|Save recovery file}}''' setting specifies, whether to periodically auto-save currently opened file into a recovery file. The recovery file name is created by appending {{string|.$}} to the original file name. The auto-save operation is performed on background and occurs only, if there are unsaved modifications made to the document. The given number is the period for auto-saving in seconds, with a default of 300 seconds (i.e. 5 minutes) between each auto-save.
  
 
Note: Recovery files are automatically deleted after successful {{feature|Save}} operation; or upon closing the document by user request (e.g. by opening a new file or closing the editor window). However, in case of power loss or system crash, recovery files are kept. Upon loading documents, TED Notepad automatically searches for presence of recovery files and notifies the user whenever a bereaved recovery file is found. See {{feature|Recovering auto-save files}} in chapter [[Recovering auto-save files]] for further details.
 
Note: Recovery files are automatically deleted after successful {{feature|Save}} operation; or upon closing the document by user request (e.g. by opening a new file or closing the editor window). However, in case of power loss or system crash, recovery files are kept. Upon loading documents, TED Notepad automatically searches for presence of recovery files and notifies the user whenever a bereaved recovery file is found. See {{feature|Recovering auto-save files}} in chapter [[Recovering auto-save files]] for further details.
  
The '''{{field|Settings:Save/Load|Save directly to original}}''' allows to skip recovery files and auto-save directly to the original file. This type of auto-save operation is performed on background as well and occurs only, if there are unsaved modifications made to the document.
+
The '''{{field|Settings:Save/Load|Save directly to original}}''' setting allows to skip recovery files and auto-save directly to the original file. This type of auto-save operation is performed on background as well and occurs only, if there are unsaved modifications made to the document.  
  
Note: Auto-saving like this does not resemble the manual {{feature|Save}} command in all manners. For example no backup file is created even if {{field|Settings:Save/Load|Create backup files}} setting is turned on. {{feature|Undo}} and {{feature|Redo}} queues are not reduced by an auto-save operation even if {{field|Settings:Edit|Reduce Undo/Redo upon Save}} setting is turned on. Also the usual warnings, messages and questions typical for resolving saving troubles might not be shown as otherwise expected. Upon any saving errors, messages or questions, the auto-save is simply interupted and the error message is only posted on the {{feature|Status Bar}}.
+
Note: Auto-saving like this does not resemble the manual {{feature|Save}} command in all manners. For example no backup file is created even if the {{field|Settings:Save/Load|Create backup files}} setting is turned on. {{feature|Undo}} and {{feature|Redo}} queues are not reduced by an auto-save operation even if the {{field|Settings:Edit|Reduce Undo/Redo upon Save}} setting is turned on. The document is not marked as saved and still says that there are {{feature|unsaved modifications}}.
  
The '''{{field|Settings:Save/Load|Store recovery files in Temp}}''' specifies, whether to store all recovery files in the {{field|Settings:Save/Load|Temp path}} instead of using the original file path. If the original file path is used, the name of a recovery file resembles nicely the original file name for user convenience. However, if recovery files are stored in the {{field|Settings:Save/Load|Temp path}}, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.
+
{{important}} Usual warnings, messages and questions typical for resolving saving troubles are not shown during auto-saving (as otherwise expected). Upon any errors, messages, dilemmas or questions, the auto-save process is simply interrupted. An information message might be posted on the {{feature|Status Bar}}, but not necessarily in all cases. From this point of view, saving directly to original is not very recommended and should only be used by users that fully understand the potential for inadvertent loss of data.
 +
 
 +
The '''{{field|Settings:Save/Load|Store recovery files in Temp}}''' setting specifies, whether to store all recovery files in the {{field|Settings:Save/Load|Temp path}} instead of using the original file path. If the original file path is used, the name of a recovery file resembles nicely the original file name for user convenience. However, if recovery files are stored in the {{field|Settings:Save/Load|Temp path}}, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.
  
 
Note: This file name mangling in the {{field|Settings:Save/Load|Temp path}} may change in the future, but it should always be possible to manually identify and link recovery files to their originals, even after such changes.
 
Note: This file name mangling in the {{field|Settings:Save/Load|Temp path}} may change in the future, but it should always be possible to manually identify and link recovery files to their originals, even after such changes.
  
The '''{{field|Settings:Save/Load|Use hidden recovery file}}''' specifies to set ''hidden'' attribute to all created recovery files. Since TED Notepad searches for presence of recovery files automatically upon loading documents, loss of information due to hidden recovery files is rather small.
+
The '''{{field|Settings:Save/Load|Use hidden recovery file}}''' setting specifies to set ''hidden'' attribute to all created recovery files. Since TED Notepad searches for presence of recovery files automatically upon loading documents, loss of information due to hidden recovery files is rather small.
  
 
Note: Recovery files are never created as hidden if stored in the {{field|Settings:Save/Load|Temp path}}.
 
Note: Recovery files are never created as hidden if stored in the {{field|Settings:Save/Load|Temp path}}.
  
The '''{{field|Settings:Save/Load|Save Untitled documents }}''' specifies, whether to auto-save new documents as well. A new document does not have a file yet, and TED Notepad does not know yet, whether and where the file would eventually be saved. Such new documents are thus always auto-saved into the {{field|Settings:Save/Load|Temp path}} and must be recovered manually after a crash or power loss. Names of the auto-saved untitled documents try to resemble the opening lines of those documents.
+
The '''{{field|Settings:Save/Load|Save Untitled documents }}''' setting specifies, whether to auto-save new documents as well. A new document does not have a file yet, and TED Notepad does not know yet, whether and where the file would eventually be saved. Such new documents are thus always auto-saved into the {{field|Settings:Save/Load|Temp path}} and must be recovered manually after a crash or power loss. Names of the auto-saved untitled documents try to resemble the opening lines of those documents.
  
 
{{tip}} If you experience a power loss and need to recover a lost Untitled document, open this page of the {{dialog|Settings}} dialog. Use the {{button|Settings:Save/Load|Explore}} button next to the {{field|Settings:Save/Load|Temp path}} to open the temp path, where the recovery file can be easily found.
 
{{tip}} If you experience a power loss and need to recover a lost Untitled document, open this page of the {{dialog|Settings}} dialog. Use the {{button|Settings:Save/Load|Explore}} button next to the {{field|Settings:Save/Load|Temp path}} to open the temp path, where the recovery file can be easily found.
Line 59: Line 71:
 
===={{field|Settings:Save/Load|Saving}}====
 
===={{field|Settings:Save/Load|Saving}}====
  
The '''{{field|Settings:Save/Load|Force Read-only files}}''' specifies, whether files with read-only attribute can be forcibly written to. By using this option, TED Notepad overrides default system behaviour, which prevents modification of such files.
+
The '''{{field|Settings:Save/Load|Force Read-only files}}''' setting specifies, whether files with read-only attribute can be forcibly written to. By using this option, TED Notepad overrides default system behaviour, which prevents modification of such files.
  
 
{{tip}} You can save into read-only file by opening its {{feature|Properties}} dialog (hotkey {{hotkey|Ctrl+F9}}) and unchecking the read-only attribute. After saving, you may then choose whether to set the read-only attribute back.
 
{{tip}} You can save into read-only file by opening its {{feature|Properties}} dialog (hotkey {{hotkey|Ctrl+F9}}) and unchecking the read-only attribute. After saving, you may then choose whether to set the read-only attribute back.
  
The '''{{field|Settings:Save/Load|No mixed newlines}}''' prevents from saving files with mixed newlines. The user is forced to some specific type of {{feature|Newlines}} at all times, and this type is then used upon saving to convert all encountered newlines. See {{feature|Newlines}} for further details.
+
The '''{{field|Settings:Save/Load|No mixed newlines}}''' setting prevents from saving files with mixed newlines. The user is forced to some specific type of {{feature|Newlines}} at all times, and this type is then used upon saving to convert all encountered newlines. See {{feature|Newlines}} for further details.
 +
 
 +
Note: After turning the {{field|Settings:Save/Load|No mixed newlines}} setting on, if the current document has {{field|Newlines|Mixed}} newlines selected for the {{feature|Newlines}} option, the {{field|Settings:File|Default newlines}} setting from the [[File page]] of the {{dialog|Settings}} dialog is used to choose new {{feature|Newlines}} option for the document.
 +
 
 +
The '''{{field|Settings:Save/Load|Flush file buffers after save}}''' setting specifies, whether to instruct Windows to flush written data to the disk.
 +
 
 +
Note: Explicitly flushing data to the disk may decrease the disk performance, but it can help ensuring that the data really gets written to the disk as soon as possible, thus avoiding potential loss of the data due to power failures while the data is being handled in the buffers.
 +
 
 +
{{tip}} See the {{field|Settings:Save/Load|Create backup files}} and {{field|Settings:Save/Load|Delete backup file after save}} settings to prevent potential loss of the data even further.
 +
 
 +
The '''{{field|Settings:Save/Load|Use memory-optimized saving}}''' setting specifies, whether to use file streaming routines when saving big files.
 +
 
 +
Note: File streaming routines are capable of saving much bigger files, but may be slower on some network drives, or drives that require specific buffering modes. Use this setting to troubleshoot slow file saving.
  
 
===={{field|Settings:Save/Load|Temp path}}====
 
===={{field|Settings:Save/Load|Temp path}}====
  
The '''{{field|Settings:Save/Load|Temp path}}''' specifies relative or absolute path, where to store temporary files.
+
The '''{{field|Settings:Save/Load|Temp path}}''' setting specifies relative or absolute path, where to store temporary files.
 
* If no path is specified, the default current user temp folder is used; e.g. {{system|C:\Documents and Settings\User\Local Settings\Temp\TedNPad}}.
 
* If no path is specified, the default current user temp folder is used; e.g. {{system|C:\Documents and Settings\User\Local Settings\Temp\TedNPad}}.
 
* If absolute path is specified, it is used unmodified. Note: No sub-directories are created and filename conflicts may potentially arise.
 
* If absolute path is specified, it is used unmodified. Note: No sub-directories are created and filename conflicts may potentially arise.
* If relative path is specified (e.g. {{string|.}} or {{string|\docs}}), it refers to current working directory. Note: The current working directory is usually the directory which TED Notepad was started from; although shortcuts allow to specify another starting directory for example. The current working directory stays the same throughout the entire instance session.
+
* If relative path is specified (e.g. {{string|.\temp}} or {{string|\docs}}), it refers to current working directory. Note: The current working directory is usually the directory which TED Notepad was started from; although shortcuts allow to specify another starting directory for example. The current working directory stays the same throughout the entire instance session.
  
 
{{tip}} A useful example for ''secure'' portable usage is a relative path starting with a back-slash (e.g. {{string|\temp\TedNPad}}), which makes all temporary files always to be stored on the same drive, from which you originally launched the application. This can be used to twist the USB drive around, while moving TED Notepad on the USB drive from one computer to another. Make the {{string|\temp}} folder hidden to get it out of the way.
 
{{tip}} A useful example for ''secure'' portable usage is a relative path starting with a back-slash (e.g. {{string|\temp\TedNPad}}), which makes all temporary files always to be stored on the same drive, from which you originally launched the application. This can be used to twist the USB drive around, while moving TED Notepad on the USB drive from one computer to another. Make the {{string|\temp}} folder hidden to get it out of the way.
 +
 +
{{tip}} If the path specified does not exist, it is automatically created. This can be very useful, but also potentially annoying, if relative path like {{string|.\temp}} is specified, since {{string|temp}} folders might start to appear all over the place.
  
 
Note: One of the requirements for this to work, is to use correct working directory upon launching TED Notepad from the USB drive. In most typical cases, the system uses the USB drive as the working directory (as expected). However, some file managers and portable launchers may need to be told what working directory to use explicitly. Set them to use the USB drive.
 
Note: One of the requirements for this to work, is to use correct working directory upon launching TED Notepad from the USB drive. In most typical cases, the system uses the USB drive as the working directory (as expected). However, some file managers and portable launchers may need to be told what working directory to use explicitly. Set them to use the USB drive.

Latest revision as of 23:22, 30 November 2021

This section is up to date for TED Notepad version 6.3.1.0.
Control page Control:dialog:Settings:Save/Load

New

The Template file setting specifies path and file to be pre-loaded as template whenever a new document is created.

Note: The new document is still untitled. Saving it does not mean saving into the file specified as Template file.

Loading

The File size warning setting tells to issue a warning whenever a file bigger than this size is being loaded, simply to prevent accidental unwanted long loading times. Use zero here to disable such warnings altogether.

Note: This value does not limit size of files loadable in TED Notepad, merely poses a friendly loading warning and a choice to interrupt a lengthy operation.

The Only one instance of each file setting specifies, whether TED Notepad should check for other instances of the same file already opened. When this option is turned on, each file is cross-checked upon opening, and if it is already opened in another window of TED Notepad, a warning is issued, asking the user, whether to switch to the already opened window.

The Warn when file is modified from outside setting specifies, whether a watch is to be set for every opened file. When this option is turned on, TED Notepad raises a warning each time the currently opened file is modified by some other application. It asks, whether to Revert the file upon such event.

Note: By reverting, you discard all unsaved modifications and load the new version of the file. The selection and actual scrolling will try to persist the loading, locating the same line in the new version of the file.

Note: For further details on how file Encoding is handled upon reverting, see Revert.

The Revert without asking (remember!) setting can be used to automatically Revert every time outsdide modifications are detected without asking the user. This can prove convenient when viewing always-changing log files, however, Revert always discards any unsaved modifications and loads the new version of the file from the disk. Not asking for permission to do this can easily lead to irrecoverable loss of data. There is no Undo after Revert! Make sure this is acceptable. And remember enabling this!

The Warn on loading binary files setting specifies, whether user should be warned upon loading binary files. While TED Notepad is fully capable of handling binary files, it is not a hex editor and should not be used to edit binary files without great caution.

The Auto-detect Unicode files setting specifies, whether Unicode detection via statistical analysis should be attempted on files without a BOM. This will not apply to files with an explicit BOM, and will only be attempted on files which fail UTF-8 recognition first.

Backup (to .~ files)

The Create backup files setting specifies, whether to create backup files by copying the previous version of the original file upon each save operation.

The Keep multiple backups setting specifies, whether to create and keep more than one backup file. By default, backup file name is created by appending .~ to the original file name and older backup files are overwritten by newer ones. However, with this setting turned on, up to 10 files are gradually created by appending .~0 to .~9 to the original file name. After using all 10 backup file names up, the oldest backup file is always replaced upon each save, effectivelly rotating them. Please note that in this case the backup file date/time must be used to locate the latest backup, not the backup file name.

The Store backup files in Temp setting specifies, whether to store all backup files in the Temp path instead of using the original file path. If the original file path is used, the name of a backup file resembles nicely the original file name for user convenience. However, if backup files are stored in the Temp path, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.

Note: This file name mangling in the Temp path may change in the future, but it should always be possible to manually identify and link backup files to their originals, even after such changes.

The Use hidden backup files setting specifies, whether to create backup files with hidden file attribute. Hidden files usually do not get in the way, since they are not shown by file explorers, but can still be found and used if necessary.

Note: Backup files are never created as hidden if stored in the Temp path. It is expected that the Temp path is not going to get in the way itself.

The Delete backup file after save setting specifies, whether to delete the backup file after a successful save operation. With this setting turned on, backup files can be used to guard against disk failures without annoyingly lying around all over the place afterwards.

Tip: In combination with the Flush file buffers after save setting, one can remain confident that either the old version of the file is still present on the disk, or the new one has been fully written to the disk (presuming Windows duly flushes all written data when instructed).

Auto-save (to .$ files)

The Save recovery file setting specifies, whether to periodically auto-save currently opened file into a recovery file. The recovery file name is created by appending .$ to the original file name. The auto-save operation is performed on background and occurs only, if there are unsaved modifications made to the document. The given number is the period for auto-saving in seconds, with a default of 300 seconds (i.e. 5 minutes) between each auto-save.

Note: Recovery files are automatically deleted after successful Save operation; or upon closing the document by user request (e.g. by opening a new file or closing the editor window). However, in case of power loss or system crash, recovery files are kept. Upon loading documents, TED Notepad automatically searches for presence of recovery files and notifies the user whenever a bereaved recovery file is found. See Recovering auto-save files in chapter Recovering auto-save files for further details.

The Save directly to original setting allows to skip recovery files and auto-save directly to the original file. This type of auto-save operation is performed on background as well and occurs only, if there are unsaved modifications made to the document.

Note: Auto-saving like this does not resemble the manual Save command in all manners. For example no backup file is created even if the Create backup files setting is turned on. Undo and Redo queues are not reduced by an auto-save operation even if the Reduce Undo/Redo upon Save setting is turned on. The document is not marked as saved and still says that there are unsaved modifications.

Important: Usual warnings, messages and questions typical for resolving saving troubles are not shown during auto-saving (as otherwise expected). Upon any errors, messages, dilemmas or questions, the auto-save process is simply interrupted. An information message might be posted on the Status Bar, but not necessarily in all cases. From this point of view, saving directly to original is not very recommended and should only be used by users that fully understand the potential for inadvertent loss of data.

The Store recovery files in Temp setting specifies, whether to store all recovery files in the Temp path instead of using the original file path. If the original file path is used, the name of a recovery file resembles nicely the original file name for user convenience. However, if recovery files are stored in the Temp path, file names are somewhat mangled to prevent potential collisions between different original paths but same original file names.

Note: This file name mangling in the Temp path may change in the future, but it should always be possible to manually identify and link recovery files to their originals, even after such changes.

The Use hidden recovery file setting specifies to set hidden attribute to all created recovery files. Since TED Notepad searches for presence of recovery files automatically upon loading documents, loss of information due to hidden recovery files is rather small.

Note: Recovery files are never created as hidden if stored in the Temp path.

The Save Untitled documents setting specifies, whether to auto-save new documents as well. A new document does not have a file yet, and TED Notepad does not know yet, whether and where the file would eventually be saved. Such new documents are thus always auto-saved into the Temp path and must be recovered manually after a crash or power loss. Names of the auto-saved untitled documents try to resemble the opening lines of those documents.

Tip: If you experience a power loss and need to recover a lost Untitled document, open this page of the Settings dialog. Use the Explore button next to the Temp path to open the temp path, where the recovery file can be easily found.

Saving

The Force Read-only files setting specifies, whether files with read-only attribute can be forcibly written to. By using this option, TED Notepad overrides default system behaviour, which prevents modification of such files.

Tip: You can save into read-only file by opening its Properties dialog (hotkey Ctrl+F9) and unchecking the read-only attribute. After saving, you may then choose whether to set the read-only attribute back.

The No mixed newlines setting prevents from saving files with mixed newlines. The user is forced to some specific type of Newlines at all times, and this type is then used upon saving to convert all encountered newlines. See Newlines for further details.

Note: After turning the No mixed newlines setting on, if the current document has Mixed newlines selected for the Newlines option, the Default newlines setting from the File page of the Settings dialog is used to choose new Newlines option for the document.

The Flush file buffers after save setting specifies, whether to instruct Windows to flush written data to the disk.

Note: Explicitly flushing data to the disk may decrease the disk performance, but it can help ensuring that the data really gets written to the disk as soon as possible, thus avoiding potential loss of the data due to power failures while the data is being handled in the buffers.

Tip: See the Create backup files and Delete backup file after save settings to prevent potential loss of the data even further.

The Use memory-optimized saving setting specifies, whether to use file streaming routines when saving big files.

Note: File streaming routines are capable of saving much bigger files, but may be slower on some network drives, or drives that require specific buffering modes. Use this setting to troubleshoot slow file saving.

Temp path

The Temp path setting specifies relative or absolute path, where to store temporary files.

  • If no path is specified, the default current user temp folder is used; e.g. C:\Documents and Settings\User\Local Settings\Temp\TedNPad.
  • If absolute path is specified, it is used unmodified. Note: No sub-directories are created and filename conflicts may potentially arise.
  • If relative path is specified (e.g. .\temp or \docs), it refers to current working directory. Note: The current working directory is usually the directory which TED Notepad was started from; although shortcuts allow to specify another starting directory for example. The current working directory stays the same throughout the entire instance session.

Tip: A useful example for secure portable usage is a relative path starting with a back-slash (e.g. \temp\TedNPad), which makes all temporary files always to be stored on the same drive, from which you originally launched the application. This can be used to twist the USB drive around, while moving TED Notepad on the USB drive from one computer to another. Make the \temp folder hidden to get it out of the way.

Tip: If the path specified does not exist, it is automatically created. This can be very useful, but also potentially annoying, if relative path like .\temp is specified, since temp folders might start to appear all over the place.

Note: One of the requirements for this to work, is to use correct working directory upon launching TED Notepad from the USB drive. In most typical cases, the system uses the USB drive as the working directory (as expected). However, some file managers and portable launchers may need to be told what working directory to use explicitly. Set them to use the USB drive.