unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, pmr@pajato.com
Subject: Re: Unmapped menus
Date: Fri, 19 Apr 2002 22:34:38 +0200 (MEST)	[thread overview]
Message-ID: <200204192034.WAA04226@pc35.bodenonline.com> (raw)
In-Reply-To: <200204152154.g3FLsPM23642@aztec.santafe.edu> from "Richard Stallman" at apr 15, 2002 03:54:25

> 
>     I think this patch only works around the bug.  The bug is that the
>     menu does not get unmapped when the main window is unmapped.
> 
> Can anyone implement unmapping of menus when the Emacs frame's window
> is unmapped?  We need to do that, and it would be much easier if
> someone who has experience with these things were to do it.

This is not a solution.  Some window managers (fvwm at least) lets you
move in short increments towards the next workspace.
If what we see is workspace 1 it kind of looks like this (M is a menu):

   ------------------------------
   | workspace1   | workspace2  |
   | ----------   |             |
   | | M      |   |             |
   | | Emacs  |   |             |
   | ----------   |             |
   ------------------------------

By using ALT-Right arrow one can move the Emacs gradually towards workspace 2

   ------------------------------
   | workspace1   | workspace2  |
   |       ----------           |
   |   M   |        |           |
   |       | Emacs  |           |
   |       ----------           |
   ------------------------------

so what you see is part of the Emacs main window, but the
menu is left behind, outside the main window.  In no situaton is the Emacs
window unmapped.  Thus, a keyboard grab to prevent this is the only solution.
It what other applications (X toolkits really) do.

	Jan D.

      reply	other threads:[~2002-04-19 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-15 21:54 Unmapped menus Richard Stallman
2002-04-19 20:34 ` Jan D. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200204192034.WAA04226@pc35.bodenonline.com \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    --cc=pmr@pajato.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).