Follow Cursor Jumps Without Slowing Input

Nash 0.9.1 introduces Cursor Wake, an elastic streak that helps you find the cursor after a jump. The release also fixes configuration sync so that commented-out settings remain associated with the correct TOML table.

A Trail, Not an Animated Input Position

Jumping to another part of an editor buffer can leave your eyes searching for the cursor. Cursor Wake briefly connects the old and new positions: the front catches up quickly, then the tail settles behind it.

The real cursor and its character move immediately. Typing, selection, and the position reported to programs are not delayed. The streak does not cover the live cursor or its character, and ordinary small movements are filtered so that each typed character need not produce a trail.

The effect supports block, bar, and underline cursors with both OpenGL and WebGPU. It resets when the layout changes rather than drawing a trail from stale coordinates. It does not draw while the window is unfocused, and it schedules no animation frames when at rest.

Adjust It or Turn It Off

The bundled configuration in 0.9.1 enables Cursor Wake. The examples below use 0.9.1's [cursor_wake] table. Nash 0.10.3 and newer use [cursor.wake] and ignore the old names; check your generated defaults before applying these examples to a newer build.

If you prefer less motion in 0.9.1, set this in your existing ~/.config/nash/nash.toml:

Save the file; Nash applies the change on configuration reload. Deleting the table is not a lasting way to disable it because sync can add it again.

For an enabled effect with a less opaque trail, one possible configuration is:

These are example choices, not a list of release defaults. The last setting stops trails when switching between panes or tabs while keeping trails for cursor jumps within a pane. Timing controls include fast_ms for the front and slow_ms for the tail; the tail time must be at least the front time. The Cursor Wake guide covers units, distance thresholds, and validation.

Comments Stay in Their TOML Table

Configuration sync treats a commented-out setting as an instruction not to reinsert that default. Before 0.9.1, comments at the end of a file could end up under a newly added table. A subsequent sync could then add back the original setting because its exclusion appeared to belong somewhere else.

This release keeps those comments in their original table, including nested tables and repeated syncs. If an earlier sync already left your file in that state, inspect the comment's table placement rather than assuming the missing exclusion is intentional. The Configuration Sync guide explains how commented entries and missing defaults differ.