Linelark Notepad Studio
What shipped in 1.6.0.
Windows, the way VS Code has them
- File ▸ New Window (⇧⌘N) opens a second editor window with its own tabs, its own panes, its own folder root, and its own find state — not a second view of the same one.
- Every open window is restored on the next launch, in the order they were open, and closing a window forgets that window rather than the app’s session.
- A new window opens looking like the one you opened it from, and the menu bar always acts on the window in front.
Panels belong to the window, preferences belong to the app
- Showing the terminal, the side panel or the right dock in one window no longer shows it in every window — each window keeps its own panel layout and its own panel heights.
- Word wrap, line numbers, the theme, the fonts and the status bar remain settings for the app, because that is what they are.
The terminal panel splits
- Terminal ▸ Split Terminal (⌃⇧5), or the header’s split button, divides the panel into up to three shells side by side, the way the editor divides into panes.
- A split is a second shell on the same terminal — same file, same pin, ended by the same tab — started in the directory the one it came from is currently in, which is usually the folder you just changed to.
- Clicking a pane moves the keyboard to it, Terminal ▸ Focus Next Terminal steps round them, and each pane’s × ends that shell and closes its column. A tab switch only ever changes the pane you are working in.
Known limits
- Editing preferences — word wrap, line numbers, whitespace, the document map, the theme, the status bar — apply to every window at once by design.
- Each window loads its own copy of every plugin, so a plugin enabled in one window needs Plugins ▸ Reload Plugins in the others, and several windows cost several JavaScript heaps.
- Terminals are still not saved with the session: relaunching starts from no shells, and a split shell is not restored.
- Code folding and recorded macros remain roadmap items with no promised date.