nerd-fonts VS fish-shell

Use any nerd fonts

SourceCodePro: https://github.com/ryanoasis/nerd-fonts/tree/master/patched-fonts/SourceCodePro

Hot off the press: https://github.com/ryanoasis/nerd-fonts/releases/tag/v3.1.0

It's a bit expensive, and I can understand if someone can't or doesn't want to spend money on it. I would recommend to check out the free fonts 'JetBains Mono' & 'Hack' to these people.

Some people have already mentioned here that Berkeley Mono is not available as Nerd Font. I would like to briefly point out that Nerd Fonts provides a font patcher tool (https://github.com/ryanoasis/nerd-fonts#font-patcher).

I'm using Neovim v0.9.1 on Ubuntu 23.04 with NvChad. I've also installed the JetBrainsMono font, as NvChad requires a Nerd Font, but nothing besides that and I haven't edited any settings or nvim files and I haven't installed any additional plugins.

There are a lot of code fonts on HN today. Rather than make a new post I will talk about some of my favorite that are a little less common. None of these are free I don't think.

Cartograph CF - The one I've been using for code for years. Very readable, almost "comic mono"-like choices of some of the lower case glyphs but in a good way. All the character is in the italic which you will either love or hate.

Quadraat sans mono - The entire quadraat family is a collection of masterpieces imo, but are generally too distinctive to be appropriate for most public-facing work. But it's your computer so who cares. I use the mono sans one for my terminal. The lowercase f seems so out of place there but you learn to love it.

Alegreya sans - Not a mono font, but it almost is so if you've ever flirted with proportional fonts for code this is a fun one to try. There is a lot of careful line width variation that gives a lot of the appearance and readability advantages of serifs but keeps most of the visual coherence of sans.

I like all of these because they look feel more like normal fonts rather than code fonts. They have careful variation that adds character and improves readability for me. I've switched to an almost-no-color code theme that uses font weight instead, and the details like this become more important that way.

And then only kind of related but if you want to use unusual fonts in your terminal but you have a complex prompt setup, install font forge and learn to use something like https://github.com/ryanoasis/nerd-fonts/blob/master/font-pat... to patch in the extra characters. This can also solve your "I love this font but want a dotted zero" type problems as well. Small skill investment for a small return over a long period of time. You'll always be using fonts.

It is FiraCode Nerd Font Mono:size=16. You can find it here. On arch linux you can just install the nerd-fonts and it's included there.

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