From: Ken Manheimer <ken.manheimer@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Noam Postavsky <npostavs@gmail.com>, 36556@debbugs.gnu.org
Subject: bug#36556: 26.2; python.el pdbtracking sometimes kills buffers when it shouldn't (plus fix)
Date: Sun, 9 Aug 2020 16:21:01 -0400 [thread overview]
Message-ID: <CAAT_zTHqRZ6uWuqbejqGdJhzN9MFyJznMnKM3v3NuBnyyPKU-g@mail.gmail.com> (raw)
In-Reply-To: <87bljjboof.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 878 bytes --]
I'm sorry I didn't reply. I think Noam's analysis makes sense, and what he
suggests should be implemented. The problem is real, and should be
rectified.
Ken
On Sun, Aug 9, 2020 at 3:32 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Noam Postavsky <npostavs@gmail.com> writes:
>
> > If (or find-file-visit-truename find-file-visit-truename) is nil, then
> > find-file-noselect would really return a new buffer in that situation,
> > so it would be correct to kill it (i.e., with these settings, we are in
> > case (a)).
> >
> > Do I have a mistake in the above?
>
> This was over a year ago, and there was no response to this question, so
> I'm closing this bug report. If the problem still exists, please
> respond to this email and we'll reopen the bug report.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
>
[-- Attachment #2: Type: text/html, Size: 1404 bytes --]
next prev parent reply other threads:[~2020-08-09 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 22:28 bug#36556: 26.2; python.el pdbtracking sometimes kills buffers when it shouldn't (plus fix) Ken Manheimer
2019-07-17 15:03 ` Noam Postavsky
2019-07-17 19:31 ` Ken Manheimer
2019-07-17 23:51 ` Noam Postavsky
2020-08-09 19:32 ` Lars Ingebrigtsen
2020-08-09 20:21 ` Ken Manheimer [this message]
2020-08-10 10:41 ` Lars Ingebrigtsen
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=CAAT_zTHqRZ6uWuqbejqGdJhzN9MFyJznMnKM3v3NuBnyyPKU-g@mail.gmail.com \
--to=ken.manheimer@gmail.com \
--cc=36556@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.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 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.