From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: martin rudalics <rudalics@gmx.at>, emacs-devel@gnu.org
Subject: Re: [display-buffer] a way to make it behave as before?
Date: Thu, 23 Jun 2011 08:20:40 +0900 [thread overview]
Message-ID: <b4mk4cd1mif.fsf@jpl.org> (raw)
In-Reply-To: BANLkTikf+Xf7969JZMHBvkCxkhxU5k7asA@mail.gmail.com
Juanma Barranquero wrote:
> On Wed, Jun 22, 2011 at 15:32, Katsumi Yamaoka <yamaoka@jpl.org> wrote:
>> Please consider that those
>> who use bzr Emacs are not necessarily the Emacs developers.
> There are releases for a reason. It's OK for people who want to live
> in the edge to use the main repository, but restricting development
> because of them seems absurd. As has been discussed several times, we
> don't even guarantee that the trunk will be in a compilable / bootable
> state at all times (though it usually is). Outside users who find
> themselves unable to use a given revision can revert to a previous
> one.
> Juanma
First of all, it's not my original purpose to oust enterprising
developments. But as for `display-buffer-alist', it looks hard
to customize so as to make it one's favorite. In fact, it's
hard (or impossible?) to make it behave as exactly the same as
old Emacsen. I might get to like it, but my interest is not
necessarily in window.el and I have no time to debug it thoroughly
for the moment. I was only made to waste time to work around[1].
I think it was not too late to have installed the new feature to
the trunk after having provided an option that enables a user to
make it work like old Emacsen.
[1] http://article.gmane.org/gmane.emacs.devel/140706
next prev parent reply other threads:[~2011-06-22 23:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 9:54 [display-buffer] a way to make it behave as before? Katsumi Yamaoka
2011-06-17 15:47 ` martin rudalics
2011-06-20 5:39 ` Katsumi Yamaoka
2011-06-20 6:21 ` Katsumi Yamaoka
2011-06-20 9:25 ` martin rudalics
2011-06-20 10:39 ` Katsumi Yamaoka
2011-06-20 12:23 ` martin rudalics
2011-06-20 23:04 ` Katsumi Yamaoka
2011-06-21 2:11 ` Katsumi Yamaoka
2011-06-21 14:05 ` Katsumi Yamaoka
2011-06-21 16:11 ` martin rudalics
2011-06-22 1:13 ` Katsumi Yamaoka
2011-06-22 7:20 ` martin rudalics
2011-06-22 13:32 ` Katsumi Yamaoka
2011-06-22 13:45 ` martin rudalics
2011-06-22 14:32 ` Drew Adams
2011-06-22 14:59 ` joakim
2011-06-23 5:07 ` Miles Bader
2011-06-22 16:43 ` Thierry Volpiatto
2011-06-23 6:40 ` Katsumi Yamaoka
2011-06-23 9:48 ` martin rudalics
2011-06-23 10:21 ` Katsumi Yamaoka
2011-06-23 11:08 ` martin rudalics
2011-06-23 11:52 ` David Kastrup
2011-06-22 15:13 ` Juanma Barranquero
2011-06-22 23:20 ` Katsumi Yamaoka [this message]
2011-06-23 0:23 ` Juanma Barranquero
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=b4mk4cd1mif.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--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).