From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: Stephen Berman <stephen.berman@gmx.net>, 2199@emacsbugs.donarmstrong.com
Subject: bug#2199: 23.0.60; calendar marks and font-lock-mode
Date: Tue, 10 Feb 2009 20:35:19 -0500 [thread overview]
Message-ID: <jwvfxilg3o5.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <f6ljsekmnz.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 10 Feb 2009 16:27:28 -0500")
> I noticed that frames on workspaces other than the current one have a
> 'visibility frame-parameter of 'icon, which surprised me. Does that
> make sense?
Yes. X11 doesn't have a notion of "workspace", fundamentally, so
window-managers simulate it by mapping/unmapping (the X11 terms for
display/hide) the windows according to which windows are displayed in
the current workspace.
Now mapping/unmapping is the same mechanism used to iconify/deiconify
a window, so Emacs treats an unmapped window as "iconified".
Note that window-managers could use other techniques to
hide/show windows. E.g. they could just move them "out of sight", in
which case Emacs would consider those windows as still "visible" but
with bogus left/right positions.
Stefan
next prev parent reply other threads:[~2009-02-11 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <qlwsbxy65i.fsf@fencepost.gnu.org>
2009-02-04 17:03 ` bug#2199: 23.0.60; calendar marks and font-lock-mode Stephen Berman
2009-02-05 9:49 ` Stephen Berman
2009-02-08 1:58 ` Glenn Morris
2009-02-08 2:10 ` Processed: " Emacs bug Tracking System
2009-02-08 20:44 ` Glenn Morris
2009-02-09 15:04 ` Stephen Berman
2009-02-09 20:04 ` Glenn Morris
2009-02-09 20:14 ` Glenn Morris
2009-02-10 2:29 ` Stefan Monnier
2009-02-10 21:27 ` Glenn Morris
2009-02-11 1:35 ` Stefan Monnier [this message]
2009-02-11 4:10 ` bug#2199: marked as done (23.0.60; calendar marks and font-lock-mode) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvfxilg3o5.fsf-monnier+emacsbugreports@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=2199@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.org \
--cc=stephen.berman@gmx.net \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.