From: Stefan Kangas <stefan@marxist.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15016-done@debbugs.gnu.org
Subject: bug#15016: 24.3.50; return of #8789: touch border of *Backtrace* frame > it disappears (exits)
Date: Wed, 15 Jan 2020 06:36:31 +0100 [thread overview]
Message-ID: <87zhepe0ww.fsf@marxist.se> (raw)
In-Reply-To: <874l0k7fe8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 07 Oct 2019 17:18:39 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Drew Adams <drew.adams@oracle.com> writes:
>
>> I am now seeing again the behavior I reported in the middle of the
>> discussion of bug #8789, which I thought had been fixed:
>>
>> When I touch mouse-1 to the *Backtrace* frame border, to try to widen
>> the frame (because the debugger frame now insists upon reinitializing
>> itself instead of remembering the last width I dragged it to...), the
>> frame immediately disappears and the debugger is exited.
>>
>> Quite frustrating to use...
>>
>> Again, the context is using `debug-on-entry' for a function that is
>> invoked when the minibuffer is active - for example, a function used to
>> sort candidates in *Completions*.
>
> Do you have a recipe to reproduce this bug from "emacs -Q"? You're
> mentioning the "*Backtrace* frame", which is unusual, so I'm guessing
> you have some customisations to pop up a frame that has the backtrace
> buffer?
More information was requested, but none was given within 14 weeks, so
I'm closing this bug. If this is still an issue, please reply to this
email (use "Reply to all" in your email client) and we can reopen the
bug report.
Best regards,
Stefan Kangas
prev parent reply other threads:[~2020-01-15 5:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-03 15:56 bug#15016: 24.3.50; return of #8789: touch border of *Backtrace* frame > it disappears (exits) Drew Adams
2019-10-07 15:18 ` Lars Ingebrigtsen
2020-01-15 5:36 ` Stefan Kangas [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
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=87zhepe0ww.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=15016-done@debbugs.gnu.org \
--cc=larsi@gnus.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).