all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 36250@debbugs.gnu.org
Subject: bug#36250: [PATCH] Allow Emacs to be resized arbitrarily
Date: 17 Jun 2019 07:54:44 -0000	[thread overview]
Message-ID: <20190617075444.83363.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.222.1560709505.10840.bug-gnu-emacs@gnu.org>

Hello, Eli.

In article <mailman.222.1560709505.10840.bug-gnu-emacs@gnu.org> you wrote:
>> From: Konstantin Kharlamov <Hi-Angel@yandex.ru>
>> Date: Sun, 16 Jun 2019 21:01:22 +0300
>> 
>> This constraint disallows standard compliant window managers to make
>> Emacs fullscreen on certain screen resolutions (ones that are not
>> multiple of width_inc and height_inc), or to expand Emacs to fill free
>> space on the screen (on certain sizes too).
>> 
>> It doesn't seem to do anything useful otherwise; besides some WMs
>> (like i3wm) just ignore this property anyway.
>> 
>> * src/xterm.c (x_wm_set_size_hint): don't set width_inc, height_inc, and
>>   GDK_HINT_RESIZE_INC.
>> * src/gtkutil.c (x_wm_set_size_hint): don't set width_inc, height_inc, and
>>   PResizeInc.
>> * src/emacsgtkfixed.c (XSetWMSizeHints): don't set width_inc and height_inc.

> 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.

Yes.  Having a whole number of lines in a window is a legitimate thing to
want.

Also, I remember vaguely partial lines causing problems in Follow Mode in
the past.  In case they cause problems there again, or somewhere else, we
should have the ability to disable partial lines.

> Also, this change (and the variable to be added) should be called out
> in NEWS.

-- 
Alan Mackenzie (Nuremberg, Germany).






  parent reply	other threads:[~2019-06-17  7:54 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16 17:59 bug#36250: Allow Emacs to be resized arbitrarily Konstantin Kharlamov
2019-06-16 18:01 ` bug#36250: [PATCH] " Konstantin Kharlamov
2019-06-16 18:24   ` Eli Zaretskii
2019-06-16 18:34     ` Eli Zaretskii
2019-06-17  8:22       ` martin rudalics
2019-06-17  8:41         ` Konstantin Kharlamov
2019-06-17  8:46           ` martin rudalics
2019-06-17  8:58           ` Juanma Barranquero
2019-06-16 18:42     ` Konstantin Kharlamov
2019-06-16 18:53       ` Eli Zaretskii
2019-06-16 18:59         ` Konstantin Kharlamov
2019-06-16 19:07           ` Eli Zaretskii
2019-06-16 19:15             ` Eli Zaretskii
2019-06-16 18:22 ` bug#36250: " Konstantin Kharlamov
2019-06-16 18:22 ` bug#36250: [PATCH v2] " Konstantin Kharlamov
2019-06-16 18:55 ` bug#36250: [PATCH v3] " Konstantin Kharlamov
2019-06-16 19:10   ` Eli Zaretskii
2019-06-17 12:32     ` Konstantin Kharlamov
2019-06-17 14:56       ` Eli Zaretskii
2019-06-18 20:34         ` Konstantin Kharlamov
2019-06-19 16:13           ` Eli Zaretskii
2020-08-26 10:26       ` Lars Ingebrigtsen
     [not found] ` <mailman.222.1560709505.10840.bug-gnu-emacs@gnu.org>
2019-06-17  7:54   ` Alan Mackenzie [this message]
2019-06-17  8:43     ` bug#36250: [PATCH] " martin rudalics
2019-06-17 14:38       ` Eli Zaretskii
2019-06-18  8:17         ` martin rudalics
2019-06-18 15:49           ` Eli Zaretskii
2019-06-17  8:21 ` bug#36250: " martin rudalics
2019-06-17  8:27   ` Konstantin Kharlamov
2019-06-17  8:44     ` martin rudalics
2019-06-17  9:14       ` Konstantin Kharlamov
2019-06-17  9:46         ` martin rudalics
2019-06-17 14:41         ` Eli Zaretskii
2019-06-18 20:35 ` bug#36250: [PATCH] Improve a bit frame-resize-pixelwise documentation Konstantin Kharlamov
2019-06-18 20:38   ` Andreas Schwab
2019-06-19 16:16   ` Eli Zaretskii
2019-06-28 11:27     ` Konstantin Kharlamov
2019-06-28 13:16       ` Eli Zaretskii
2019-06-28 13:59         ` Konstantin Kharlamov
2019-06-28 14:22           ` Eli Zaretskii
2019-06-28 14:34             ` Konstantin Kharlamov
2019-06-28 14:49               ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190617075444.83363.qmail@mail.muc.de \
    --to=acm@muc.de \
    --cc=36250@debbugs.gnu.org \
    --cc=eliz@gnu.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.