unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'martin rudalics'" <rudalics@gmx.at>
Cc: occitan@esperanto.org, 12419@debbugs.gnu.org
Subject: bug#12419: Mouse click changes layout
Date: Fri, 14 Sep 2012 12:40:35 -0700	[thread overview]
Message-ID: <646E419BC4D542A28891D407B84CE6FE@us.oracle.com> (raw)
In-Reply-To: <50538224.1020607@gmx.at>

> If you have a copy of Emacs 19 or 20 around you will notice that other
> windows did shrink too.

No, I don't see that in Emacs 20 (I don't have 19).  I not only have a copy of
it hanging around, I use it much of the time!

> The "shrink only the adjacent 
> window" behavior you mention was introduced together with 
> `adjust-window-trailing-edge'.

Maybe, but in Emacs 20 I still see only the adjacent window shrink.  I'm on MS
Windows - dunno whether that make a difference.

GNU Emacs 20.7.3 (i386-*-nt5.1.2600) of Thu Dec 21 2000 on buffy

> But this function is not very suitable for the minibuffer.

>  > Consider proposing something for emacs-devel to discuss.  
>  > Was the change in behavior from Emacs 23 to 24 (the change
>  > made so far) ever discussed?
> 
> Partially.  Most of them were the results of attempting to fix errors.
> But I have to admit that I never understood the old code 
> completely so I couldn't even tell what has changed and how.

It would be good to present the alternative behaviors to people in emacs-devel
(and maybe even help-gnu-emacs), so they can make an informed choice.  And it
might be good to let end users have a choice (e.g., via an option), if that's
feasible.

>  > Personally I don't care much, since I don't split windows 
>  > that much.  But this sounds like something that affects lots
>  > of users, and perhaps there should be some discussion about it.
> 
> There should have been more testing before the release.  But I wasn't
> very good at advertising my branch then.

It's not likely that a branch will be tried by many Windows users who don't
build Emacs themselves.

Before inclusion in a release, a change should be available in a pretest
(prerelease version), and users can test it there.  But perhaps there was not
enough pretest time.  I believe that pretests used to be longer in the old days.

For another thing, users of a pretest should be informed (at least via NEWS, and
preferably on emacs-devel by anyone who wants something specific tested during
pretest) about new features to be tested.






  reply	other threads:[~2012-09-14 19:40 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-11 22:04 bug#12419: Mouse click changes layout Daniel Pfeiffer
2012-09-12  2:59 ` Eli Zaretskii
2012-09-12  8:09 ` martin rudalics
2012-09-13 20:41   ` Daniel Pfeiffer
2012-09-14  9:00     ` martin rudalics
2012-09-14 10:36       ` Eli Zaretskii
2012-09-14 13:38         ` martin rudalics
2012-09-14 14:10           ` Drew Adams
2012-09-14 15:08             ` martin rudalics
2012-09-14 16:18               ` Drew Adams
2012-09-14 19:14                 ` martin rudalics
2012-09-14 19:40                   ` Drew Adams [this message]
2012-09-15  9:51                     ` martin rudalics
2012-09-15 10:31                       ` martin rudalics
2012-09-14 14:53           ` Eli Zaretskii
2012-09-14 15:16             ` martin rudalics
2012-09-14 16:20               ` Drew Adams
2012-09-14 19:14                 ` martin rudalics
2012-09-14 16:56               ` Eli Zaretskii
2012-09-14 19:15                 ` martin rudalics
2012-09-14 20:16                   ` Eli Zaretskii
2012-09-15  9:54                     ` martin rudalics
2012-09-15 10:23                       ` Eli Zaretskii
2012-09-15 10:39                         ` martin rudalics
2012-09-15 11:14                           ` Eli Zaretskii
2012-09-15 12:44                             ` martin rudalics
2012-09-15 13:35                               ` Eli Zaretskii
2012-09-15 14:34                                 ` martin rudalics
2012-09-14 15:45             ` Stefan Monnier
2012-09-14 19:14               ` martin rudalics
2012-09-14 19:56                 ` Stefan Monnier
2012-09-15  9:51                   ` martin rudalics
     [not found]       ` <5055D769.1060804@t-online.de>
2012-09-16 17:45         ` martin rudalics
2012-09-22 20:29           ` Daniel Pfeiffer
2012-09-23  9:21             ` martin rudalics
2012-09-23 21:56               ` Daniel Pfeiffer
2012-09-24  8:17                 ` martin rudalics
2012-09-24 14:33                   ` Eli Zaretskii
2012-09-25  9:58                     ` martin rudalics
2012-09-25 12:09                       ` Eli Zaretskii
2012-09-25 14:12                         ` martin rudalics
2012-09-26  8:22                           ` Eli Zaretskii
2012-09-26 11:03                             ` martin rudalics
2012-09-26 11:55                               ` Eli Zaretskii
2012-09-26 12:43                                 ` martin rudalics
2012-09-26 13:17                                   ` Eli Zaretskii
2012-09-26 13:44                                     ` martin rudalics
2012-09-26 13:57                                       ` Eli Zaretskii
2012-09-24 22:20                   ` Daniel Pfeiffer
2012-09-25  6:32                     ` Eli Zaretskii
2012-09-25  9:58                     ` martin rudalics
2020-09-13 17:06               ` Lars Ingebrigtsen
2020-12-07 16:43                 ` Lars Ingebrigtsen

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=646E419BC4D542A28891D407B84CE6FE@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12419@debbugs.gnu.org \
    --cc=occitan@esperanto.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).