Skip to content
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

Some editors can't find agave #8

Closed
aasutossh opened this issue Jul 27, 2019 · 11 comments
Closed

Some editors can't find agave #8

aasutossh opened this issue Jul 27, 2019 · 11 comments
Labels

Comments

@aasutossh
Copy link

Hi, as you already know, agave is the one. So I am trying to use it with a bunch of editors.

Android Studio doesn't find agave, same with Python IDLE.

But others, like gVim, PyCharm, IDEA, Sublime Text, VS Code can locate the font.

Are those specific software problems or font issues?

@blobject
Copy link
Owner

blobject commented Jul 29, 2019

Hey there. Thank you for opening this issue. I will have to take a look at what's going on here. I'll also treat this issue in conjunction with #7, as a single item. (ie. a similar problem occurs with VS Community.)

@aasutossh
Copy link
Author

Yeah but those editors don't even list the font.

@blobject
Copy link
Owner

I see. I will see if I can reproduce and fix this.

@aasutossh
Copy link
Author

I see. I will see if I can reproduce and fix this.

Let me know if I can be of any help.

@iozsaygi
Copy link

@drdonkey Visual Studio Community lists the font but it does not apply the font to the editor when i choose Agave. It activates some different font instead. (Courier New for example)

@aasutossh
Copy link
Author

@iozsaygi yeah, I noticed it too on VS Code Insiders.

@aasutossh
Copy link
Author

I got the beta version of Android studio and amazingly it is able to find agave.
Finally, I am complete.

@iozsaygi
Copy link

iozsaygi commented Aug 7, 2019

Congrats! Hope VS will be able to find it too. (At some point)

@aasutossh
Copy link
Author

aasutossh commented Aug 7, 2019

Congrats! Hope VS will be able to find it too. (At some point)

Yeah. People should try beta or dev builds to see if it works for them or not.
For the sake of completeness of this issue I am closing this one.

@blobject
Copy link
Owner

blobject commented Aug 8, 2019

Great to hear! I'll try to find a fix for the other editors - hopefully within this weekend. Thanks for the testing and feedback @iozsaygi @drdonkey

@blobject
Copy link
Owner

blobject commented Aug 27, 2019

I understand this issue is closed, and do apologise for the late follow-up, but just wanted to leave a comment saying that I was unable to reproduce the issue.

I am running a recent & near-vanilla instance of Archlinux + KDE (ie. anything font-rendering-related was untouched after the installation of the default xorg and plasma-desktop packages). I installed agave manually, then opened IDLE and Android-Studio, and found that both applications were successfully locating and applying the font.

NOTE: the font name "agave" is all-lowercase, so IDLE, for example, had "agave" near the bottom of its font listing due to its ordering Capital names first. I hope that was not the cause of this issue.

Some screenshots:

agave installed by placing agave-r.ttf in a manually created ~/.fonts folder:

image

Python's IDLE 3.7.3:

image

Android-Studio stable 3.5.0.21 (https://aur.archlinux.org/packages/android-studio/):

image

I have not tested the other well-behaving editors mentioned in the opening comment, but did try some other apps already locally installed, including Emacs, GIMP, Inkscape, and Termite. They all had no trouble showing agave.

In case you'd like me to look into this issue more, I would appreciate some more information on what desktop environment was used (if any), what the procedure was for installing agave, and pertinent software versions (editors, fontconfig, DE). Otherwise, I will leave this issue as-is and focus on what the deal is with Visual Studio over in Wimdows land. Thanks!

@blobject blobject added the bug label Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants