Show HN: Fresh – A new terminal editor built in Rust
151–158 of 158 posts
Re: Show HN: Fresh – A new terminal editor built in Rust
#152If you are doing TUI, you can't miss Kakoune and Helix as popular editors. Add them to your comparison benchmarks.
Kakoune and helix are modal editors. They're largely based on a text selection mode (like the `v` and `V` commands in vim) with commands acting on the selected text, so they're somewhat more intuitive than vi or vim, but the notion of distinct 'modes' is still key to the workflow. Fresh is a mode-free editor; much like nano, Emacs or the new Rust-based MS Edit.
Neovim is there!
(Neo)Vim is the quintessential modal editor. If your comment is generated by an AI, please don't post comments again.
Re: Show HN: Fresh – A new terminal editor built in Rust
#153I tried it, I like it a lot, but I did find an issue straight away. I'm on MacOS and I have remapped the fn and command keys so it can be more like Windows (I can't undo 20+ years of muscle memory, and also I just don't wanna) Anyway, Fresh seems to ignore the remapping - it's back to the command key for copy/paste and the command palette. Is there a way to access the dropdown menus by keyboard? I can see F underline…
Alt+F should open the File menu. I guess that's Option+F on MacOS. Does that work?
Re: Show HN: Fresh – A new terminal editor built in Rust
#154What are Zed's numbers in the performance challenge?
no ansi color rendering
Re: Show HN: Fresh – A new terminal editor built in Rust
#155Re: Show HN: Fresh – A new terminal editor built in Rust
#156Earlier quoted context omitted.
Alt+F should open the File menu. I guess that's Option+F on MacOS. Does that work?
no
Re: Show HN: Fresh – A new terminal editor built in Rust
#157Looks like an interesting project! OP, I'm playing around with it a bit, but notice it only supports mouse input when running in terminal emulator under X, and doesn't support mouse events from GPM (in the way that mcedit does, for example).
Re: Show HN: Fresh – A new terminal editor built in Rust
#158I'm a little annoyed that for a Rust based tool the recommended installation command is to use npm. Why? Is Cargo not good enough? Cargo seems exceptionally well to me.
I took the feedback and now you can install binaries in any of these methods: - Homebrew (MacOS) - Arch Linux AUR - Debian/Ubuntu .deb - Fedora/RHEL .rpm as well as cargo install (which builds from source), npm, npx or building from source by cloning