unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jonas@bernoul.li, emacs-devel@gnu.org
Subject: Re: Let mode-line packages distinguish the selected-window
Date: Sun, 27 Oct 2019 08:48:17 +0100	[thread overview]
Message-ID: <87879675-7cf6-9daa-12b0-d5b9cb4c3813@gmx.at> (raw)
In-Reply-To: <837e4qu6hj.fsf@gnu.org>

 > If we are going to add this feature as a C primitive, it should
 > ideally free the Lisp programmers from jumping through any additional
 > hoops, IMO.  So the above should be done in C instead, before
 > returning the value.  If some applications may want the minibuffer
 > window and others won't,

This is for applications that want to know the "usually" selected
window while the minibuffer window is selected.  It's still unclear to
me what 'minibuffer-selected-window' should really return in the first
place.  Its doc-string

   Return window selected just before minibuffer window was selected.

is misleading because, while the minibuffer is active, I always can
select a window that is not minibuf_selected_window and then select
the minibuffer window again.

 > we should make the function accept an
 > optional argument to select between these two alternatives.

The current version would be for users to evaluate right now.  If it
suits their needs, we can always provide it as a primitive.

martin



  reply	other threads:[~2019-10-27  7:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 13:38 Let mode-line packages distinguish the selected-window Jonas Bernoulli
2019-10-26 14:01 ` Eli Zaretskii
2019-10-26 21:10   ` martin rudalics
2019-10-27  5:01     ` Eli Zaretskii
2019-10-27  7:48       ` martin rudalics [this message]
2019-10-27 21:13     ` Jonas Bernoulli
2019-10-28  9:40       ` martin rudalics
2019-10-28 10:32         ` Jonas Bernoulli
2019-10-29  9:27           ` martin rudalics
2019-10-29 12:24             ` Eli Zaretskii
2019-10-29 18:05               ` martin rudalics
2019-10-29 18:46                 ` Eli Zaretskii
2019-10-30  8:14                   ` martin rudalics
2019-10-30 16:10                     ` Eli Zaretskii
2019-10-28 15:55       ` Eli Zaretskii
2019-10-29 11:50         ` Jonas Bernoulli
2019-10-26 16:36 ` Stefan Monnier
2019-10-26 19:27   ` Jonas Bernoulli
2019-10-26 19:41     ` Eli Zaretskii
2019-10-26 20:36     ` Stefan Monnier
2019-10-27 18:08       ` Jonas Bernoulli
2019-10-27 21:55         ` Stefan Monnier

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=87879675-7cf6-9daa-12b0-d5b9cb4c3813@gmx.at \
    --to=rudalics@gmx.at \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jonas@bernoul.li \
    /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).