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

make-frame-invisible issues #21

Open
emacsomancer opened this issue Aug 17, 2020 · 1 comment
Open

make-frame-invisible issues #21

emacsomancer opened this issue Aug 17, 2020 · 1 comment

Comments

@emacsomancer
Copy link
Owner

In GitLab by @artemyurchenko on Aug 17, 2020, 03:50

There are three lines in the code:

;; double-tap, otherwise frame lands in limbo
(make-frame-invisible current-frame)
(make-frame-invisible current-frame)                 

I wonder, if setting the force parameter of make-frame-invisible would remove the need for double invocation.

Documenting to experiment later.

@emacsomancer
Copy link
Owner Author

I pretty certain that force doesn't help (though we'd have to check different Emacs versions, I imagine): it's not an issue of the frame not becoming invisible, but an issue of the visibility property not being properly set on the first invocation. That is, the problem is that the first call of (make-frame-invisible current-frame) makes the frame invisible, but doesn't mark it as invisible: i.e. frame-visible-p still reports it as being visible. The second call of (make-frame-invisible current-frame) ends up setting the property correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant