Reading and workspace settings

Start with the supplied scheme#

Apply the intended ePaper variant and its matching editor scheme. Check comments, ordinary text, muted metadata, and a selected line. A retained colorful custom scheme can hide the pack’s low-chroma editor treatment.

Duplicate the bundled scheme before making local changes. Keep the supplied variant available for comparison after IDE or language-plugin updates.

Adjust typography#

Set font family, size, and line spacing under Editor → Font, or use a deliberate scheme-specific override. A quiet palette can still be difficult to read at a small font size; adjust typography before changing many syntax categories at once.

Inspect code at your normal viewing distance and brightness. Light, eInk, and Sepia are different surfaces, so choose the one whose background and text remain comfortable in your actual room.

Preserve semantic colors#

When editing a copied scheme, retain distinct error, warning, selection, search-result, and diff states. Check added/removed text in a diff and modified files in the Project tree. Recoloring every state to a similar gray can remove information the Accessible variant deliberately keeps visible.

Inspect icons and panels#

The pack supplies a custom icon treatment and modern panel separation. Other icon/appearance plugins can replace those resources. Compare with one provider active if an icon differs unexpectedly.

Workspace geometry depends on the IDE’s supported UI as well as the theme. UI scale and compact-mode changes should be evaluated separately from editor text colors. Reapply the supplied theme/scheme to restore a baseline before reporting a rendering problem.