Notepad++ style unsaved document autosave and restore
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
Research direction
Start by reviewing related issues #428, #607, and #226, then inspect xed's existing session and plugin behavior. Clarify how temporary autosaves, close-time saves, and restoration should interact, including whether restoration covers all opened documents. Done means the three listed behaviors work reliably without prompting for unsaved documents.
Written by the indexing model from the issue text.
Description
This feature request entails the following behaviors:
- Periodically, auto-save unsaved documents to a temp directory
- Auto-save unsaved documents when the app would normally close, such that it closes without needing to ask the user to save
- Restore all opened documents, temp or otherwise, on reopening the application
This is based on how the popular software Notepad++ works on Windows.
It is a very effective pattern that surprisingly doesn't exist yet for xed despite its semi-advanced capabilities.
Similar issues:
#428, #607 (scoped to only disaster recovery)
Issue #226 is about restoring the session on app start, not explicitly for unsaved documents. It mentions a plugin everyone is praising that might be doing that as well.
It's also an issue from eight years ago, and Linux Mint is attracting some of the crowd from Windows, most who are not as technical. So they'll find it unhelpful when eventually they lose data by needing to close things, or forgetting how important something is when they go to close it, because they're unaware that xed has a plugin system or unaware of its plugins. It's a very core feature, I think, better fitting to be part of the app than outside it.
I am an outsider spurred by wanting something. For those who do work on xed, what do you think?
- Dominant language
- C
- Stars
- 551
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxmint/xed
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Allow pkexec xed OpenFEATURE REQUEST
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·