all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 18637@debbugs.gnu.org
Subject: bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows
Date: Tue, 07 Oct 2014 21:26:23 +0300	[thread overview]
Message-ID: <8361fvlos0.fsf@gnu.org> (raw)
In-Reply-To: <41484edb-9aaa-4f56-bf46-4ab70b609aac@default>

> Date: Tue, 7 Oct 2014 11:12:56 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 18637@debbugs.gnu.org
> 
> > That's my understanding as well, but someone who has access to such
> > a system should actually try that and report back.
> > 
> > > I guess that would mean that frame-position coordinates (`left',
> > > `top') are then interpreted relative to that other monitor (?).
> > > Is that right?
> > 
> > No, I think they are "ignored".  That is, the coordinates are
> > interpreted in the virtual coordinate system, but then Windows
> > decides on its own how to position the frame, using the criterion
> > described above.
> 
> By "criterion described above, do you mean just based on which monitor
> is showing more of the frame?

Yes.

> (Note too that I am using MS Windows, but the OP who reported the
> problem is, I think, not on Windows.)

Then the problem might be even more complicated than I thought ;-)

> > > But if that were the case then I would think that restoring a
> > > recorded `left' etc. parameter later would put the frame back
> > > where it was, which is apparently not what is happening.
> > 
> > Except that Windows has its own rules, see above, at least when you
> > create a frame that didn't exist (i.e. restore it from information
> > recorded in some file).
> 
> This code does not create any new frames.  It just calls
> `modify-frame-parameters' on an existing frame, setting its `left',
> `top', `width', and `height' parameters.

Then I'd expect it to "just work".  Of course, it doesn't, so there's
some factor or factors at work that we don't understand.

> > That's a lot of code, and I have no way of trying it.
> 
> If you are interested, you can try it easily, by downloading these
> two files:
> http://www.emacswiki.org/emacs-en/download/frame-cmds.el
> http://www.emacswiki.org/emacs-en/download/frame-fns.el

No, I meant I have no access to a system with more than one monitor.





  reply	other threads:[~2014-10-07 18:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<c75b3094-d24b-4949-9c1e-b513c0b5bed7@default>
     [not found] ` <<ce89167f-4906-496e-9ace-4d51e1741311@default>
     [not found]   ` <<83tx3flxn2.fsf@gnu.org>
2014-10-07 18:12     ` bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows Drew Adams
2014-10-07 18:26       ` Eli Zaretskii [this message]
     [not found]     ` <<41484edb-9aaa-4f56-bf46-4ab70b609aac@default>
     [not found]       ` <<8361fvlos0.fsf@gnu.org>
2014-10-07 18:31         ` Drew Adams
     [not found] <<b5ac6ce3-5c0d-4517-a44f-6925cfccdcfd@default>
     [not found] ` <<837g0dm95c.fsf@gnu.org>
2014-10-06 17:25   ` Drew Adams
2014-10-05 19:23     ` Drew Adams
2014-10-05 19:30       ` Eli Zaretskii
2014-10-05 19:44         ` Eli Zaretskii
2014-10-06 18:08       ` Andy Moreton
2014-10-06 18:23         ` Drew Adams
2014-10-07 18:35       ` Andy Moreton
2014-10-07 20:25         ` Drew Adams
2014-10-06 19:29     ` Eli Zaretskii
2014-10-06 20:52     ` Drew Adams
2014-10-07 15:14       ` Eli Zaretskii
     [not found] <<b3d0f532-3b29-43d3-a41d-6687886307dc@default>
     [not found] ` <<83ppe5mfed.fsf@gnu.org>
2014-10-06 16:31   ` Drew Adams
2014-10-06 16:54     ` Eli Zaretskii
     [not found] <<12fc196e-cc82-4f22-8d2f-cede95542ea7@default>
     [not found] ` <<83vbnymi0h.fsf@gnu.org>
     [not found]   ` <<83tx3imhdg.fsf@gnu.org>
2014-10-06  2:55     ` Drew Adams
2014-10-06 14:39       ` Eli Zaretskii
2014-10-06 16:34         ` Stefan Monnier
2014-10-06  2:55   ` Drew Adams

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=8361fvlos0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18637@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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.