Multi-Tab Editing: The Productivity Boost You Didn't Know You Needed
Open your desktop right now. How many of these do you see?
- A Sticky Note with a phone number
- A TextEdit window called "Untitled 4"
- A Notepad full of half-written ideas
- Three browser tabs you keep open "just in case"
Why Single-Document Editors Fail You
Most quick-note tools open one document at a time. You make a note. You close it. You forget where you put it. Next time you need it, you make a new one. Repeat for years.
The result:
- Notes scattered across
Untitled 1.txt,Untitled 2.txt,Untitled 3.txt - Important ideas buried in random folders
- Lost work because you cleared a sticky note
- No way to compare two pieces of text side by side
How Tabs Change Your Workflow
Once you start using tabs intentionally, your editor becomes a workspace, not just a text box.
Here are a few patterns that work:
1. One Tab Per Topic
If you are working on three things at once — a project plan, a code snippet, and a meeting agenda — give each one its own tab. Switch between them instead of merging everything into one giant file.
2. A Permanent "Scratch" Tab
Keep one tab open just for throwaway thoughts. A phone number. A quote. A regex you are testing. Treat it like a digital napkin — fast in, fast out.
3. A "Today" Tab
At the start of the day, open a tab and write down what you want to get done. Close the tab when the day ends. No project management software needed.
4. Long-Lived Reference Tabs
Some tabs you never close. A list of bash aliases. A SQL query you keep tweaking. The Wi-Fi password for the office. These live as permanent tabs you can find in two seconds.
What Makes Tabs Work in EDTR
Tabs sound simple, but the details matter:
- Auto-save — every keystroke is saved to your browser's LocalStorage. Closing a tab does not lose your content unless you delete it on purpose.
- Persist across reloads — close the browser, reopen it tomorrow, your tabs are still there.
- Per-tab language — each tab can have its own syntax highlighting (SQL in one, JavaScript in another, plain text in a third).
- Per-tab filename — give your tabs real names so you can find them.
- Keyboard shortcuts —
⌥Tto open,⌥Wto close. No mouse required.
A Workflow Example
Here is a real day for a developer using EDTR with tabs:
- 9:00 AM — Open EDTR. The four tabs from yesterday are still there:
today.md,bash-aliases.sh,query-debug.sql,notes.md. - 9:15 AM — Open a new tab (
⌥T) for a code review note. Paste the snippet, set language to TypeScript. - 10:30 AM — Meeting starts. Open another tab. Title it
team-sync.md. Switch to Markdown. - 11:00 AM — Meeting ends. Close the meeting tab (
⌥W). - 2:00 PM — Customer asks for an export. Open SQL tab. Tweak the query. Copy. Done.
- 5:30 PM — Wrap up. Tabs left open:
today.mdis now full. Will start tomorrow's tab fresh.
How to Avoid Tab Overload
Tabs can become clutter if you let them. A few habits keep things sane:
- Close tabs at the end of the day that have served their purpose
- Name tabs clearly instead of leaving them as "Untitled"
- Use the sidebar (
⌘B) to see all open tabs at a glance - Pin important ones by leaving them in the same position
- Group with folders when you start managing real files via the File System Access API
Tabs vs Files vs Windows
Some people use multiple windows. Some use one giant file with ------ separators. Some use a separate file for everything.
Tabs are a middle ground that beats both:
- Faster than files — no save dialogs, no naming required up front
- More organized than one big file — no scrolling to find something
- Lighter than windows — switch with one click, no Alt-Tab gymnastics
Try It
Open edtr.plus and try this:
- Make a tab for what you are working on right now
- Make a tab for the next idea you want to remember
- Keep both open
One workspace. Many ideas. Always within reach.