Trouble using fea files to alter variable output

[yorkshirelandscape]

I see that you're working on a method of automating .fea file creation. I'm all for this, as I've tried playing around with the included fea files and applying them and have had zero success. This is a lovely font and I'll happily use it either way, but variable fonts are so neat and it would be great if I could this MM that way.

I suppose the chances of there being a variable MM-NF are pretty low, though, right?

[subframe7536]

I see that you're working on a method of automating .fea file creation. I'm all for this, as I've tried playing around with the included fea files and applying them and have had zero success. This is a lovely font and I'll happily use it either way, but variable fonts are so neat and it would be great if I could this MM that way.

TBH, I recommend not using variable font as your Editor/IDE/Terminal font for best compatibility. I am willing to provide some suggestions on fea file modification.

I suppose the changes of there being a variable MM-NF are pretty low, though, right?

It seems that the Nerd-Font patch script itself also not recommend to run with variable font, and there is no variable format in official releases, so I will follow the convention.

[yorkshirelandscape]

Thank you! That's most kind. I suppose I can see how static fonts might work better in most terminals.

I was just trying to figure out how to bake a few decisions into the variable version by default, most notably:

feature cv01;
feature cv02;
feature cv03;
feature ss08;

It didn't seem like adding those lines or playing around with the members of the letter classes was making a difference, but I may never have hit upon the right combination of edits.

[subframe7536]

You can move all the contents (sub XXX by XXX;) in these features into calt block, build, install, enable ligature (calt), then you will see the change

[yorkshirelandscape]

Ahh neat. I'll give that a try. Thanks!

[yorkshirelandscape]

That did the trick. Thanks again.