unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 38535@debbugs.gnu.org
Subject: bug#38535: 26.3; Optionally make recursive editing more noticeable
Date: Sun, 8 Dec 2019 15:19:28 -0800 (PST)	[thread overview]
Message-ID: <1a644d72-cf7e-4dd5-951a-8ceca8543008@default> (raw)
In-Reply-To: <87lfrmwhpl.fsf@mail.linkov.net>

> > Recursive editing is sometimes useful.
> > Its main disadvantage is that you might not
> > be aware that you've entered or exited a
> > recursive edit.
> 
> But there is minibuffer-depth-indicate-mode that shows the recursion
> depth in the minibuffer prompt when recursive minibuffers are enabled.

Unrelated.

Minibuffer recursion is indicated as you say.
It is not indicated by [...] in the mode line.

 "Minibuffer input is a special kind of
  recursive editing." (elisp) `Recursive Editing'

This is about a non-minibuffer recursive edit,
which is indicated only by a not-very-noticeable
[...] in the mode line.

Those two are handled very differently in terms
of UI and interaction.

For the same reason that we highlight the
minibuffer indication of minibuffer depth, minor
mode `rec-edit-mode' can highlight the [...]
brackets.  ("Can", because an option controls
whether the highlighting occurs.)





  reply	other threads:[~2019-12-08 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-08 18:30 bug#38535: 26.3; Optionally make recursive editing more noticeable Drew Adams
2019-12-08 22:50 ` Juri Linkov
2019-12-08 23:19   ` Drew Adams [this message]
2021-06-14 14:33     ` 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=1a644d72-cf7e-4dd5-951a-8ceca8543008@default \
    --to=drew.adams@oracle.com \
    --cc=38535@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).