Coming from quill

Newen was called quill until 0.1.9. Updating a quill 0.1.9 to Newen is an ordinary update; on its first start, Newen moves quill’s things to their new names by itself. There is nothing to do.

What moves

In this order, each step safe to repeat:

1. Folders. quill’s data and settings folders become Newen’s (~/.local/share/quill → ~/.local/share/newen, and the same for ~/.config). On Linux and macOS a quill link is left pointing at the new folder.
2. Saved paths. Pictures and release notes the database points at are pointed at the new folder.
3. Launcher. On Linux, a quill.desktop made by quill’s installer becomes newen.desktop. A launcher you wrote yourself is left alone.
4. Skills Newen generated for each session are removed; they are made again as needed.
5. The database, last: quill.db becomes newen.db.

Then Newen writes a marker, .migrated-from-quill, and does not try again.

When it waits

• It runs only if quill was really there (its quill.db), not because some other app has a folder named quill.
• If quill is still open, Newen leaves everything as it is and tries again at its next start.
• If a step fails, quill’s names stay in use and it tries again at the next start. Each step writes a line to updates.log: migrate: data folder: done, or not done and why.

What keeps working

• QUILL_* environment variables you set in a launcher are still read when the NEWEN_* one is not set. Rename them when you can: a later release will stop reading them, and its notes will say so.
• Secrets in the keychain under quill are copied to newen the first time they are needed.
• Sites you allowed for the agent’s browser in quill stay allowed, and an editor setting of quill-ide means newen-ide.
• quill’s start-at-login entry is replaced by Newen’s when you turn Open at login on or off.
• newen-ide moves its own folders (quill-ide → newen-ide) the same way when it starts.

Note

On Linux and macOS, if an update ever rolls back past 0.2.0, quill 0.1.9 starts again through the quill link, with your data.