From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>
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: Sun, 17 Jul 2011 11:39:40 +0200 [thread overview]
Message-ID: <4E22ADDC.9060105@gmx.at> (raw)
In-Reply-To: <EE3172AD9CF84CB78AD60DA9F46E3C52@us.oracle.com>
> 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.
If a consensus can be reached, this could be easily done. The calling
application would propose the default behavior via an argument and the
user could override it.
martin
next prev parent reply other threads:[~2011-07-17 9:39 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E22ADDC.9060105@gmx.at \
--to=rudalics@gmx.at \
--cc=4550@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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 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.