-
Notifications
You must be signed in to change notification settings - Fork 830
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
was the folder symlink icon removed for a reason? #945
Comments
The codepoints were assigned by Nerd Fonts. But anyhow, there have been more icons dropped, see the Nerd Fonts packaging logfile (but the be honest Nerd Fonts came from an ancient Octicons version):
Maybe I missed some renaming of the |
Created a icon that mixes Left to right: I could PR that icon, if Octicons is interested. Edit:
Ok, no problem. |
Hey all, thanks for the comments! We'll take a look at this issue at an upcoming Octicons working session. |
I would also like to highlight a related bug on the GitHub UI: https://github.com/silverwind/symlink-test ![]() A symlink to a file should use ![]() The directory symlink visible above should ideally use a new dedicated icon as mentioned, so it's distinguishable from git submodules which use So in total, there should be 5 octicons:
|
Hi everyone, thanks for the discussion here! The internal Octicons team has taken a look at the options and what was discussed here, and I think we will be shipping a |
Make use of the [new octicon](primer/octicons#945) that indicates a symlink to a directory: <img width="189" alt="Screenshot 2023-06-22 at 22 50 57" src="https://github.com/go-gitea/gitea/assets/115237/a70690ea-ebfc-48fe-af23-cdc33bcb2098">
Discovered this after updating my system nerdfont package. Nerdfonts recently released version 3.0.0, which now depends on octicons 18.3.
This may be an issue for nerdfont, or perhaps even the lsd command which I'm using that generates the nerdfont codepoints. I thought I would start here to see if maybe this was removed by mistake.
Before:
After:
The text was updated successfully, but these errors were encountered: