unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: emacs-devel@gnu.org
Subject: Handling minibuffers in several mini-windows
Date: Fri, 8 Jan 2021 18:54:03 +0000	[thread overview]
Message-ID: <X/iqS+2hZEgebHbf@ACM> (raw)

Hello, Emacs.

This post probably belongs in the thread "Stop frames stealing
eachothers' minibuffers!", but I think people are beginning to suffer
thread-fatigue wrt that thread.  Only Martin R. is currently posting
things to me in that thread.  (Thanks, Martin!)

The problem arises when minibuffer-follows-selected-frame is configured
to nil, thus allowing several mini-windows to be simultaneously visible
in several frames.  As long as the user attempts to use only the most
deeply nested MB, that isn't a problem, but when she tries to type into,
terminate, or abort another MB, we've got to decide how to handle it.

My proposal (which I've already implemented and tried out, though not
published at all), is that
(i) it should be possible to type into, and edit text in any visible
  minibuffer;
(ii) it should be possible to terminate (by RET `exit-minibuffer') only
  the most deeply nested MB.  The attempt elsewhere should display an
  error message, leaving the MBs unchanged;
(iii) it should be possible to abort (with C-g `abort-recursive-edit'),
  any minibuffer.  This will have the effect of aborting all more deeply
  nested MBs at the same time.

What do people think about this?

-- 
Alan Mackenzie (Nuremberg, Germany).



             reply	other threads:[~2021-01-08 18:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 18:54 Alan Mackenzie [this message]
2021-01-08 20:32 ` Handling minibuffers in several mini-windows Stefan Monnier
2021-01-10  0:56   ` Alan Mackenzie
2021-01-10 12:06 ` Lars Ingebrigtsen
2021-01-10 12:38   ` Alan Mackenzie
2021-01-11 14:22     ` 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

  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=X/iqS+2hZEgebHbf@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@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 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).