all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Tassilo Horn <tsdh@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: On the pains of using child-frames / posframes
Date: Tue, 20 Jul 2021 09:21:30 +0200	[thread overview]
Message-ID: <80529c3c-6704-f8a2-1a97-94d4eeb2e7e7@gmx.at> (raw)
In-Reply-To: <87a6miyuxi.fsf@gnu.org>

 > Daniel is away for some days and then
 > I'm away for two weeks, so I've proven again to be a specialist in
 > inadequate timing.  Don't hold your breath but I'm pretty sure we (and
 > especially Daniel) will pick up the discussion in the nearer future and
 > come up with a proposal.

Just to elaborate on two aspects:

(1) Any fix we come up with for the `no-accept-focus' misbehavior should
     fix any misbehavior of this for normal top-level frames too and also
     handle any misbehavior of `no-focus-on-map'.  I suppose we should do
     this in handle_one_xevent and/or x_detect_focus_change in xterm.c.

(2) The `posn-at-point' problem with overlays is very likely a separate
     issue and should be reported and fixed separately.

martin



      reply	other threads:[~2021-07-20  7:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210715105707.10057.54746@vcs0.savannah.gnu.org>
     [not found] ` <20210715105709.4F14820D13@vcs0.savannah.gnu.org>
2021-07-15 14:07   ` [elpa] externals/corfu a44c778 1/2: Yet another hack: posn-at-point computation returns wrong y-coordinate on Emacs 28 Stefan Monnier
2021-07-16  0:46     ` Daniel Mendler
2021-07-17 20:18       ` On the pains of using child-frames / posframes Tassilo Horn
2021-07-18  8:30         ` martin rudalics
2021-07-19 19:07           ` Tassilo Horn
2021-07-20  7:21             ` martin rudalics [this message]

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=80529c3c-6704-f8a2-1a97-94d4eeb2e7e7@gmx.at \
    --to=rudalics@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=tsdh@gnu.org \
    /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.