From: martin rudalics <rudalics@gmx.at>
To: chad <yandros@MIT.EDU>
Cc: 'Tassilo Horn' <tassilo@member.fsf.org>,
'Stefan Monnier' <monnier@iro.umontreal.ca>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: Usage examples of dedicated windows and popup frames?
Date: Sun, 10 Jul 2011 11:00:35 +0200 [thread overview]
Message-ID: <4E196A33.5040506@gmx.at> (raw)
In-Reply-To: <7B4A38E4-3C68-42D3-BD71-389E09EDE2A7@mit.edu>
> Do you take special steps with the Ediff frame? That's the other
> problem case I'm seeing with multiple frames and focus on
> Windows/MacOSX.
Ediff frames are hand tailored using a custom split-window-function and
other layout management techniques. Which problems do you see?
martin
next prev parent reply other threads:[~2011-07-10 9:00 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 14:19 Usage examples of dedicated windows and popup frames? Tassilo Horn
2011-07-08 14:47 ` Richard Riley
2011-07-08 14:49 ` John Yates
2011-07-08 16:11 ` Stefan Monnier
2011-07-08 16:34 ` Drew Adams
2011-07-08 16:51 ` Stefan Monnier
2011-07-08 17:38 ` Drew Adams
2011-07-08 17:54 ` Tassilo Horn
2011-07-08 18:55 ` Stefan Monnier
2011-07-09 13:00 ` martin rudalics
2011-07-09 15:03 ` Drew Adams
2011-07-10 0:43 ` chad
2011-07-10 9:00 ` martin rudalics [this message]
2011-07-10 9:43 ` Drew Adams
2011-07-12 17:47 ` chad
2011-07-12 18:55 ` Drew Adams
2011-07-13 6:24 ` martin rudalics
2011-07-13 23:09 ` chad
2011-07-10 23:45 ` undisplay temporary dialog buffers when done [was: ... dedicated windows and popup frames] Drew Adams
2011-07-09 17:22 ` Usage examples of dedicated windows and popup frames? Tassilo Horn
2011-07-10 9:00 ` martin rudalics
2011-07-10 9:39 ` Tassilo Horn
2011-07-10 15:30 ` martin rudalics
2011-07-10 16:00 ` Tassilo Horn
2011-07-10 21:13 ` Drew Adams
2011-07-08 16:11 ` Drew Adams
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=4E196A33.5040506@gmx.at \
--to=rudalics@gmx.at \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tassilo@member.fsf.org \
--cc=yandros@MIT.EDU \
/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.