141–150 of 223 posts
Really nice design. I like CLI and TUI, they can be both practical and aesthetically pleasing, in my opinion the "beauty" of tools is something that can improve the quality of life for the end-user. But I have a few negative remarks. - The glow.exe app on Windows is 19M, the launch is fast and I love that it is self contained and portable, but I think that even a pretty markdown viewer could be compiled to a much sma…
I personally believe we really should graduate from the terminal infrastructure that was designed in the ancient time. We can make a good use of stuffs like client-side UI rendering (fast & reactive), graphical boxes (more compact boxes), image embedding, native multiplexing, capability negotiation, etc. These might be still possible on the existing infrastructure, but a clean slate should provide more consistent experience for everyone involved.
Earlier quoted context omitted.
You can configure kitty to open the entire scrollback buffer in an editor or a pager(less/nvim etc). https://github.com/kovidgoyal/kitty/issues/719
I wish there was something that have stdout in an env variable that is readily usable next time the prompt is available.
I love the general renaissance of terminal UI tools we are seeing in the last few years. I can't quite put my finger on what I like about it so much. Something to do with the simplicity and directness of these UIs, guaranteed optimised for efficient keyboard nav, widespread adoption of vim-like navigation keys, and the fact that they link directly with my terminal shell so I can stay entirely in a stream of thought w…
Earlier quoted context omitted.
What about 'glow' and 'glamour' components of the charm project? What is their difference from what you propose? Aside: I use glow to display help for special keybindings mode on sway.
Those are cool but they are still using just ANSI color codes and what not. I think it is great but not ideal or optimized than if terminals would implement a native markdown or markup renderer.
Is this like, a framework for making command line apps, the way Spring is a framework for making web apps? Is Soft Serve for people who don't want to use GitHub?
> Is Soft Serve for people who don't want to use GitHub? There's no web UI for soft serve, it's strictly a command line and config driven git repo manager. It's more of a direct comparison to look at gitolite (also a script/CLI driven repo manager). If you're looking for a run your own web UI for git, check out gitea.