Version 0.12.0 of package Gnosis has just been released in GNU ELPA. You can now find it in M-x list-packages RET.
Gnosis describes itself as: ================ Knowledge System ================ More at https://elpa.gnu.org/nongnu/gnosis.html ## Summary: 1 Gnosis ════════ Gnosis is a personal knowledge management and spaced repetition system for Emacs. It integrates two complementary subsystems in a single package: a Zettelkasten-style note system called *nodes*, and a flashcard-based self-testing system built around *themata*. Both subsystems share a single SQLite database, and their contents are linked together so that flashcard questions can refer directly to the notes they are drawn from. 1.1 Why Gnosis ────────────── Most spaced repetition tools treat flashcards as isolated units. You create a card, review it, and the system schedules the next review. The cards have no relationship to each other or to anything outside the review loop. Most note-taking tools do the opposite: they help you build a web of ## Recent NEWS: 2026/09/15 2026/09/14 ⁃ [Homepage] ⁃ [Upstream] ⁃ [Changelog] [Homepage] <https://thanosapollo.org/projects/gnosis/> [Upstream] <https://git.thanosapollo.org/gnosis/> [Changelog] <https://thanosapollo.org/log/gnosis/> 1 0.12.0 ════════ 1.1 Upgrading ───────────── ⁃ Upgrade released schema 9 to schema 10 to retain practice encounter evidence. Released 0.10.6 databases still upgrade through schema 9. Existing content, schedules and study history are preserved; missing historical answers are not invented. ⁃ Back up before the first database open with this version. Downgrading to 0.11.0 requires its matching pre-upgrade database backup, not a schema-10 database. 1.2 Fixes ───────── ⁃ Populate dashboard statistics on first startup without requiring a previous review session to load their implementation. ⁃ Refuse native thema saves that would discard explanation headings or prose outside fields. Preserve the complete draft and source links, including when the editor is narrowed. ⁃ Preserve file-level Org IDs and adjacent source/example blocks when inserting the first file tag. ⁃ Retire study collection and dashboard ownership when their buffers become files. Refresh and retained commands cannot erase successor drafts or reuse retired selections after detachment. ⁃ Keep dashboard study actions and pending-review Delete, Suspend and Flag actions bound to the database and presentation that produced them, including across prompts. 1.3 Practice and journals ───────────────────────── ⁃ Retain accepted practice answers and context, support an explicit unlimited-attempt policy, and recover current practice sessions without changing scheduled-review evidence or FSRS state. ⁃ Add optional journal templates and free-form capture through `gnosis-journal-insert-template' and `gnosis-journal-capture'. Thoughts can be edited before saving; cancellation leaves the journal unchanged. ⁃ Route journal captures through explicit local heading roles and reject ambiguous destinations rather than choosing an unrelated heading. ⁃ Improve the bundled demo collection and remove stale ELPA ignore entries. 2 0.11.0 ════════ 2.1 Breaking changes and upgrading ────────────────────────────────── ⁃ Replace the previous scheduling algorithm with FSRS-6. Remove the legacy algorithm and per-tag scheduling customization. Desired retention is now a versioned, database-wide setting. Remove `gnosis-custom-values' and `gnosis-history-clear'; activity is derived from retained evidence rather than a separately editable daily log. ⁃ The supported database upgrade is from released 0.10.6 (schema 8) directly to schema 9. Preserve existing due dates and review totals without inventing individual review events or historical FSRS state. Older schemas, separate org-gnosis databases and private development layouts require matching older source or a separately verified conversion. ⁃ Back up before opening an existing database with 0.11.0. `gnosis-backup-db' copies the existing database without upgrading it; follow the manual's pre-first-open procedure and keep the matching old source for rollback. Back up Org files and external media separately. ⁃ Journal entries now default to one `journal.org', or `journal.org.gpg' when `gnosis-journal-as-gpg' is enabled. Set `gnosis-journal-file' to `nil' to retain one file per entry. Existing files are not converted. ⁃ Saving a journal no longer completes tasks in other Org files. Use `gnosis-journal-insert-task' and `gnosis-journal-complete-task' for explicit, confirmed completion through source ID links. 2.2 Scheduling and review ───────────────────────── ⁃ Use FSRS-6 with binary Again/Good outcomes and an initial desired retention of 90%. `gnosis-scheduler-set-retention' changes the target for future accepted reviews without rewriting existing due dates. ⁃ Retain scheduled review events and their configuration for replay. `gnosis-study-history-audit' distinguishes migrated totals, scheduled recall, same-day activity, practice exposures and voided grades. ⁃ Bound failure relearning: a failed thema returns once at the end of … …
