[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Documentation of top-level doesn't mention that it kills minibuffers
From: |
Niels Möller |
Subject: |
Documentation of top-level doesn't mention that it kills minibuffers |
Date: |
Fri, 25 Apr 2008 09:50:33 +0200 |
User-agent: |
Gnus/5.1008 (Gnus v5.10.8) Emacs/21.3 (usg-unix-v) |
The documentation string for top-level says "Exit all recursive
editing levels.", and the manual says
: The command `M-x top-level' is equivalent to "enough" `C-]' commands
: to get you out of all the levels of recursive edits that you are in.
: `C-]' gets you out one level at a time, but `M-x top-level' goes out
: all levels at once.
This doesn't mention that the command also kills all existing
minibuffers, which I think is an important feature of that command.
As far as I'm aware, "minibuffer" and "recursive edit" usually refers
to two quite different concepts. I don't know if they are related
internally, but for me, I associate "recursive edit" with the display
of [] in the mode line, which isn't displayed no matter how many
minibuffers I have (I have set enable-recursive-minibuffers to t, and
I can get several dozens of them when my one and a half year old kid
borrows the keyboard...).
Best regards,
/Niels Möller
In GNU Emacs 22.1.1 (i686-pc-linux-gnu)
of 2007-06-04 on maskros.s3.kth.se
Windowing system distributor `The X.Org Foundation', version 11.0.70101000
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: C
value of $LC_CTYPE: en_US.iso-8859-1
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: nil
locale-coding-system: iso-8859-1
default-enable-multibyte-characters: t
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Documentation of top-level doesn't mention that it kills minibuffers,
Niels Möller <=