From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: enometh@meer.net, 39977@debbugs.gnu.org
Subject: bug#39977: 28.0.50; Unhelpful stack trace
Date: Sat, 21 Mar 2020 15:15:42 +0200 [thread overview]
Message-ID: <838sjtetmp.fsf@gnu.org> (raw)
In-Reply-To: <9a3df43d-4a83-bed0-9ad1-b59cf11b4c9c@gmx.at> (message from martin rudalics on Sat, 21 Mar 2020 10:32:24 +0100)
> Cc: enometh@meer.net, 39977@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 21 Mar 2020 10:32:24 +0100
>
> >> I'm afraid that we already might mishandle some of those simple cases.
> >
> > That just makes my point stronger, doesn't it?
>
> Not really. It's easy for delete_frame to refuse deleting a frame right
> at the beginning. But once it has accepted a deletion, it might become
> hard to deal with all the consequences.
I don't think I understand where you are going with this.
> >> > The problem is how to do this without breaking legitimate code. For
> >> > example, changing the window configuration temporarily, then changing
> >> > it back is quite legitimate,
> >>
> >> Right in the middle of redisplay, while constructing the mode line or
> >> the title format?
> >
> > Why not? As long as things are back as they were by the time :eval
> > returns, I see no reason to disallow such code.
>
> Such a change in the window configuration would take place in a state
> where certain variables have temporary settings only. Selected frame,
> selected window and current buffer have been set by redisplay in a fast,
> improvised manner. I would never trust the outcome of save_window_save
> or 'set-window-configuration' in such a state.
This isn't about trust. This is about letting users' Lisp do anything
they want as long as the results allow redisplay to continue after
that Lisp returns. I don't think it's right to disallow certain
actions just because they _might_ cause problems.
> > No, they are there in cases where we simply don't know how to
> > continue.
>
> If that's the reason, then SELECTED_FRAME can easily set selected_frame
> to some live frame and continue.
Something like that, yes.
next prev parent reply other threads:[~2020-03-21 13:15 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-07 17:43 bug#39977: 28.0.50; Unhelpful stack trace Madhu
2020-03-07 18:50 ` Eli Zaretskii
2020-03-13 9:55 ` Eli Zaretskii
2020-03-13 16:28 ` martin rudalics
2020-03-13 19:43 ` Eli Zaretskii
2020-03-14 8:48 ` martin rudalics
2020-03-14 10:10 ` Eli Zaretskii
2020-03-14 10:37 ` martin rudalics
2020-03-14 18:55 ` martin rudalics
2020-03-14 20:09 ` Eli Zaretskii
2020-03-15 17:49 ` martin rudalics
2020-03-15 18:41 ` Eli Zaretskii
2020-03-16 9:24 ` martin rudalics
2020-03-16 15:33 ` Eli Zaretskii
2020-03-17 9:38 ` martin rudalics
2020-03-17 15:51 ` Eli Zaretskii
2020-03-17 17:31 ` martin rudalics
2020-03-17 17:45 ` Eli Zaretskii
2020-03-17 18:39 ` martin rudalics
2020-03-17 19:41 ` Eli Zaretskii
2020-03-18 9:12 ` martin rudalics
2020-03-18 14:53 ` Eli Zaretskii
2020-03-18 18:48 ` martin rudalics
2020-03-18 19:36 ` Eli Zaretskii
2020-03-19 8:55 ` martin rudalics
2020-03-19 14:33 ` Eli Zaretskii
2020-03-21 9:32 ` martin rudalics
2020-03-21 13:15 ` Eli Zaretskii [this message]
2020-03-22 18:20 ` martin rudalics
2020-03-23 14:48 ` Eli Zaretskii
2020-03-24 9:45 ` martin rudalics
2020-03-28 8:23 ` Eli Zaretskii
2020-03-28 18:38 ` martin rudalics
2020-04-03 16:32 ` martin rudalics
2020-04-10 11:51 ` Madhu
2020-09-30 15:06 ` Lars Ingebrigtsen
2020-09-30 15:31 ` Eli Zaretskii
2020-09-30 17:29 ` martin rudalics
2020-10-01 0:01 ` Lars Ingebrigtsen
2020-10-01 4:37 ` Madhu
2020-03-19 3:48 ` Madhu
2020-03-16 2:42 ` Madhu
2020-03-16 9:25 ` 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=838sjtetmp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39977@debbugs.gnu.org \
--cc=enometh@meer.net \
--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 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).