Skip to content

fix(setup): link omascribe-panel into ~/.local/bin - #16

Merged
jamespember merged 1 commit into
jamespember:mainfrom
bryangruneberg:pr/1-panel-symlink
Sep 17, 2026
Merged

jamespember merged 1 commit into
jamespember:mainfrom
bryangruneberg:pr/1-panel-symlink

Conversation

@bryangruneberg

Copy link
Copy Markdown
Contributor

The Omarchy control panel (Panel.qml) runs omascribe-panel to read the recording status and recent notes, but setup.sh only linked omascribe and omascribe-status. On a stock install the panel's Process finds no such command, so the widget never shows status or recent meetings.

The Omarchy control panel (Panel.qml) runs `omascribe-panel` to read the
recording status and recent notes, but setup.sh only linked `omascribe`
and `omascribe-status`. On a stock install the panel's Process finds no
such command, so the widget never shows status or recent meetings.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
@jamespember

Copy link
Copy Markdown
Owner

Nice catch, thanks @bryangruneberg. The Omarchy panel plugin invokes omascribe-panel as an external process, so without this symlink the widget silently no-ops on a stock install.

Confirmed:

  • omascribe-panel is declared in pyproject.toml alongside omascribe and omascribe-status (setuptools installs it into venv/bin/).
  • integrations/omarchy/omascribe-control/Panel.qml runs omascribe-panel as a Process { command: [...] }, so it needs to be on PATH.
  • Matches the pattern already used for the other two entry points on the two lines above.

Trivial change, no test warranted (it's a one-liner in setup.sh that mirrors the two lines above it). Merging.

@jamespember
jamespember merged commit 488f746 into jamespember:main Sep 17, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants