From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Juanma Barranquero'" <lekktu@gmail.com>
Cc: 8911@debbugs.gnu.org
Subject: bug#8911: bs-cycle-next deletes window in some cases.
Date: Wed, 29 Jun 2011 11:21:03 -0700 [thread overview]
Message-ID: <339CDDF170EF4297B476C3ADC0A7CBCC@us.oracle.com> (raw)
In-Reply-To: <EBE9304982FA49E4A3F4AD4A7D0B7E89@us.oracle.com>
> Even if you insisted on prepopulating the hook so that the
> _default_ behavior was whatever you prefer (e.g. iconifying),
> what I would like is for users to have real control over
> the behavior - not just some binary option to delete
> instead of iconify.
Let me also be clear that it is not about hook vs option. It would be fine with
me if we had a user option for this instead of a hook, as long as it let you do
just as much.
E.g., a function to be invoked after the buffer order is changed. Function
`ignore' would take care of the do-nothing case. The function would need to
accept the buffer as its (first) argument.
What I object to is Stefan's proposal of an option that allows only a choice
between deleting the frame and iconifying it.
next prev parent reply other threads:[~2011-06-29 18:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 11:01 bug#8911: bs-cycle-next deletes window in some cases Juanma Barranquero
2011-06-21 13:37 ` martin rudalics
2011-06-21 14:00 ` Juanma Barranquero
2011-06-21 14:42 ` martin rudalics
2011-06-21 15:02 ` Juanma Barranquero
2011-06-21 16:12 ` martin rudalics
2011-06-21 16:21 ` Juanma Barranquero
2011-06-21 16:28 ` Stefan Monnier
2011-06-21 16:37 ` Juanma Barranquero
2011-06-22 2:14 ` Stefan Monnier
2011-06-22 2:31 ` Juanma Barranquero
2011-06-22 20:11 ` Stefan Monnier
2011-06-21 16:22 ` Stefan Monnier
2011-06-21 16:28 ` Juanma Barranquero
2011-06-21 17:15 ` Drew Adams
2011-06-22 2:11 ` Stefan Monnier
2011-06-22 2:53 ` Drew Adams
2011-06-22 3:13 ` Drew Adams
2011-06-22 20:07 ` Stefan Monnier
2011-06-22 22:01 ` Drew Adams
2011-06-23 21:55 ` Stefan Monnier
2011-06-25 21:24 ` Juanma Barranquero
2011-06-26 9:29 ` martin rudalics
2011-06-26 11:25 ` Juanma Barranquero
2011-06-27 1:30 ` Stefan Monnier
2011-06-27 1:53 ` Juanma Barranquero
2011-06-27 7:00 ` martin rudalics
2011-06-27 9:38 ` Juanma Barranquero
2011-06-27 12:46 ` martin rudalics
2011-06-27 14:01 ` Juanma Barranquero
2011-06-27 14:12 ` martin rudalics
2011-06-27 14:22 ` Juanma Barranquero
2011-06-27 20:11 ` Juanma Barranquero
2011-06-29 3:27 ` Stefan Monnier
2011-06-29 3:57 ` Juanma Barranquero
2011-06-30 17:02 ` Stefan Monnier
2011-06-30 18:50 ` Juanma Barranquero
2011-07-01 12:07 ` Juanma Barranquero
2011-06-29 7:11 ` martin rudalics
2011-06-30 17:06 ` Stefan Monnier
2011-06-29 11:36 ` Juanma Barranquero
2011-06-29 15:36 ` Drew Adams
2011-06-29 18:21 ` Drew Adams [this message]
2011-06-30 7:00 ` martin rudalics
2011-06-30 15:31 ` Drew Adams
2011-06-22 2:07 ` Stefan Monnier
2011-06-21 16:36 ` martin rudalics
2011-06-21 17:07 ` 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=339CDDF170EF4297B476C3ADC0A7CBCC@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=8911@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.