From: Konstantin Kharlamov <hi-angel@yandex.ru>
To: martin rudalics <rudalics@gmx.at>
Cc: 36250@debbugs.gnu.org
Subject: bug#36250: Allow Emacs to be resized arbitrarily
Date: Mon, 17 Jun 2019 11:27:42 +0300 [thread overview]
Message-ID: <1560760062.11992.0@yandex.ru> (raw)
In-Reply-To: <90a948a4-8917-67e5-7f47-2c6aced95b73@gmx.at>
On Пн, июн 17, 2019 at 10:21, martin rudalics <rudalics@gmx.at>
wrote:
> > Unconstrained resize of Emacs is widely tested, e.g. I've been
> using
> > for years Emacs on i3wm, which just ignores the property, thus
> > resizes Emacs arbitrarily. Also: I don't touch in this patch
> > `frame_resize_pixelwise` variable, because it's used for something
> > else; in particular, setting this variable had no influence on the
> > problem.
>
> Why do you think that 'frame_resize_pixelwise' is used for something
> else? gtkutil.c uses it to assign the increments as
>
> size_hints.width_inc = frame_resize_pixelwise ? 1 :
> FRAME_COLUMN_WIDTH (f);
> size_hints.height_inc = frame_resize_pixelwise ? 1 :
> FRAME_LINE_HEIGHT (f);
>
> > 1: https://bugs.kde.org/show_bug.cgi?id=408746#c8
> > 2: https://github.com/kwin-scripts/kwin-tiling/issues/161
>
> There Martin Flöser says on 2019-06-16
>
> > Given the resize increment provided by emacs (8x17) it is impossible
> > to fullscreens the window with the used resolution. 1326 doesn't
> > divide by 8 and 681 doesn't divide by 17.
>
> so it appears that you did _not_ set 'frame-resize-pixelwise' since
> otherwise the 8 x 17 wouldn't be there. Can you please clarify.
>
> If setting 'frame-resize-pixelwise' does not work as intended, we
> apparently fail to set the increments in due time. But then this is
> to my knowledge the first time this happens since we introduced that
> variable and we certainly have to fix that. So if it does not work
> for some reason, please use GDB with a checkpoint at these assignments
> and tell us whether frame_resize_pixelwise really wasn't set properly.
From cursory reading of the code, frame_resize_pixelwise is only used
on window creation. Either way, you can easily reproduce it the
following way:
1. Evaluate in Emacs (setq frame-resize-pixelwise t)
2. Execute `xprop | grep "program specified resize increment"`
You will see something like "program specified resize increment: 7 by
15"; both 7 and 15 are certainly bigger than 1 :)
next prev parent reply other threads:[~2019-06-17 8:27 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 ` bug#36250: [PATCH] " Alan Mackenzie
2019-06-17 8:43 ` 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 [this message]
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=1560760062.11992.0@yandex.ru \
--to=hi-angel@yandex.ru \
--cc=36250@debbugs.gnu.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 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.