unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Handling minibuffers in several mini-windows
Date: Sun, 10 Jan 2021 12:38:24 +0000	[thread overview]
Message-ID: <X/r1QDwpFDTMQd/R@ACM> (raw)
In-Reply-To: <875z45vvwr.fsf@gnus.org>

Hello, Lars.

On Sun, Jan 10, 2021 at 13:06:12 +0100, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > 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?

> i and ii sound good to me.  I'm not sure about iii -- I think trying it
> out and see what it feels like in practice might be a good idea, though.

An idea: in (iii), how about asking the user with yes-or-no-p before
aborting more than one level?  It's something which is unlikely to come
up more than occasionally.

> -- 
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2021-01-10 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-08 18:54 Handling minibuffers in several mini-windows Alan Mackenzie
2021-01-08 20:32 ` Stefan Monnier
2021-01-10  0:56   ` Alan Mackenzie
2021-01-10 12:06 ` Lars Ingebrigtsen
2021-01-10 12:38   ` Alan Mackenzie [this message]
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/r1QDwpFDTMQd/R@ACM \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).