From: martin rudalics <rudalics@gmx.at>
To: 11556-done@debbugs.gnu.org
Cc: Tobias Bading <tbading@web.de>
Subject: bug#11556: 24.0.97; Strange behaviour of bury-buffer after desktop-read
Date: Mon, 28 May 2012 12:26:26 +0200 [thread overview]
Message-ID: <4FC352D2.2090805@gmx.at> (raw)
In-Reply-To: <77DBE6D1-BF5C-4728-AC11-0B0027C98230@web.de>
> desktop.diff works fine for me, thank you.
Committed in revision 108018 of the release branch.
> What to expect from desktop-read when used in the middle of a session?
> Good question. I never use it that way, because I tend to spam my one
> and only session with lots of buffers ;-). However, other more
> organized people might use multiple desktop files. They would probably
> want desktop-read to behave as in Emacs 23, whatever that behaviour
> exactly was.
I don't use desktop but wonder what should happen when, for example, a
buffer read by `desktop-read' exists already. Should it move to the
front of the buffer lists or stay where it was before?
> The "If no desktop file is found, clear the desktop
> [...]" part in the doc-string of desktop-read sounds odd to me. Why
> would the function want to clear the desktop if it doesn't find a
> desktop file, but perform some sort of a merge operation with the
> current session (instead of a replace) if one is found?
Looks odd. Anyone who wants to clear the desktop could do this by
calling `desktop-clear'.
I'm looking for a kind soul to work on integrating window handling into
desktop.
martin
prev parent reply other threads:[~2012-05-28 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 8:50 bug#11556: 24.0.97; Strange behaviour of bury-buffer after desktop-read Tobias Bading
2012-05-27 13:20 ` martin rudalics
2012-05-27 16:16 ` Tobias Bading
2012-05-28 10:26 ` martin rudalics [this message]
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=4FC352D2.2090805@gmx.at \
--to=rudalics@gmx.at \
--cc=11556-done@debbugs.gnu.org \
--cc=tbading@web.de \
/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.