From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: martin rudalics <rudalics@gmx.at>
Cc: tromey@redhat.com, Eli Zaretskii <eliz@gnu.org>,
dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: threads and kill-buffer
Date: Thu, 06 Sep 2012 17:28:12 -0400 [thread overview]
Message-ID: <jwvk3w6265x.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <5048DF46.9000003@gmx.at> (martin rudalics's message of "Thu, 06 Sep 2012 19:37:10 +0200")
>> Why? When you killed the first *Backtrace* buffer, it lost its name, so
>> when B pops a new backtrace, it creates a new *Backtrace* buffer.
> And if, at the time it gets killed, *Backtrace* appears in a window
> managed by thread A what do I see after it has been killed?
Some other buffer: a window cannot display a killed buffer.
Stefan
next prev parent reply other threads:[~2012-09-06 21:28 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 20:36 threads and kill-buffer Tom Tromey
2012-09-04 20:43 ` Lars Ingebrigtsen
2012-09-04 21:03 ` Paul Eggert
2012-09-05 2:53 ` Eli Zaretskii
2012-09-05 14:20 ` Sam Steingold
2012-09-05 16:35 ` Eli Zaretskii
2012-09-05 16:50 ` Sam Steingold
2012-09-05 16:54 ` Eli Zaretskii
2012-09-05 19:19 ` Stephen J. Turnbull
2012-09-05 20:34 ` Tom Tromey
2012-09-06 0:20 ` Stephen J. Turnbull
2012-09-06 1:53 ` Tom Tromey
2012-09-06 8:34 ` Stephen J. Turnbull
2012-09-05 18:13 ` Stefan Monnier
2012-09-05 18:28 ` Tom Tromey
2012-09-05 19:14 ` Stefan Monnier
2012-09-05 18:20 ` Tom Tromey
2012-09-05 19:00 ` Stephen J. Turnbull
2012-09-05 19:10 ` Tom Tromey
2012-09-05 19:50 ` Eli Zaretskii
2012-09-05 20:48 ` Stephen J. Turnbull
2012-09-06 5:16 ` Eli Zaretskii
2012-09-06 9:22 ` Stephen J. Turnbull
2012-09-06 10:58 ` Eli Zaretskii
2012-09-07 1:26 ` Stephen J. Turnbull
2012-09-05 20:25 ` Stephen J. Turnbull
2012-09-05 19:45 ` Eli Zaretskii
2012-09-05 19:46 ` Eli Zaretskii
2012-09-06 2:28 ` Stefan Monnier
2012-09-06 5:24 ` Eli Zaretskii
2012-09-06 12:32 ` Stefan Monnier
2012-09-05 3:49 ` SAKURAI Masashi
2012-09-05 4:34 ` Dmitry Antipov
2012-09-05 9:44 ` martin rudalics
2012-09-05 16:28 ` Eli Zaretskii
2012-09-06 7:19 ` martin rudalics
2012-09-06 7:56 ` Eli Zaretskii
2012-09-06 14:41 ` martin rudalics
2012-09-06 14:55 ` Eli Zaretskii
2012-09-06 16:04 ` martin rudalics
2012-09-06 17:07 ` Stefan Monnier
2012-09-06 17:37 ` martin rudalics
2012-09-06 18:22 ` Eli Zaretskii
2012-09-06 19:25 ` Eli Zaretskii
2012-09-07 9:52 ` martin rudalics
2012-09-06 21:28 ` Stefan Monnier [this message]
2012-09-07 9:52 ` martin rudalics
2012-09-07 14:44 ` Stefan Monnier
2012-09-07 16:13 ` martin rudalics
2012-09-07 18:31 ` Stefan Monnier
2012-09-06 20:49 ` PJ Weisberg
2012-09-07 5:52 ` Eli Zaretskii
2012-09-07 15:28 ` PJ Weisberg
2012-09-08 14:58 ` Nix
2012-09-08 15:21 ` Eli Zaretskii
2012-09-08 19:45 ` Stefan Monnier
2012-09-05 13:41 ` Stefan Monnier
2012-09-05 14:34 ` Tom Tromey
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=jwvk3w6265x.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
--cc=tromey@redhat.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).