grid: decide what XTGETTCAP TN reports under the native identity #388

Closed

opened 2026-09-25 00:48:15 +09:00 by natsukium · 1 comment

natsukium commented

2026-09-25 00:48:15 +09:00

Owner

XTGETTCAP TN/name answers xterm-256color (crates/felis-grid/src/xtgettcap.rs ~50-58), while docs/reference/terminal-identity.md says felis identifies natively on every identity surface (TERM=xterm-felis, XTVERSION felis …).

Decide whether:

TN should report the stamped TERM (xterm-felis, or the FELIS_TERM hatch value), or
xterm-256color is deliberate (esctest expectations, producers that key off TN). In that case record the exception in docs/explanation/architecture/terminal-identity.md and the reference twin.

The protocol docs now list the answered subset exactly (Co/colors, TN/name, co/cols, li/lines).

XTGETTCAP `TN`/`name` answers `xterm-256color` (`crates/felis-grid/src/xtgettcap.rs` ~50-58), while `docs/reference/terminal-identity.md` says felis identifies natively on every identity surface (`TERM=xterm-felis`, XTVERSION `felis …`). Decide whether: - `TN` should report the stamped TERM (`xterm-felis`, or the `FELIS_TERM` hatch value), or - `xterm-256color` is deliberate (esctest expectations, producers that key off `TN`). In that case record the exception in `docs/explanation/architecture/terminal-identity.md` and the reference twin. The protocol docs now list the answered subset exactly (`Co`/`colors`, `TN`/`name`, `co`/`cols`, `li`/`lines`).

natsukium added the

type/design

label

2026-09-25 00:48:15 +09:00

natsukium referenced this issue

2026-09-25 00:48:41 +09:00

docs: fix inconsistencies found by a tree-wide docs and skills audit #395

natsukium referenced this issue from a commit

2026-09-25 00:54:55 +09:00

docs: fix inconsistencies found by a tree-wide docs and skills audit (#395)

natsukium commented

2026-09-25 11:45:18 +09:00

Author

Owner

Decision: TN/name reports the stamped TERM (xterm-felis, or the FELIS_TERM hatch value), consistent with felis identifying natively on every identity surface; kitty's TN likewise answers its own TERM. Update the protocol reference and check esctest expectations that key off TN.

Decision: `TN`/`name` reports the stamped TERM (`xterm-felis`, or the `FELIS_TERM` hatch value), consistent with felis identifying natively on every identity surface; kitty's `TN` likewise answers its own TERM. Update the protocol reference and check esctest expectations that key off `TN`.

natsukium referenced this issue from a pull request that will close it,

2026-09-25 12:06:37 +09:00

grid: answer XTGETTCAP TN with the TERM the session was spawned with #440

natsukium closed this issue

2026-09-25 12:30:31 +09:00

natsukium referenced this issue from a commit

2026-09-25 12:30:32 +09:00

grid: answer XTGETTCAP TN with the TERM the session was spawned with (#440)

Commenting is not possible because the repository is archived.