GramEditor/gram
39
991
Fork
You've already forked gram
87

Window can't remember it's state after closing #82

Closed
opened 2026年03月10日 15:30:12 +01:00 by freetz · 9 comments

Using Manjaro, Xfce4, Gram can't restore in maximized window state

Using Manjaro, Xfce4, Gram can't restore in maximized window state
Contributor
Copy link

can't reproduce, works fine for me on gnome with wayland.

xfce is still using x11 i assume so i think this may be a x11 specific issue?

can't reproduce, works fine for me on gnome with wayland. xfce is still using x11 i assume so i think this may be a x11 specific issue?
Author
Copy link

this may be a x11 specific issue?

I'm pretty sure, but anyway X11 is still alive, so maybe anyone can do something with this?

> this may be a x11 specific issue? I'm pretty sure, but anyway X11 is still alive, so maybe anyone can do something with this?
Owner
Copy link

I’m not sure I fully understand the issue, but the first step to fixing it would be to figure out what causes the issue. Knowing that it seems to be X11-specific is valuable information, the code paths for wayland and x11 are somewhat different.

I’m not sure I fully understand the issue, but the first step to fixing it would be to figure out what causes the issue. Knowing that it seems to be X11-specific is valuable information, the code paths for wayland and x11 are somewhat different.

@aylamz wrote in #82 (comment):

can't reproduce, works fine for me on gnome with wayland.

xfce is still using x11 i assume so i think this may be a x11 specific issue?

I'm on Fedora 43 with Gnome 49.3 (Mutter/Wayland), and I can't seem to get Gram to remember the - windowed - size I've adjusted it to. Could you check if it also remembers its windowed size on your machine?

@aylamz wrote in https://codeberg.org/GramEditor/gram/issues/82#issuecomment-11698242: > can't reproduce, works fine for me on gnome with wayland. > > xfce is still using x11 i assume so i think this may be a x11 specific issue? I'm on Fedora 43 with Gnome 49.3 (Mutter/Wayland), and I can't seem to get Gram to remember the - windowed - size I've adjusted it to. Could you check if it also remembers its windowed size on your machine?
Contributor
Copy link

it does yeah

it does yeah

@aylamz wrote in #82 (comment):

it does yeah

weird, indeed.

did you change anything in Gram's settings to get it to behave that way?

NB: I don't remember this being an issue with Zed, as far as I can remember, and I don't remember changing any setting reg. window size there, but it's been a while since I had it installed.

@aylamz wrote in https://codeberg.org/GramEditor/gram/issues/82#issuecomment-12566580: > it does yeah weird, indeed. did you change anything in Gram's settings to get it to behave that way? NB: I don't remember this being an issue with Zed, as far as I can remember, and I don't remember changing any setting reg. window size there, but it's been a while since I had it installed.
Contributor
Copy link

i don't see anything obvious in my settings file that would affect this, no.

i don't see anything obvious in my settings file that would affect this, no.

@aylamz wrote in #82 (comment):

i don't see anything obvious in my settings file that would affect this, no.

fresh boot today, new empty Gram window, resized, closed, reopened - it's working today.

That's a bit weird, considering I tried the very same thing for days, if not weeks, haha.

@aylamz wrote in https://codeberg.org/GramEditor/gram/issues/82#issuecomment-12567837: > i don't see anything obvious in my settings file that would affect this, no. fresh boot today, new empty Gram window, resized, closed, reopened - it's working today. That's a bit weird, considering I tried the very same thing for days, if not weeks, haha.
Owner
Copy link

I haven't really looked into how the window state is saved or restored, but I have also noticed that it is pretty bad at restoring the state of the worktree as well - seems to open buffers almost at random. Definitely something strange going on there.

I haven't really looked into how the window state is saved or restored, but I have also noticed that it is pretty bad at restoring the state of the worktree as well - seems to open buffers almost at random. Definitely something strange going on there.
Sign in to join this conversation.
No Branch/Tag specified
main
test/wgpu-on-mac
test-ci/failing-test-mac
test/failing-test-mac
test/build-on-22-04
test/wgpu-present-mode-mailbox
v2.1
test/altgr-fix-again
test/2.0.0-rc1
test/linux-build
test/objc2
v1.2.1
3.0.1
3.0.0
2.2.0
2.1.2
2.1.1
2.1.0
2.0.0
1.2.1
1.2.0
1.1.0
1.0.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
GramEditor/gram#82
Reference in a new issue
GramEditor/gram
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?