Reduce complexity in output?

[eugenesvk]

Reduce complexity in output?

[eugenesvk]

I've customized your script for my own purposes to follow this logic (prioritizing 'Devicons' over 'SetiUI', moving 'SetiUI' right after 'Devicons') and only retaining 'FA' glyphs that don't conflict with 'Octicons' (haven't tested yet moving the displaced glyphs elsewhere).

Now that I've thought of additional simplification (with only two fonts required) the patcher could have those two additional aggregate options for producing SourceFontNFA prioritizing 'FA' and SourceFontNO prioritizing 'Octicons'.

If you're interested in such a simplification, I'd be happy to do a PR with the script and help with fixing the names for couple of fonts that I use myself.

[ryanoasis]

I really appreciate your ideas here and they make a lot of sense. 🙇

These are suggestions I will definitely and probably need to consider, especially the 'windows version' possibly just trimming the names no matter what. Especially if that actually makes things less confusing to someone coming to download the fonts.

With short names (e.g. "NC" instead of "Nerd Font Complete") Windows version is never needed.

Yeah correct. This might be the way to go. Have to think about this and perhaps get some more opinions (if possible) 😄

For the 1st there is no variation, 'SetUI' takes precedence.

Sorry didn't quite understand what you meant here. It seems like later you contradicted by saying you prefered 'Devicons' to take priority over 'Seti-UI' or maybe I misunderstood.

Personally, I'd prefer in the 1st conflict to prioritize 'Devicons'

Yeah that makes sense. Originally when this font started it was just 'Seti-UI' and those were moved for some reason that I currently do not remember (I will have to check). But yes when 'devicons' was added the conflict was apparent only then.

Really the only problem with moving 'Seti-ui' is that it would break vim-devicons which relies upon the specific codepoints for glyphs and was the catalyst of this project even existing 😛. However there is a good target opportunity to move around glyph positions for version 1.0.0 of vim-devicons is released (following semver) because there are going to be breaking changes already planned for 😄

Anyway, yes these are all possible at some point 👍

[eugenesvk]

You're right, I do prefer 'Devicons' to take precedence. I was just assuming that this choice, once made, is constant and doesn't offer variations. Only in this sense there is no variation.
But technically you're correct, you could offer two variations instead of one — with Devicons as prio and SetiUI as prio.
In light of the fact that codepoints will be broken in vim-devicions anyway, I'd just suggest you respect the glyphs that actually make part of the project name :) and leave Devicons at default codepoints, shifting SetiUI and still having only one font as output.
If that were not feasible, then yes, two fonts would be a better alternative and that would increase the total complexity to four variations:

1. Devicons + FA prio
2. Devicons + Octicons prio
3. SetiUI + FA prio
4. SetiUI + Octicons prio

P.S.
Btw, I've noticed that your custom SetiUI glyphs are bigger than the default ones. How did you do that?

[ryanoasis]

@eugenesvk Yeah I think this should be feasible and done at the 1.0.0 release since it will be a breaking change for both projects.

A few other interesting motivator to decrease the number of Fonts:

• Cloning and downloading the Repo is not feasible for everyone: #73
• May be coming up on a GitHub repo size limit: https://help.github.com/articles/what-is-my-disk-quota/

[ryanoasis]

going to close this as we will be changing the mappings for the next major version. thanks

[github-actions]

This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a new issue, complete the issue template with all the details necessary to reproduce, and mention this issue as reference.