-
Notifications
You must be signed in to change notification settings - Fork 0
IPEP 18: Text Editor for the Notebook
| Status | Deferred |
| Author | Min RK <[email protected]> |
| Created | July 2013 |
| Updated | July 2013 |
| Discussion | |
| Implementation |
The Notebook interface was never designed to function as a text editor. That said, Notebook users do need to edit text files, and will often try to subvert the interface to do so.
The proposed solution is to allow the Notebook to open a text editor in a new tab.
The user would have a magic, say 'edit', which would take a path to the file they wanted to hack on, so running %edit script.py would open the editor in a new tab, with script.py open. Each time the magic was called, a new instance of the editor would be created in a new browser tab.
Each editor instance will display the file name in the browser tab using the <title> element, and display the state of the editor (think saved/unsaved changes) by updating the favicon. This allows the browser's native tabs to be used to manage multiple instances of the editor (and Notebook).
The editor will support Save and Save-As operations, but not Open or New, which will be features of the Notebook's new magic. Not sure about Run??
Actually implementing an editor should be pretty straight forwards, so why hasn't it been done?
- While ACE and CodeMirror seem to be the only real choices regarding which editor to use, we still need to pick one of them.
- The Web API still needs specifying.
- The extension to the Notebook interface needs to be discussed. For starters, should
%%editopen the cell in the editor? Should the magic be called edit at all?