You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2020. It is now read-only.
First of all, thank you for making Gentoo better.
So, the I noticed 2 issues
The pre-release version 1.14, which this ebuild is based have a few bugs, one of these bugs doesn't let the software initialize at all. Maybe that can have more bugs inside this pre-release version of brackets but how I couldn't even initialize I can't tell you more.
Solution: There's a new version of the software already. 1.14.1 is the version you have to look for. Bumping the version by editing the ebuild locally solved my problem
The last issue is the .desktop file that has a typo or maybe a bug but, by the way, I didn't find anything related in the issues section of brackets. So if you try to open the file using the menu of the system it simply don't open, because of this bug/typo.
Solution: Copying the file at /usr/share/applications/brackets-brackets-bin.desktop to $HOME/.local/share/applications/ and changing the sections "Exec=brackets" and "TryExec=brackets" for "Exec=/opt/brackets/Brackets" and "TryExec=/opt/brackets/Brackets" respectively solved the problem. Now the software initialize as well.
PS.: I Don't know if there are more bugs out there but these was what I found.
Sorry for not making a Pull Request, but I'm not very experienced on Gentoo and Git. So hope it helps.
Bye!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
First of all, thank you for making Gentoo better.
So, the I noticed 2 issues
PS.: I Don't know if there are more bugs out there but these was what I found.
Sorry for not making a Pull Request, but I'm not very experienced on Gentoo and Git. So hope it helps.
Bye!
The text was updated successfully, but these errors were encountered: