unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Po Lu <luangruo@yahoo.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: make-frame-command with multiple munitors
Date: Wed, 21 Sep 2022 12:55:12 +0200	[thread overview]
Message-ID: <CAO48Bk_5-fp0zvZUtcXJo68bQST8vHoXuFjnuyJ+M=EATZX0KA@mail.gmail.com> (raw)
In-Reply-To: <87r105gfsl.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]

Well... if I'm on the Linux laptop it's the laptop's TFT and if I'm on the
macbook Pro, I mean the Macbook Pro's TFT ...

/PA

On Wed, 21 Sept 2022 at 12:53, Po Lu <luangruo@yahoo.com> wrote:

> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
> > I stand corrected ... this is what happens when the morning coffee has
> not yet kicked in and you write an email ;-)
> >
> > So, in my case, i observe that the root window both on my Linux Laptop
> and on the Macbook Pro coincides with the device's display.
> > I have the device on my right and I place an additional physical display
> on the left. So the + 32 in my code is the equivalent I found
> > to the (left . 32) (top .32) in the xx-frame-alist.
>
> "Device's display?"
>
> Which of "display", "screen" or "monitor" do you mean by that?
>


-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 1739 bytes --]

  reply	other threads:[~2022-09-21 10:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  9:35 Re: Re: make-frame-command with multiple munitors Pedro Andres Aranda Gutierrez
2022-09-20 10:14 ` Emanuel Berg
2022-09-20 11:07 ` Po Lu
2022-09-20 14:37   ` Pedro Andres Aranda Gutierrez
2022-09-21  2:15     ` Po Lu
2022-09-21  5:08       ` Pedro Andres Aranda Gutierrez
2022-09-21  5:22         ` Pedro Andres Aranda Gutierrez
2022-09-21  5:44           ` Po Lu
2022-09-21  9:21             ` Pedro Andres Aranda Gutierrez
2022-09-21 10:52               ` Po Lu
2022-09-21 10:55                 ` Pedro Andres Aranda Gutierrez [this message]
2022-09-21 11:44                   ` Po Lu
  -- strict thread matches above, loose matches on Subject: below --
2022-09-15 15:15 Pascal Quesseveur
2022-09-17 17:55 ` Juri Linkov
2022-09-17 18:37   ` wilnerthomas--- via Emacs development discussions.
2022-09-19  7:21   ` Pascal Quesseveur
2022-09-19 12:28     ` Po Lu
2022-09-19 13:21       ` Christopher Dimech
2022-09-19 13:38         ` Po Lu
2022-09-19 14:54           ` Christopher Dimech
2022-09-19 17:58       ` Pascal Quesseveur
2022-09-19 19:22         ` Juri Linkov
2022-09-20  6:57           ` Juri Linkov
2022-09-19 20:16         ` Christopher Dimech

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='CAO48Bk_5-fp0zvZUtcXJo68bQST8vHoXuFjnuyJ+M=EATZX0KA@mail.gmail.com' \
    --to=paaguti@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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 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).