all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Konstantin Kharlamov <hi-angel@yandex.ru>
Cc: 36250@debbugs.gnu.org
Subject: bug#36250: Allow Emacs to be resized arbitrarily
Date: Mon, 17 Jun 2019 17:41:41 +0300	[thread overview]
Message-ID: <83r27stgt6.fsf@gnu.org> (raw)
In-Reply-To: <1560762868.11992.2@yandex.ru> (message from Konstantin Kharlamov on Mon, 17 Jun 2019 12:14:28 +0300)

> Date: Mon, 17 Jun 2019 12:14:28 +0300
> From: Konstantin Kharlamov <hi-angel@yandex.ru>
> Cc: 36250@debbugs.gnu.org
> 
> > > 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 :)
> > 
> > You either have to set it in your initial file (like I do, for
> > example) or before a new frame is created.
> 
> I just tested it, and it works. However I've always wondered, is there 
> a place in .emacs file, which is guaranteed to be executed before a 
> window is created? I may be mistaken, but it looks to me like Emacs 
> tries to create window almost immediately on start, and that the (setq 
> frame-resize-pixelwise t) line at the beginning of the config being 
> executed before window is created is pure luck.

It doesn't have to be sheer luck: Emacs resets some display-related
parameters after it reads the init files, precisely to cater to the
cases such as this one.  I don't know if this parameter is one of
those that benefit from this, but it might be.  One example of
settings that definitely are acted upon after reading the init file is
default-frame-alist.





  parent reply	other threads:[~2019-06-17 14:41 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
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 [this message]
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=83r27stgt6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=36250@debbugs.gnu.org \
    --cc=hi-angel@yandex.ru \
    /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.