all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: emacs-devel@gnu.org
Subject: Re: Is there a way to control where frames get created?
Date: Mon, 01 Oct 2018 17:06:47 +0200	[thread overview]
Message-ID: <5BB23807.2080507@gmx.at> (raw)
In-Reply-To: <20181001070643.0c0afc09@jabberwock.cb.piermont.com>

 >> BTW the X-position 690 of your new frame is much larger than I would
 >> expect from 0 + 675.  So this seems even more broken.
 >
 > No, that's fine. I deliberately added 15 pixels there for a couple of
 > reasons. (I wanted to be able to see if I was obscuring any
 > terminals, a thin strip of the background is good for this purpose.
 > It isn't a bug, I did it myself.)

A pity somehow, because it means that we don't get any two pixel
symmetry.  If, as a rule, you always subtract two pixels for the top
position of the new window, do you get always exact vertical
alignment?  Even with the old window at top zero?  Or is there some
randomness?

martin



  reply	other threads:[~2018-10-01 15:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 22:37 Is there a way to control where frames get created? Perry E. Metzger
2018-09-30  1:37 ` Drew Adams
2018-09-30  7:57 ` martin rudalics
2018-09-30 12:05   ` Perry E. Metzger
2018-09-30 12:22     ` martin rudalics
2018-09-30 14:14   ` Perry E. Metzger
2018-09-30 14:41     ` Perry E. Metzger
2018-09-30 16:20       ` Stefan Monnier
2018-09-30 17:48         ` martin rudalics
2018-09-30 18:07           ` Perry E. Metzger
2018-09-30 17:47       ` martin rudalics
2018-09-30 18:35         ` Perry E. Metzger
2018-10-01  8:35           ` martin rudalics
2018-10-01 11:06             ` Perry E. Metzger
2018-10-01 15:06               ` martin rudalics [this message]
2018-09-30 11:58 ` Michael Heerdegen

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=5BB23807.2080507@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=perry@piermont.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.