Differences
This shows you the differences between the selected revisions of the page.
| 2009-09-03 | 2010-03-23 | ||
| bug 366 (martin) | no summary (kdpickett) | ||
| Line 16: | Line 16: | ||
| ==== [[mdi]] Problems with Some External Editors ==== | ==== [[mdi]] Problems with Some External Editors ==== | ||
| - | Some external editors can open multiple files in one process. Usually such editors have some kind of tabbed interface, but it is also case of new versions of Microsoft Word (2000 and later). | + | Some external editors can open multiple files in one process. Usually such editors have some kind of tabbed interface, but it is also the case of new versions of Microsoft Word (2000 and later). |
| - | If such an editor is already running and WinSCP runs a second instance to open new file, the second instance just notifies the first to open the new file and exits immediately. | + | If such an editor is already running and WinSCP runs a second instance to open a new file, then the second instance just notifies the first to open the new file and exits immediately. |
| - | To allow using this kind of editor, WinSCP do not treat the file as closed when the editor launched to open it is closed. | + | To allow using this kind of editor, WinSCP does not treat the file as closed when the editor launched to open it is closed. |
| - | If you choose to edit the same file again during the same session, WinSCP will download it to the same temporary directory as before, allowing the external editor to reload the file content in case it has it still opened (if the editor can detect the change). | + | If you choose to edit the same file again during the same session, WinSCP will download it to the same temporary directory as before, allowing the external editor to reload the file content in case it still has it opened (assuming the editor can detect the change). |
| - | Drawback of the approach is that all the files ever edited by the current instance of WinSCP are kept in [[temp_folder|temporary directory]] (until WinSCP is closed) and WinSCP need to watch for changes of them all. | + | One drawback of this approach is that all of the files ever edited by the current instance of WinSCP are kept in a [[temp_folder|temporary directory]] (until WinSCP is closed). WinSCP watches for changes to them all. |
| - | If you want to avoid that you need to make sure that your editor opens each file in separate window (process). Some editors do that by default, some offers a configuration option for that. Then configure your editor as an external editor for WinSCP and enable preference option //[[ui_editor_preferences#external|External editor opens each file in separate window (process)]]//. Then WinSCP will treat the file as closed when the editor launched to open it is closed. Note that setting only affects the "edit" operation. So you may want to make sure that editing is [[ui_pref_panels#double-click|default operation for double-click]]. | + | If you want to avoid that, you need to make sure that your editor opens each file in a separate window (process). Some editors do that by default while some offer a configuration option for that. If either is the case, then configure your editor as an external editor for WinSCP and enable preference option //[[ui_editor_preferences#external|External editor opens each file in separate window (process)]]//. WinSCP will then treat the file as closed when the editor launched to open it is closed. Note that this setting only affects the "edit" operation. So you may want to make sure that editing is the [[ui_pref_panels#double-click|default operation for double-click]]. |
| ===== [[binary]] Editing Binary Files ===== | ===== [[binary]] Editing Binary Files ===== | ||