all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ken Hori <fplemma@gmail.com>
To: "Emacs Dev [emacs-devel]" <emacs-devel@gnu.org>
Subject: No way to peek window configurations? Any way to restore them after restarting Emacs?
Date: Wed, 28 Apr 2010 01:48:34 -0700	[thread overview]
Message-ID: <n2jd0dc7c8f1004280148jf5fb308ch4c4884676ec1a09d@mail.gmail.com> (raw)

I was just reading the Emacs Lisp Reference Manual to see if
Emacs provided any way of restoring window configurations when
Emacs had to restart itself due to some unfortunate crash or for
whatever other reasons.

Restoring a window configuration on a live Emacs is very easy:

(setq winconf (current-window-configuration))
... do whatever you like ...
(set-window-configuration winconf)

I also understand that some information may get lost (like how to
get e.g. an eshell buffer) once Emacs is closed.

But if Emacs provided a way to access what are inside window
configurations, most stuff can be restored.

However, the manual states:
  Other primitives to look inside of window configurations would
  make sense, but are not implemented because we did not need them.

So there is currently no way to peek the contents of window configuration.

I do not know what the author of the sentence meant by "we" above
exactly, but wouldn't it be useful to be able to access winconf
contents, as it would give Emacs capabilities somewhat similar to
"workspace" in IDEs?

If we can't use window configuration, what are the alternatives
for that purpose?

Thanks.




             reply	other threads:[~2010-04-28  8:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  8:48 Ken Hori [this message]
2010-04-28  8:51 ` No way to peek window configurations? Any way to restore them after restarting Emacs? Juri Linkov
2010-04-28 11:00   ` Ken Hori

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=n2jd0dc7c8f1004280148jf5fb308ch4c4884676ec1a09d@mail.gmail.com \
    --to=fplemma@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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.