GNU bug report logs - #36250
Allow Emacs to be resized arbitrarily

Previous Next

Package: emacs;

Reported by: Konstantin Kharlamov <hi-angel <at> yandex.ru>

Date: Sun, 16 Jun 2019 18:01:02 UTC

Severity: wishlist

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #32 received at 36250 <at> debbugs.gnu.org (full text, mbox):

From: Konstantin Kharlamov <hi-angel <at> yandex.ru>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 36250 <at> debbugs.gnu.org
Subject: Re: bug#36250: [PATCH] Allow Emacs to be resized arbitrarily
Date: Sun, 16 Jun 2019 21:59:26 +0300

В Вс, июн 16, 2019 at 21:53, Eli Zaretskii <eliz <at> gnu.org> 
написал:
>>  Date: Sun, 16 Jun 2019 21:42:25 +0300
>>  From: Konstantin Kharlamov <hi-angel <at> yandex.ru>
>>  Cc: 36250 <at> debbugs.gnu.org
>> 
>>  > Thanks, but after so many years of doing this stuff the way we 
>> do, and
>>  > without any experts in this domain on board, I think we need to 
>> leave
>>  > behind a "fire escape" -- a variable that users could set from 
>> Lisp to
>>  > get back the old behavior.  There are too many window managers out
>>  > there, and we cannot be sure none of them need the old code.
>> 
>>  As I noted, "unconstrained behavior" is widely tested. At the very
>>  least, it's tested by users of i3wm.
> 
> We've been there before: the real world out there never ceases to
> surprise us, no matter how sure we are in our conclusions.  I've
> learned that lesson after seeing our best intentions backfire enough
> times.

Okay, then, should I maybe bring it up on emacs-devel? I wanted 
initially to do just that, but then I figured that searching for 
reasons why these variables were added in the first place should be 
enough. But if not, I can still open a topic there.






This bug report was last modified 4 years and 268 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.