glow VS fish-shell

To get started, install Mods and check out some of the examples below. Since Mods has built-in Markdown formatting, you may also want to grab Glow to give the output some pizzazz.

I recently started using markdown in neovim (with an LSP) along with https://github.com/charmbracelet/glow to view markdown / navigate. Does everything I used to use Obsidian for minus the links / graph functionality which I don't really need and it's pretty snappy on an old Lenovo. Very customizable as well.

Yup, those seem to be the key challenges. I've been making good progress on them, but there's plenty more work to do!

On the topic of "AI-generated PRs", I used my tool to file a PR to the `glow` CLI tool. I don't know the go language, so I had aider make the changes to glow.

https://github.com/charmbracelet/glow/pull/502

I've also been able solve a couple of github issues that were file by users by just pasting the issue into my tool... it fixed itself. Links below:

https://github.com/paul-gauthier/aider/issues/13#issuecommen...

https://github.com/paul-gauthier/aider/issues/5#issuecomment...

I'm personally also quite fond of Glow. I use it pretty much every time I touch a markdown file.

Nice idea! I’m excited to check it out. I write a lot of docs in Markdown and this could be a great way to browse them.

Out of curiosity, have you seen glow[0]?

[0] https://github.com/charmbracelet/glow

Charm's Glow is a joy to use, a good example of having the Charm's Bubbletea usage - but from the code perspective, it's a bit difficult to navigate as many code paths are put in the same package

thanks! Yeah all the markdown is handled through glow, which is one fairly awesome tool.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512