Debug -> Reload Without Extensions?A custom font set in View->Themes is ignored.
Fira Code, FiraCode, 'SourceCodePro-Medium', ï¼ï¼³ ゴシック, 'MS Gothic', monospaceExpected behavior:
Custom font should be displayed in the editor.
Actual behavior:
Custom font is set, but only once, after committing the setting. After zooming in/out, after a restart, or a reload, the default font is displayed again.
Brackets 1.9
Windows 10
This is a regression from 1.8, where setting a custom font worked just fine.
‘I’ve been through the same situation!
same situation... tried changing the defaultPreferneces.json.... Still no luck...
I'm seeing this also. Windows 7 and Windows 10.
This issue is already posted here,
https://github.com/adobe/brackets/issues/13205
Its not working even in Ubuntu (in my case Ubuntu 16.04 LTS x64)
That appears to be a different issue, as it also reports the problem in 1.8.
This particular case is a regression from 1.8, meaning the feature worked fine in 1.8, but it broke as of 1.9.
I have modified the brackets.min.css.
Can this please be fixed with a maintenance update?
It happens too often that we need to wait 3 months or longer, for an issue to get solved in the next release. And any new release may introduce other breaking bugs, causing us to have to wait even longer.
Can this please be fixed with a maintenance update?
I +1 this comment. Its such annoying bug..
+1
@thany We are working on this issue and hopefully have a fix by next week. Once the fix is in, we will trigger a pre-release which would be available under Brackets GitHub releases.
I have this bug too.
When I change the font in preferences, the font changes. But after restarting brackets it shows with default font.
Closing this as fixed by #13279 and available as part of 1.10 pre-release 1 build https://github.com/adobe/brackets/releases/tag/release-1.10-prerelease-1
I just noticed 1.9 is still up as the latest release, even though this bug is still in there, supposedly. Why aren't you releasing this 1.10-prerelease as a maintenance update to 1.9? You can call it 1.9.1 or something.
Most helpful comment
Can this please be fixed with a maintenance update?
It happens too often that we need to wait 3 months or longer, for an issue to get solved in the next release. And any new release may introduce other breaking bugs, causing us to have to wait even longer.