all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>,
	Lennart Borgman <lennart.borgman@gmail.com>
Cc: 6068@debbugs.gnu.org
Subject: bug#6068: make-frame-visible but not selected
Date: Fri, 2 Jul 2021 14:25:41 +0200	[thread overview]
Message-ID: <bfe46f38-14f3-52e5-fdc4-975552f3274a@gmx.at> (raw)
In-Reply-To: <87v95tt13p.fsf@gnus.org>

 >> So I seem to be unable to reproduce this (under Debian/bullseye, under
 >> Gnome Shell).
 >>
 >> Are you still seeing this issue in recent Emacs versions?
 >
 > More information was requested, but no response was given within a
 > month, so I'm closing this bug report.  If the problem still exists,
 > please respond to this email and we'll reopen the bug report.

Just to elaborate: After

   (setq frame (window-frame))
   (make-frame)

a plain

   (make-frame-visible frame)

indeed won't change anything.  But

   (setq frame (window-frame))
   (make-frame)
   (iconify-frame frame)

followed by

   (make-frame-visible frame)

usually will shift focus to the frame.  Conceptually,

   (set-frame-parameter frame 'no-focus-on-map t)

should fix it but here on Debian Buster this does not work and I have to
use

   (set-frame-parameter frame 'no-accept-focus t))

to handle Lennart's use case.  This is not TRT because the frame
probably should accept focus later but so far I have not found a
reliable way to fix that.

martin





  reply	other threads:[~2021-07-02 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-30 19:39 bug#6068: Please learn Emacs to distinguish between visible and active windows Lennart Borgman
2021-06-03  9:00 ` bug#6068: make-frame-visible but not selected Lars Ingebrigtsen
2021-07-02 11:19   ` Lars Ingebrigtsen
2021-07-02 12:25     ` martin rudalics [this message]
2021-07-02 12:27       ` Lars Ingebrigtsen

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=bfe46f38-14f3-52e5-fdc4-975552f3274a@gmx.at \
    --to=rudalics@gmx.at \
    --cc=6068@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=lennart.borgman@gmail.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.