From: npostavs@users.sourceforge.net
To: Drew Adams <drew.adams@oracle.com>
Cc: 13336@debbugs.gnu.org
Subject: bug#13336: 24.3.50; `next-frame' should not choose a frame (e.g. *Backtrace*) that did not exist when it was invoked
Date: Mon, 30 Jan 2017 22:22:53 -0500 [thread overview]
Message-ID: <87h94frjzm.fsf@users.sourceforge.net> (raw)
In-Reply-To: <796316f7-38a5-4927-88df-96b8b90c3cea@default> (Drew Adams's message of "Mon, 30 Jan 2017 06:32:31 -0800 (PST)")
retitle 13336 `next-frame' should not choose the *Backtrace* frame while debugging
quit
Drew Adams <drew.adams@oracle.com> writes:
>
> At least in the case of *Backtrace*, which is perhaps a special
> case, it makes no difference whether the frame exists by the
> time `next-frame' is called. Backtrace acts specially: it does
> not take its own context into account, but instead reflects the
> state of the rest of Emacs. The debugger should not return the
> *Backtrace* frame.
Ah okay, a special case for *Backtrace* could make sense. Although I
forsee some tricky edge cases since *Backtrace* is a buffer, not a
frame.
next prev parent reply other threads:[~2017-01-31 3:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 18:13 bug#13336: 24.3.50; `next-frame' should not choose a frame (e.g. *Backtrace*) that did not exist when it was invoked Drew Adams
2017-01-30 6:33 ` npostavs
2017-01-30 14:32 ` Drew Adams
2017-01-31 3:22 ` npostavs [this message]
2021-08-23 14:37 ` bug#13336: `next-frame' should not choose the *Backtrace* frame while debugging Lars Ingebrigtsen
2021-08-23 15:20 ` bug#13336: [External] : " Drew Adams
2021-08-23 16:06 ` martin rudalics
2021-08-23 17:41 ` Drew Adams
2021-08-24 9:41 ` martin rudalics
2021-08-24 15:49 ` Drew Adams
2021-08-24 17:41 ` martin rudalics
2021-08-24 20:02 ` Drew Adams
2021-08-25 7:48 ` martin rudalics
2021-08-25 15:27 ` Drew Adams
2021-08-25 19:41 ` martin rudalics
2021-08-25 20:23 ` Drew Adams
2021-08-26 7:53 ` 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=87h94frjzm.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=13336@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).