unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: emacs@martins.cc
Cc: 32207@debbugs.gnu.org
Subject: bug#32207: 26.1; can't set window position with emacs 26.3
Date: Fri, 27 Jul 2018 11:21:23 +0200	[thread overview]
Message-ID: <5B5AE413.20807@gmx.at> (raw)
In-Reply-To: <32574.1532633813@monster.martins.cc>

 > Yes, though I should qualify the "perfectly!" above.
 > - there is an initial frame that seems to be placed by fvwm,
 >    at a position of the window manager's choice
 > - the initial frame is then moves to the position specified
 >    in the command line.
 > - the moves comes almost immediately after the intial
 >    placement, resulting in a flashing effect.

The initial frame serves to display any messages that might be
produced when evaluating your .emacs or init.el file.

With Emacs 27 you can put the 'initial-frame-alist' specification into
an early-init.el file which is loaded before the initial frame is made
by the window system and gets the parameters applied right there.  I
doubt that this will always make correct geometry calculations but the
flashing effect should disappear.

martin





  reply	other threads:[~2018-07-27  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18 23:41 bug#32207: 26.1; can't set window position with emacs 26.3 emacs
2018-07-19  8:20 ` martin rudalics
2018-07-19 13:26   ` emacs
2018-07-19 19:56     ` emacs
2018-07-20  6:42       ` martin rudalics
2018-07-20 20:10         ` Henrique Martins
2018-07-21  7:43           ` martin rudalics
2018-07-22 17:48             ` emacs
2018-07-23  6:51               ` martin rudalics
2018-07-24 19:38                 ` emacs
2018-07-25  6:21                   ` martin rudalics
2018-07-25 20:14                     ` Henrique Martins
2018-07-26  7:56                       ` martin rudalics
2018-07-26 19:36                         ` emacs
2018-07-27  9:21                           ` martin rudalics [this message]
2018-07-20  6:41     ` martin rudalics
2019-12-17 16:00 ` Elof Ofel

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=5B5AE413.20807@gmx.at \
    --to=rudalics@gmx.at \
    --cc=32207@debbugs.gnu.org \
    --cc=emacs@martins.cc \
    /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).