From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>,
"'Katsumi Yamaoka'" <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: RE: [display-buffer] a way to make it behave as before?
Date: Wed, 22 Jun 2011 07:32:53 -0700 [thread overview]
Message-ID: <1029299D6A2A4D43B5599BC7D4C9CD00@us.oracle.com> (raw)
In-Reply-To: <4E01F1F6.2060705@gmx.at>
> > The best choice is to revert all your recent changes, I really,
> > really believe. I also really believe that you are really
> > skillful, so I really believe you will bring the new version that
> > makes everyone happy, within a month. Please consider that those
> > who use bzr Emacs are not necessarily the Emacs developers.
>
> Well this recommendation is not "really" helpful. I've set up a bzr
> branch more than a year ago and asked people to try it but with the
> exception of Juanma nobody did. So I have to go through with this by
> annoying people in order to get some feedback.
>
> The only other choice I see is reverting my changes and leave
> the window code to someone else.
No, we should not give up. Patience, for all. There are lots of cases to
consider, no doubt, and it will take some time to iron out all the problems.
Some of us might not be able to use the development Emacs builds (beyond using
them as emacs -Q) for a while, but if we provide enough feedback and Martin can
fix the code to handle the cases we report then we'll get through this.
Think how long it took to get the latest round of mouse changes completed. This
has to be at least as hairy, I would guess.
I don't know that we'll all be satisfied at the end, but I do know that Martin
is trying to handle the cases we report. And I'm hoping that we all will be
satisfied - and better than that.
next prev parent reply other threads:[~2011-06-22 14:32 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 [this message]
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
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=1029299D6A2A4D43B5599BC7D4C9CD00@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
--cc=yamaoka@jpl.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 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).