From: "Drew Adams" <drew.adams@oracle.com>
To: 14147@debbugs.gnu.org
Subject: bug#14147: 24.3.50; turn on `minibuffer-depth-indicator-mode' by default
Date: Fri, 5 Apr 2013 10:03:46 -0700 [thread overview]
Message-ID: <C508BE570A2C4340AD732AAE0A81F290@us.oracle.com> (raw)
It is unfortunate that this minor mode is still not turned on by
default. There is no reason not to do so. The mode has no effect when
there is no recursive minibuffer, which is most of the time. And when
there is a recursive minibuffer it is essential that that fact be
communicated to users, one way or another. This mode provides one way.
mb-depth.el has been present in the code for years now, but it is still
essentially ignored, unknown to most users. Please put it to use,
letting users know when they are in a recursive minibuffer, by default.
Novice users are the least likely to discover this feature, and they are
perhaps the most in need of its aid.
This is no different from Emacs automatically adding nested `[...]' to
the mode line to indicate recursive editing levels. No one would
suggest that that indicator be turned off by default and that users be
forced to learn about it on their own and turn it on. The same should
be the case for indicating recursive minibuffer levels. Should be a
no-brainer.
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
of 2013-03-28 on ODIEONE
Bzr revision: 112173 monnier@iro.umontreal.ca-20130328163306-419khox8aneaoaxv
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
`configure --with-gcc (4.7) --no-opt --enable-checking --cflags
-IC:/Devel/emacs/build/include --ldflags -LC:/Devel/emacs/build/lib'
next reply other threads:[~2013-04-05 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 17:03 Drew Adams [this message]
2013-04-05 21:38 ` bug#14147: 24.3.50; turn on `minibuffer-depth-indicator-mode' by default Stefan Monnier
2013-04-06 0:19 ` Drew Adams
2016-04-28 23:20 ` Lars Ingebrigtsen
2016-04-29 16:46 ` Drew Adams
2016-05-02 9:28 ` Nicolas Richard
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=C508BE570A2C4340AD732AAE0A81F290@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=14147@debbugs.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 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.