From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9419@debbugs.gnu.org
Subject: bug#9419: 24.0.50; C-x k deletes the entire frame instead of switching to another buffer
Date: Tue, 06 Sep 2011 09:17:04 -0400 [thread overview]
Message-ID: <jwvd3fdx1ei.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83k49oz2z7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 04 Sep 2011 19:28:28 +0300")
>> > On second though, if we are trying to fix the specific use case of
>> > save-window-excursion, why not solve it on the level of
>> > save-window-excursion?
I think we first need to decide what use case we want to fix:
- the use of save-window-excursion is normally for "I want to run this
code which fiddles with the windows, but I don't want it to fiddle
with the windows". I.e. unless the code really only fiddles with
windows and never with frames it is actually a bug since you can't
fully undo frame operations (they're visible to the user before we
get to try and undo them).
- the use of "get current-window-configuration, store it in a global var,
give the hand back to the user, at some later time, call
set-window-configuration". This is not a good solution since it
assumes that the user works in a strict nesting way, whereas in
practice (and with frames even more so), the user may interleave two
or more activities, so the set-window-configuration may end up
deleting/resetting windows in undesired ways.
So the problem is really not in how those primitives are implemented,
but in the functionality offered by those primitives.
Stefan
next prev parent reply other threads:[~2011-09-06 13:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 17:46 bug#9419: 24.0.50; C-x k deletes the entire frame instead of switching to another buffer Eli Zaretskii
2011-09-03 11:01 ` martin rudalics
2011-09-03 11:53 ` Eli Zaretskii
2011-09-03 13:54 ` martin rudalics
2011-09-03 14:20 ` Eli Zaretskii
2011-09-03 17:29 ` martin rudalics
2011-09-03 17:44 ` Eli Zaretskii
2011-09-03 19:27 ` Eli Zaretskii
2011-09-04 10:34 ` martin rudalics
2011-09-04 16:28 ` Eli Zaretskii
2011-09-06 13:17 ` Stefan Monnier [this message]
2011-09-08 7:02 ` martin rudalics
2011-09-06 13:06 ` Stefan Monnier
2011-09-08 7:02 ` martin rudalics
2011-09-08 7:02 ` martin rudalics
2011-09-09 9:16 ` Eli Zaretskii
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=jwvd3fdx1ei.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9419@debbugs.gnu.org \
--cc=eliz@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 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).