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, 20 Jul 2018 08:41:38 +0200 [thread overview]
Message-ID: <5B518422.8080707@gmx.at> (raw)
In-Reply-To: <4103.1532006778@monster.martins.cc>
> No, it fails to position the initial frame period. I start
> one emacs on the "default/initial" screen, another a few
> screens away. Neither obeys the command line position.
I was confused by your earlier text ...
>> them on desk 1/page 1 and desk1/page 5 of my FVWM
>> configuration, and they both start on desk 1/page 1, at the
... and so I now presume that the desk/page specifications have no
relevance to the problem. Right?
>> Does positioning a new frame in a running Emacs session via
>> (make-frame '((left . x) (top . y)))
>
> Just tried it with x and y within the physical desktop and a
> few screens away and neither worked.
Aha. So let's concentrate on 'make-frame' from a running Emacs
session to avoid dealing with the startup rigmarole.
> However, if I kill fvwm and use make-frame, it WORKS! Even
> off screen, which I can see when I restart fvwm.
>
> This is interesting, as I'm running the same fvwm as with
> the previous emacs, where this worked. Also xterms position
> themselves properly. Just tried glxgears, mplayer and it
> works with those too. Xv works within the physical screen,
> it doesn't off-screen.
>
> Maybe Emacs changed the way it requests the screen position
> to a way that fvwm doesn't like. I'll need to try with
> another window manager.
We already have a new window manager dependent issue with Bug#31745.
Just that fvwm is not listed there IIRC.
martin
next prev parent reply other threads:[~2018-07-20 6:41 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
2018-07-20 6:41 ` martin rudalics [this message]
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=5B518422.8080707@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).