Sloppie's own icon images are broken if you run from source since they're loaded from the icon theme. That works after installation.
Fonts and editor are pretty much about this part of the README:
> Sloppie is hard-coded to its author's preferences and not generic or configurable. If you like the concept and want to use Sloppie, instead of installing and using it directly, you'd likely want to clone the repository, ask a coding agent to customize the font, colors, editor etc. to your preferences and use that clone instead.
The UI fonts should have fallbacks, but the terminal doesn't.
Regarding the editor, note that it's also launched with line or line + column arguments and against the directory if no file selected — all of which work in Emacs, but not in all editors.
Give it a try! The main mechanics is coding agent + git, which should just work.
I've noticed that images and fonts are broken and that it assumes emacs editor instead of using $EDITOR.
I like the general idea and simplicity of it though. I'll try to run a task or two through it.
Sloppie's own icon images are broken if you run from source since they're loaded from the icon theme. That works after installation.
Fonts and editor are pretty much about this part of the README:
> Sloppie is hard-coded to its author's preferences and not generic or configurable. If you like the concept and want to use Sloppie, instead of installing and using it directly, you'd likely want to clone the repository, ask a coding agent to customize the font, colors, editor etc. to your preferences and use that clone instead.
The UI fonts should have fallbacks, but the terminal doesn't.
Regarding the editor, note that it's also launched with line or line + column arguments and against the directory if no file selected — all of which work in Emacs, but not in all editors.
Give it a try! The main mechanics is coding agent + git, which should just work.
[flagged]
[dead]