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 }}
Repository navigation
Should remove spurious "editor state" fields in .sfd #34
@kaj-se you claim you have SaveEditorState set to off, yet ModificationTime still got updated?
This is surprising to me, because it doesn't work that way for me, and because the commit in fontforge that introduced SaveEditorState also gated ModificationTime based on it: fontforge/fontforge@68f5bb9 🤔
changed the title [-]<title describing problem. e.g. We don't have a consistent issue creation format>[/-][+]Should remove spurious "editor state" fields in .sfd[/+]on Feb 11, 2026
as described in the PR, I think we want programmatic enforcement of these changes as part of this change
And I think ensuring comments are not used is a good one as well. -- likely this is a separate issue, but the fix would likely come out of the same system that makes sure that these editor fields aren't introduced. #30 (comment)
Activity
hmdunce commentedon Feb 11, 2026
@kaj-se you claim you have SaveEditorState set to off, yet ModificationTime still got updated?
This is surprising to me, because it doesn't work that way for me, and because the commit in fontforge that introduced SaveEditorState also gated ModificationTime based on it: fontforge/fontforge@68f5bb9 🤔
[-]<title describing problem. e.g. We don't have a consistent issue creation format>[/-][+]Should remove spurious "editor state" fields in .sfd[/+]kaj-se commentedon Feb 11, 2026
@hmdunce I found the isse i looked at the wrong file. I can reproduce what you have set. If I save the the project again the
get removed
kaj-se commentedon Feb 11, 2026
Now we can do the merge ;-)
seanmakesgames commentedon Feb 17, 2026
as described in the PR, I think we want programmatic enforcement of these changes as part of this change
And I think ensuring comments are not used is a good one as well. -- likely this is a separate issue, but the fix would likely come out of the same system that makes sure that these editor fields aren't introduced.
#30 (comment)