From: Stefan Monnier <monnier@iro.umontreal.ca>
To: martin rudalics <rudalics@gmx.at>
Cc: 'Lars Magne Ingebrigtsen' <larsi@gnus.org>, 4550@debbugs.gnu.org
Subject: bug#4550: 23.1; give users a choice for quitting backtrace buffer
Date: Mon, 18 Jul 2011 09:45:20 -0400 [thread overview]
Message-ID: <jwvtyajwvot.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4E22ADDC.9060105@gmx.at> (martin rudalics's message of "Sun, 17 Jul 2011 11:39:40 +0200")
>> I want the frame to either remain or be deleted, not iconified.
>> I want users to be able to specify the behavior they prefer.
> We can add a buffer display specifier which tells a priori what to do
> with the window/frame/buffer when the window is no more needed. For
> that I'd need a list of specification concepts for
> - what to do with the window (delete it or keep it),
> - what to do with the frame (iconfiy, delete, keep it, make it
> invisible),
> - what to do with the buffer (kill it, bury it),
> with an optional function that could be called for each of these.
Sounds way overkill to me.
All Drew needs AFAIK is a bury-buffer-function that lets him change the
iconify-frame default to something else.
Stefan
next prev parent reply other threads:[~2011-07-18 13:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 17:00 bug#4550: 23.1; give users a choice for quitting backtrace buffer Drew Adams
2011-07-13 13:54 ` Lars Magne Ingebrigtsen
2011-07-13 15:29 ` Drew Adams
2011-07-13 15:35 ` Lars Magne Ingebrigtsen
2011-07-13 15:52 ` Drew Adams
2011-07-13 16:21 ` Lars Magne Ingebrigtsen
2011-07-13 16:53 ` Drew Adams
2011-07-16 17:41 ` Stefan Monnier
2011-07-17 9:39 ` martin rudalics
2011-07-17 10:18 ` Štěpán Němec
2011-07-17 12:06 ` martin rudalics
2011-07-17 12:21 ` Štěpán Němec
2011-07-17 13:00 ` martin rudalics
2011-07-18 13:45 ` Stefan Monnier [this message]
2012-10-06 17:37 ` martin rudalics
2012-10-08 13:28 ` Drew Adams
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=jwvtyajwvot.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=4550@debbugs.gnu.org \
--cc=larsi@gnus.org \
--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).