Stream: Archive Mirror: Isabelle Users Mailing List

Topic: [isabelle] Isabelle/jEdit cannot return from fullscreen


view this post on Zulip Email Gateway (Aug 22 2022 at 10:56):

From: Ramana Kumar <rk436@cam.ac.uk>
Hi all,

I am using Isabelle2015. When I run Isabelle/jEdit, I can enter fullscreen
mode (F11). If I then try to exit fullscreen mode (press F11 again), the
entire window turns grey and I cannot see anything. (The mouse cursor would
indicate that the window is still there underneath the grey, though, since
it changes from a text cursor to a pointer cursor around where the buffer
changes to the menu.)

If I switch back to fullscreen mode, it comes back, but there is no way
back to non-fullscreen mode without restarting the prover. What could be
wrong? What can I do?

Thanks,
Ramana

view this post on Zulip Email Gateway (Aug 22 2022 at 10:56):

From: Makarius <makarius@sketis.net>
This sounds like an odd Linux/X11 window manager problem. Java/AWT makes
certain assumptions that don't hold for recent forks and variations on
window managers. Since there is so much choice of window managers on
Linux, the solution is to choose one that works: I am using Xfce4, for
example.

Makarius

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Ramana Kumar <rk436@cam.ac.uk>
Hmm... well, to be honest, I'm very happy with my window manager (apart
from this possible interaction with unrealistic assumptions in Java/AWT).

It's not yet obvious to me that the window manager is really the problem.
Does anyone have any methods by which to analyse the situation further?

[Perhaps I should just use a theorem prover IDE that works. There is choice
there too :)]

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Ramana Kumar <rk436@cam.ac.uk>
Thanks very much, Brian!

Impersonating LG3D does appear to work.

I also have set the _JAVA_AWT_WM_NONREPARENTING environment variable, but
only setting that variable didn't work.

I am surprised that just setting the environment variable didn't work,
since the version of java (1.7.0) bundled with Isabelle2015 is quite
recent. Does Isabelle's java require some special treatment of environment
variables?

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Brian Campbell <Brian.Campbell@ed.ac.uk>
Lots of Java applications suffer from these problems. I found some
workarounds at

http://awesome.naquadah.org/wiki/Problems_with_Java

Trying them on a machine with the xmonad window manager I can get the
fullscreen problem to go away with "wmname LG3D".

Brian

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Makarius <makarius@sketis.net>
This is an ancient argument of Window manager projects versus Java/AWT.
Funnily, Sun made both the X11 WM specifications and Java at about the
same time many decades ago, but it seems by different teams that did not
speak to each other. The web is full of questions and answers about that,
it is futile to repeat that here.

The official Isabelle Installation website solves the problem by this
intensional specification of Requirements for Linux:

* Window manager / Desktop environment that works with Java/AWT/Swing

Makarius

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Matthew Fernandez <matthew.fernandez@nicta.com.au>
FWIW this requirement seemed necessary but not sufficient to me in the past. Modern Isabelle works fine for me, but the first few Isabelle/jEdit releases were unusable on my then window manager (a Gnome/Xmonad hybrid), despite other Java AWT/Swing programs running fine. At the time I limped along on the slowly bitrotting Emacs setup and thankfully by the time this disappeared Makarius' improvements to the jEdit setup made it play nice with my window manager.


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

view this post on Zulip Email Gateway (Aug 22 2022 at 10:57):

From: Makarius <makarius@sketis.net>
Can you pin down anything specific that changed in the jEdit setup in this
respect? I don't think I did anything myself there, although there might
have been positive side-effects from other tuning.

I would guess it was merely Oracle ironing out some snags once again, but
they cannot fully finish that without changing something fundamental in
their X11 vs. AWT approach.

Since both X11 and AWT are legacy they might just wait until both are
phased out, although I have no idea if there is a clear vision of what
will come after it. Maybe Wayland + JavaFX?

Makarius

view this post on Zulip Email Gateway (Aug 22 2022 at 10:58):

From: Matthew Fernandez <matthew.fernandez@nicta.com.au>
On 25/08/15 19:56, Makarius wrote:

On Tue, 25 Aug 2015, Matthew Fernandez wrote:

  • Window manager / Desktop environment that works with Java/AWT/Swing

FWIW this requirement seemed necessary but not sufficient to me in the past. Modern Isabelle works fine for me, but
the first few Isabelle/jEdit releases were unusable on my then window manager (a Gnome/Xmonad hybrid), despite other
Java AWT/Swing programs running fine. At the time I limped along on the slowly bitrotting Emacs setup and thankfully
by the time this disappeared Makarius' improvements to the jEdit setup made it play nice with my window manager.

Can you pin down anything specific that changed in the jEdit setup in this respect? I don't think I did anything myself
there, although there might have been positive side-effects from other tuning.

I was never really sure. I suspect it was an upgrade of the JRE bundled with Isabelle. However, I don't know why this
helped as I tried running standalone jEdit under the same JRE at the time and it had no problems. I did not investigate
in depth at the time as I had a viable workaround (Emacs).

I would guess it was merely Oracle ironing out some snags once again, but they cannot fully finish that without changing
something fundamental in their X11 vs. AWT approach.

Since both X11 and AWT are legacy they might just wait until both are phased out, although I have no idea if there is a
clear vision of what will come after it. Maybe Wayland + JavaFX?

Makarius


The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.


Last updated: Nov 21 2024 at 12:39 UTC