Name change of "x.semi-chancery-{straight|curly}" to "x.semi-chancery-{straight|curly}-serifless" not yet implemented in website customizer about iosevka HOT 8 CLOSED

It's correct on my end:

Try refreshing the page.

from iosevka.

Ok, but just changing that in my toml (which should essentially be the same action, since I created the toml with the customizer a few hours ago, anyway) does not fix the issue. It is still looking for "semi-chancery-curly" somewhere, and I cant' find it.
I found semiChanceryCurlySerifless in the x.mjs (.\Iosevka\packages\font-glyphs\src\letter\latin), so ..

Occurances:

• In the .\Iosevka\params\variants.toml were three semiChanceryCurly under the entry 4100: [prime.x.variants-buildup.stages.body.semi-chancery-curly-serifless]
• I found semiChanceryCurlySerifless in the x.mjs (.\Iosevka\packages\font-glyphs\src\letter\latin)
• semiChanceryCurlySerifless in C:\Users\Distelzombie\Iosevka\packages\font-glyphs\src\letter\latin\x.ptl

still no idea where the error is. NPM is still looking for semi-chancery-curly, even after changing all of them to serifless

from iosevka.

• In the .\Iosevka\params\variants.toml were three semiChanceryCurly under the entry 4100: [prime.x.variants-buildup.stages.body.semi-chancery-curly-serifless]

This does not match the variants.toml file found in main. Have you been editing that instead of creating a private-build-plans.toml file?

from iosevka.

By the way I tested it using my private-build-plans.toml and it compiles for me just fine:

from iosevka.

What... that works aswell on my end. Seems like something else is werid. Maybe somewhere there is a copy or configuration saved of my non-working toml and it wont update if the new one has the same name??

x = "semi-chancery-curly" is the only row that changed, why wouldn't it work then AFTER adding "serifless"

idk

from iosevka.

What... that works aswell on my end. Seems like something else is werid. Maybe somewhere there is a copy or configuration saved of my non-working toml and it wont update if the new one has the same name??

x = "semi-chancery-curly" is the only row that changed, why wouldn't it work then AFTER adding "serifless"

idk

I wouldn't recommend editing the variants.toml file for basic user configuration.
The reason it seems to "magically" add the -serifless at the end is because of an extra step in the variant buildup tree that you're trying to add back yourself.

Simply leaving the variants.toml file alone (i.e. the same as it is in the main branch in the repo) and doing all your configuration in private-build-plans.toml makes everything work correctly.

from iosevka.

Yes, I found out that it was not the culprit and that it worked default..

I fixed it, though: After pasting the contents of this repository over everything again, my toml, where I added "serifless", is now also working. So there must have been some configuration/copy of my toml saved from the time when there was no "serifless" in it, and the builder used that one. Maybe look into that. :)

Anyway, I just had very bad timing. I created toml while the website was still old version, but the github download was newer. Or I took too long while making it and missed the update - keeping my local copy of the customizer old.

Well, thanks :)

from iosevka.

Anyway, I just had very bad timing. I created toml while the website was still old version, but the github download was newer. Or I took too long while making it and missed the update - keeping my local copy of the customizer old.

It usually takes an hour (± a few minutes) for the release binaries to be uploaded to the actual releases tab after be5invis merges the original release commit into main, and then two or three minutes after that for the site to be updated. If you ever see that the version numbers in the release tab and the main repo don't match, then just wait a bit.

As for the discontinuity between your local files and the repo itself, that might be a cache issue, but don't quote me on that.

from iosevka.