From: Juri Linkov <juri@jurta.org>
To: gebser@mousecar.com
Cc: 9105@debbugs.gnu.org
Subject: bug#9105: Feature req: Remembering emacs frames, windows, buffer position to subsequent session
Date: Mon, 18 Jul 2011 01:54:55 +0300 [thread overview]
Message-ID: <87oc0sk036.fsf@mail.jurta.org> (raw)
In-Reply-To: <4E226E0A.6010601@mousecar.com> (ken's message of "Sun, 17 Jul 2011 01:07:22 -0400")
> Yes, this is asking quite a bit. So I'll add one more thing. In Linux
> and other OSs employing X it's possible to have multiple viewports
> (i.e., desktops) and to place any GUI application into any viewport. So
> it's possible that all emacs windows might not be all in the same
> viewport... six emacs frames could be positioned in two, four, or more
> different viewports. Accurately positioning all of them in the correct
> viewports would constitute a thorough recreation of the previous session.
Do you know what commands can move Emacs frames to different viewports?
next prev parent reply other threads:[~2011-07-17 22:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110716204736.5d3e63ef@chaostal.de>
[not found] ` <87ei1qqawk.wl%v.plechinger@gmail.com>
[not found] ` <20110717013918.7fd31f15@chaostal.de>
2011-07-17 5:07 ` bug#9105: Feature req: Remembering emacs frames, windows, buffer position to subsequent session ken
2011-07-17 9:46 ` martin rudalics
2011-07-17 13:16 ` Drew Adams
2011-07-17 22:57 ` Juri Linkov
2011-07-17 15:56 ` ken
[not found] ` <4E230619.6090205@mousecar.com>
2011-07-17 17:42 ` martin rudalics
2011-07-17 22:59 ` Juri Linkov
2011-07-17 22:54 ` Juri Linkov [this message]
2011-07-18 8:52 ` Jan Djärv
2008-11-14 22:46 bug#1348: set-frame-width and set-frame-position seem buggy on at least MSWindows Themba Fletcher
2014-09-21 18:02 ` martin rudalics
2014-09-22 9:07 ` bug#9105: Feature req: Remembering emacs frames, windows, buffer position to subsequent session martin rudalics
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=87oc0sk036.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9105@debbugs.gnu.org \
--cc=gebser@mousecar.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).