From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.bugs Subject: bug#32207: 26.1; can't set window position with emacs 26.3 Date: Fri, 20 Jul 2018 08:41:38 +0200 Message-ID: <5B518422.8080707@gmx.at> References: <13991.1531957318@monster.martins.cc> <5B5049B0.6070804@gmx.at> <4103.1532006778@monster.martins.cc> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1532068810 7470 195.159.176.226 (20 Jul 2018 06:40:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 20 Jul 2018 06:40:10 +0000 (UTC) Cc: 32207@debbugs.gnu.org To: emacs@martins.cc Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jul 20 08:40:06 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fgP58-0001mi-TH for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Jul 2018 08:40:03 +0200 Original-Received: from localhost ([::1]:46667 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fgP7F-0000ku-Ou for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Jul 2018 02:42:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:48768) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fgP77-0000ki-IJ for bug-gnu-emacs@gnu.org; Fri, 20 Jul 2018 02:42:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fgP74-0004I9-G3 for bug-gnu-emacs@gnu.org; Fri, 20 Jul 2018 02:42:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:43713) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fgP74-0004Hu-9S for bug-gnu-emacs@gnu.org; Fri, 20 Jul 2018 02:42:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fgP74-0002YB-3A for bug-gnu-emacs@gnu.org; Fri, 20 Jul 2018 02:42:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: martin rudalics Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Jul 2018 06:42:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 32207 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 32207-submit@debbugs.gnu.org id=B32207.15320689179791 (code B ref 32207); Fri, 20 Jul 2018 06:42:02 +0000 Original-Received: (at 32207) by debbugs.gnu.org; 20 Jul 2018 06:41:57 +0000 Original-Received: from localhost ([127.0.0.1]:48731 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fgP6z-0002Xr-L5 for submit@debbugs.gnu.org; Fri, 20 Jul 2018 02:41:57 -0400 Original-Received: from mout.gmx.net ([212.227.15.19]:48001) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fgP6x-0002Xd-Mb for 32207@debbugs.gnu.org; Fri, 20 Jul 2018 02:41:56 -0400 Original-Received: from [192.168.1.101] ([213.162.73.201]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M3igT-1fxf2r2zFx-00rHrv; Fri, 20 Jul 2018 08:41:48 +0200 In-Reply-To: <4103.1532006778@monster.martins.cc> X-Provags-ID: V03:K1:uWfE2EdUuNlhjIrvE+VSXAfOVcJCTQ6u0UmHTPnksR4bF2ZmpkG 72OZn2gio3nY/oHDKbZgl5Xk42luSeG7BvOy700JwEc38RBSQ5YwTgder0LcmmZzmaSX+kY wgF5PLBqRdQO69Sz5z7k0KVRR661SkDhl/LKWHNTxCIFe2RAEhtQCueOfNtfNdKVqXIMu03 rfQuB3FMYeY0DFKKrTcHg== X-UI-Out-Filterresults: notjunk:1;V01:K0:pYJr4B9sCto=:P+GMV88arE3JJj3BbouQxy 0F5yNy2HVO2iOPQU+mkUx5qcAEfwNUQ+awnNlWkjg6mAIVkEQeoj09Yv8BlVikYWa+PjpRPj5 y2OEfWhekwKPyoiAZlKmzImoN/7S2QgqJnT2urlegCcSEtwxKE/ygrx9C4fg5Nj44Eer8XIdy TQm2M0r/lnWIjjsCqBDtyUv70RaedVO5Ox3oAVDq46wKtfpqsg42JqeV+EK0zWo+dZbfqIr4h n4BujH6sP7hqDoyCrMgnYlIWlt0+7ScBZuGI2Tundo75uu6sYy6+B0UjowTWyTKRfNeNDbHm/ HOHdtF7lzbXIwruGK0BPVuOVpJhJxBiEcolHGsSvIRH80NtJWN2TaLfwvjOdd+sRUHGnOK01B +RbaZlL5vf6zd6Rg3fym3ajLCF9nHhwnQHApwyF/gItiO0jmDZhjySFN6oK8y399dmTBlzrDM pakY8Fso4k1tMFO7mVrdQtcP5vACNMNWxas438WL3D/uNzUTIw00bKLp+lAg3O8r0VMZCQYtV zTCBCkGY/vdT5pr7VB2iFFIEC0bg3gMw4EO876ERCqfoIsPXrnbUi4bVRocVQYdgwqZI1G7GX 1+YLyi5/4Z2eIdj3Z40yhnrOTsST6dXQy+fDOgERa/PtgaosjcgwBHVIwvOaYs8t4S+yeykLM KNk0BrBujUnXEFraxRUYRGtUH6A6AIhBVl5BhNl1i0MDm8hpGE11mBNyqdOrykQl/JoOspZQX e/+aBzUvBafLcdxN5vavjXjL6jNBTQwlEGsKzOgNlxVkm0icg64ZfOHGGBL5je7VPCdmJ/kZ X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:148702 Archived-At: > 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