pinchord-29 Fix Tab and Enter in Javelin

Pinchord · pinchord.git · Tickets · Changelog

A Pinchord Ticket (Dismissed):

Ticket · History

• October 21, 2026 Created (title: Fix Tab and Enter in Javelin, status: open, category: triaged, type: bug)
  Changes

  @@ -0,0 +1,24 @@+---+title: Fix Tab and Enter in Javelin+status: open+category: triaged+type: bug+---++## Symptom++Javelin now uses the same format as Plover for tab and enter in the [[Pinchord Mods|mods dict]] - `\t` and `\n` in JSON form. `pinchord-mods-javelin-v30.1.json` still uses the old `\\t` and `\\n` format.++## Problem++This is a follow-up to [[pinchord@23|plover-tab-and-enter]].++In [[pinchord@23|plover-tab-and-enter]], the mods dict was split into a Plover and a Javelin version because the two engines used different formats for tab and enter. This was a bug in Javelin that has sine been fixed, so the Javelin version of Pinchord is now incorrect.++## Solution++Unify the mods dict back into one file for both engines - `pinchord-mods-v30.2.json` - that uses the `\t` and `\n` versions++## Implementation++- [ ] Remove the Javelin-specific escaping from `generate-mods.clj` and generate a single mods dict instead of 2

• October 21, 2026 Edited
  Changes

  @@ -13,7 +13,7 @@  This is a follow-up to [[pinchord@23|plover-tab-and-enter]]. -In [[pinchord@23|plover-tab-and-enter]], the mods dict was split into a Plover and a Javelin version because the two engines used different formats for tab and enter. This was a bug in Javelin that has sine been fixed, so the Javelin version of Pinchord is now incorrect.+In [[pinchord@23|plover-tab-and-enter]], the mods dict was split into a Plover and a Javelin version because the two engines used different formats for tab and enter. This was a bug in Javelin that has since been fixed, so the Javelin version of Pinchord is now incorrect.  ## Solution 

• October 21, 2026 Edited
  Changes

  @@ -17,7 +17,7 @@  ## Solution -Unify the mods dict back into one file for both engines - `pinchord-mods-v30.2.json` - that uses the `\t` and `\n` versions+Unify the mods dict back into one file for both engines - `pinchord-mods-v30.1.json` - that uses the `\t` and `\n` versions  ## Implementation 

• October 24, 2026 Edited (status: open → closed)
  Changes

  @@ -1,10 +1,12 @@ --- title: Fix Tab and Enter in Javelin-status: open+status: closed category: triaged type: bug --- +*Closed, Javelin support was dropped, but this bug was fixed before that*+ ## Symptom  Javelin now uses the same format as Plover for tab and enter in the [[Pinchord Mods|mods dict]] - `\t` and `\n` in JSON form. `pinchord-mods-javelin-v30.1.json` still uses the old `\\t` and `\\n` format.

• October 24, 2026 Rename tickets to <project>-<number> <title> (renamed from pinchord@29.md, title: Fix Tab and Enter in Javelin → none)
  Changes

  @@ -1,5 +1,4 @@ ----title: Fix Tab and Enter in Javelin status: closed category: triaged type: bug@@ -13,9 +12,9 @@  ## Problem -This is a follow-up to [[pinchord@23|plover-tab-and-enter]].+This is a follow-up to [[pinchord-23 Plover Tab and Enter]]. -In [[pinchord@23|plover-tab-and-enter]], the mods dict was split into a Plover and a Javelin version because the two engines used different formats for tab and enter. This was a bug in Javelin that has since been fixed, so the Javelin version of Pinchord is now incorrect.+In [[pinchord-23 Plover Tab and Enter]], the mods dict was split into a Plover and a Javelin version because the two engines used different formats for tab and enter. This was a bug in Javelin that has since been fixed, so the Javelin version of Pinchord is now incorrect.  ## Solution 

• October 24, 2026 Replace ticket status, category and resolution with ticket (status: closed → none, category: triaged → none)
  Changes

  @@ -1,6 +1,5 @@ ----status: closed-category: triaged+ticket: dismissed type: bug ---