From: Juri Linkov <juri@jurta.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 9105@debbugs.gnu.org, gebser@mousecar.com
Subject: bug#9105: Feature req: Remembering emacs frames, windows, buffer position to subsequent session
Date: Mon, 18 Jul 2011 01:59:11 +0300 [thread overview]
Message-ID: <87mxgch68s.fsf@mail.jurta.org> (raw)
In-Reply-To: <4E231EFA.3000206@gmx.at> (martin rudalics's message of "Sun, 17 Jul 2011 19:42:18 +0200")
> And you have to decide what to do with windows whose buffers did not
> visit a file in the old session.
This is possible already by specifying `desktop-buffer-mode-handlers'
to reconstruct non-persistent buffers like it's done by
`Info-restore-desktop-buffer', `dired-restore-desktop-buffer', etc.
Implenting it in more packages will save and restore more different buffers.
next prev parent reply other threads:[~2011-07-17 22:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 18:47 Remember window config Bastian Ballmann
2011-07-16 19:32 ` Valentin Plechinger
2011-07-16 23:39 ` Bastian Ballmann
2011-07-17 4:02 ` ken
2011-07-17 4:25 ` masashi ito
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
2011-07-17 17:42 ` martin rudalics
2011-07-17 22:59 ` Juri Linkov [this message]
2011-07-17 15:56 ` ken
2011-07-17 22:54 ` Juri Linkov
2011-07-18 8:52 ` Jan Djärv
2011-07-18 11:26 ` ken
2011-07-17 3:47 ` Remember window config Leo
-- strict thread matches above, loose matches on Subject: below --
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mxgch68s.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9105@debbugs.gnu.org \
--cc=gebser@mousecar.com \
--cc=rudalics@gmx.at \
/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.