bug#160: marked as done (Documentation of top-level doesn't mention that it kills minibuffers)

[don@donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 895 bytes --]


Your message dated Sat, 06 Sep 2008 13:28:27 -0400
with message-id <87hc8tkwuc.fsf@cyd.mit.edu>
and subject line Re: Documentation of top-level doesn't mention that it kills minibuffers
has caused the Emacs bug report #160,
regarding Documentation of top-level doesn't mention that it kills minibuffers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact don@donarmstrong.com
immediately.)


-- 
160: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=160
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 7394 bytes --]

From: nisse@lysator.liu.se (Niels Möller)
To: bug-gnu-emacs@gnu.org
Subject: Documentation of top-level doesn't mention that it kills minibuffers
Date: Fri, 25 Apr 2008 09:50:33 +0200
Message-ID: <nniqy61igm.fsf@sellafield.lysator.liu.se>

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




[-- Attachment #3: Type: message/rfc822, Size: 1524 bytes --]

From: Chong Yidong <cyd@stupidchicken.com>
To: nisse@lysator.liu.se (Niels Möller)
Cc: 160-done@emacsbugs.donarmstrong.com
Subject: Re: Documentation of top-level doesn't mention that it kills minibuffers
Date: Sat, 06 Sep 2008 13:28:27 -0400
Message-ID: <87hc8tkwuc.fsf@cyd.mit.edu>

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

I've updated the docs accordingly.  Thanks.