From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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 16:27:28 -0500 [thread overview]
Message-ID: <f6ljsekmnz.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <jwvzlgvf2k6.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Mon, 09 Feb 2009 21:29:42 -0500")
Stefan Monnier wrote:
>>> Changing the last argument of walk-windows in calendar-window-list
>>> from t to 0 is probably good enough.
>
>> But that breaks the behaviour if I have multiple frames open on
>> different workspaces in Window Maker.
I was wrong, it doesn't make a difference in that regard, so I can
install that.
> Not sure I understand what you mean by "different workspaces in Window
> Maker"? I'm guessing that these are different X displays, maybe of the
> form "foo:0.0" and "foo:0.1"?
No. I probably should have said "virtual desktop"? The different
screens provided by your window manager / "desktop environment", which
you can switch between and move applications between.
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?
next prev parent reply other threads:[~2009-02-10 21:27 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 [this message]
2009-02-11 1:35 ` Stefan Monnier
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
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=f6ljsekmnz.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=2199@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
--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 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).