From: Robert Pluim <rpluim@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 31031@debbugs.gnu.org
Subject: bug#31031: 27.0; (elisp) `Position Parameters', floating-point values
Date: Fri, 06 Apr 2018 12:28:38 +0200 [thread overview]
Message-ID: <87fu48pr1l.fsf@gmail.com> (raw)
In-Reply-To: <87sh8bw4xa.fsf@gmail.com> (Robert Pluim's message of "Wed, 04 Apr 2018 14:07:45 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>> D'oh. Of course, top is the right parameter to use. With that the
>>> frame switches monitor between top and bottom, so that would imply
>>> that the same switching should happen for "left". Iʼm undecided so far
>>> as to which I think is the "correct" behaviour.
>>
>> I'm not sure I understand. Do you mean that when you change the value
>> of 'left' the frame always stays within the left monitor while when
>> you change 'top' the frame moves from the upper to the lower monitor
>> and back? That would be queer.
>
> Iʼll have to retest this one, I may have missed a case.
Two monitors, one above the other, frame on bottom one.
(modify-frame-parameters nil '((top . 0.0)))
=> frame moves to top monitor
(modify-frame-parameters nil '((top . 1.0)))
=> frame moves tobottom monitor
Repeating those commands cycles between top and bottom monitor.
(and they're not flush to the edges, but this is with GDK scaling
going on, so Iʼm not too surprised by that).
Two monitors, one next to the other, frame on right one.
(modify-frame-parameters nil '((left . 0.0)))
=> frame moves to left monitor
(modify-frame-parameters nil '((left . 1.0)))
=> frame moves to right monitor
and again this cycles between the monitors. So whatever I tested
before, it wasn't this, and the behaviour is consistent between "left"
and "top".
I can't find anything in the elisp manual describing that the
workareas of the two monitors are combined like this. Should such
information go in (elisp)Multiple Terminals, or (emacs)Multiple
Displays? Or both?
Robert
next prev parent reply other threads:[~2018-04-06 10:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 21:56 bug#31031: 27.0; (elisp) `Position Parameters', floating-point values Drew Adams
2018-04-03 6:46 ` martin rudalics
2018-04-03 8:25 ` Robert Pluim
2018-04-03 10:23 ` martin rudalics
2018-04-03 12:35 ` Robert Pluim
2018-04-03 16:18 ` modify-frame-parameters with floating point offsets Robert Pluim
2018-04-03 21:50 ` Robert Pluim
2018-04-04 7:51 ` martin rudalics
2018-04-04 7:51 ` martin rudalics
2018-04-04 8:54 ` Robert Pluim
2018-04-05 6:59 ` martin rudalics
2018-04-05 14:07 ` Robert Pluim
2018-04-04 7:49 ` bug#31031: 27.0; (elisp) `Position Parameters', floating-point values martin rudalics
2018-04-04 12:07 ` Robert Pluim
2018-04-05 7:00 ` martin rudalics
2018-04-05 14:21 ` Robert Pluim
2018-04-06 10:28 ` Robert Pluim [this message]
2018-04-06 12:56 ` Eli Zaretskii
2018-04-06 13:09 ` Robert Pluim
2018-04-06 13:19 ` Eli Zaretskii
2018-04-03 15:08 ` Drew Adams
2018-04-04 7:51 ` martin rudalics
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=87fu48pr1l.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31031@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.