v1.1.0

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

Full Changelog: v1.0.0...v1.1.0

v1.0.0 (Stable)

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

Full Changelog: v0.2.0...v1.0.0

v0.2.0

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

What's Changed

• gramit supports two modes code and grammar fix by @JoeCelaster in #4

Full Changelog: v0.1.3...v0.2.0

v0.1.3

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

Full Changelog: v0.1.2...v0.1.3

v0.1.2

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

Full Changelog: v0.1.1...v0.1.2

v0.1.0

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then gramit start, and:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

What's Changed

• Fix/vercel serverless entrypoint by @JoeCelaster in #1
• updated-code to use deployed backend server by @JoeCelaster in #2
• gramit - v0.1.0 supports cross-os by @JoeCelaster in #3

New Contributors

• @JoeCelaster made their first contribution in #1

Full Changelog: https://github.com/JoeCelaster/gramit/commits/v0.1.0

v0.1.1

Install

Windows

irm https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.ps1 | iex

macOS and Linux

curl -fsSL https://raw.githubusercontent.com/JoeCelaster/gramit/main/install.sh | sh

Then:

gramit setup      # name the backend your text is sent to
gramit start

gramit contains no backend address — you supply your own, and it is saved
only in your config. Per-OS notes:

• Linux (GNOME): gramit doctor --fix to bind Ctrl+Alt+F.
• macOS: grant Accessibility in System Settings → Privacy & Security.
  These builds are not Developer ID signed, so the grant has to be renewed
  after each upgrade.
• Windows: nothing further.

Every archive contains both gramit and gramitd; they must stay in the
same directory. Verify a download against SHA256SUMS.

Full Changelog: v0.1.0...v0.1.1