unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: emacs-25 3722a69: Fix bugs in window resizing code
Date: Tue, 01 Mar 2016 19:20:04 +0200	[thread overview]
Message-ID: <83egbu6rp7.fsf@gnu.org> (raw)
In-Reply-To: <56D5CB91.4060108@gmx.at> (message from martin rudalics on Tue, 01 Mar 2016 18:04:17 +0100)

> Date: Tue, 01 Mar 2016 18:04:17 +0100
> From: martin rudalics <rudalics@gmx.at>
> Cc: emacs-devel@gnu.org
> 
>  > `enlarge-window' appears on several places on the Elisp sources,
>  > including calls like
>  >
>  > textmodes/two-column.el:305:6:    (enlarge-window 99999 t))
>  >
>  > which now will result on a error.
> 
> Ugly.  Earlier, with code like this you never knew whether the author's
> intention was to maximize the window or to delete all other windows in
> the same combination.  The author should either use ‘maximize-window’ or
> `delete-other-windows-vertically' instead.  Please file a bug report.
> 
>  > To be clear, I have nothing against throwing an error on the interactive
>  > case, but against throwing the error on the non-interactive one. That's
>  > what constitutes an API change on my book.
>  >
>  > So I would suggest to remove the `error' and consider where and when to
>  > add it after the release, after studying the code in the wild.
> 
> I can make any change people want but won't make any decision.  John,
> Eli?

MO is that we should fix all uses of enlarge-window and shrink-window
in our sources, and otherwise leave the change in 25.1.  Maybe also
document that in NEWS as potentially incompatible behavior.  I don't
think we should postpone the bugfix to 26.1, because I don't really
believe anything will happen until then that will change the
situation: the same problems this could cause now it will cause then.



  reply	other threads:[~2016-03-01 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160218102715.15576.42604@vcs.savannah.gnu.org>
     [not found] ` <E1aWLnn-000448-7K@vcs.savannah.gnu.org>
2016-03-01  1:31   ` emacs-25 3722a69: Fix bugs in window resizing code Óscar Fuentes
2016-03-01  8:07     ` martin rudalics
2016-03-01 15:10       ` Óscar Fuentes
2016-03-01 17:04         ` martin rudalics
2016-03-01 17:20           ` Eli Zaretskii [this message]
2016-03-02  8:22             ` martin rudalics
2016-03-02  9:28               ` martin rudalics
2016-03-02 15:54               ` Eli Zaretskii
2016-03-04  7:48                 ` martin rudalics
2016-03-04  8:28                   ` Eli Zaretskii

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=83egbu6rp7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=ofv@wanadoo.es \
    --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).