From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim X Newsgroups: gmane.emacs.help Subject: Re: [[[...(org)...]]] in the mode line Date: Tue, 25 Jan 2011 08:16:45 +1100 Organization: Unlimited download news at news.astraweb.com Message-ID: <8739oi57eq.fsf@rapttech.com.au> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1295905880 2114 80.91.229.12 (24 Jan 2011 21:51:20 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Mon, 24 Jan 2011 21:51:20 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Jan 24 22:51:16 2011 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PhUJf-0001Qu-5K for geh-help-gnu-emacs@m.gmane.org; Mon, 24 Jan 2011 22:51:15 +0100 Original-Received: from localhost ([127.0.0.1]:60581 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PhUJe-0002Zu-Jh for geh-help-gnu-emacs@m.gmane.org; Mon, 24 Jan 2011 16:51:14 -0500 Original-Path: usenet.stanford.edu!news.glorb.com!news2.glorb.com!news.astraweb.com!border2.newsrouter.astraweb.com!not-for-mail Original-Newsgroups: gnu.emacs.help User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:1Wz7WfBylgU9gkCXeDjCq7SIq+o= Original-Lines: 53 Original-NNTP-Posting-Host: 2e619d35.news.astraweb.com Original-X-Trace: DXC=of7hMeCKPMH\kdljK^UWoEL?0kYOcDh@JXb<8`kRh<; @jZ[HUKIQP@G]G; 2>V^?kWC48NP]Hm4n:I`amD`:2d; gJk=B]45h:bgO Original-Xref: usenet.stanford.edu gnu.emacs.help:184561 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:78722 Archived-At: Memnon Anon writes: > Hi, > >> On Mon, Jan 24, 2011 at 12:13 AM, ishi soichi wrote: > ... >>> [[[...(org)...]]] >>> [[[...(Lisp Iteration)...]]] > > Jeff Horn writes: >> I, too, would be interested in finding the cause of this. I sometimes >> have as many as 6 or 7 brackets around the modes if emacs has been >> running for a while. > > FWIW, I see this sometimes, too. > I can fix it killing the frame and getting a new one. > Additional brackets are gone in a fresh frame. > (I run emacs as daemon.) > > Memnon > > As mentioned by others, the [[ ]] indicate emacs is in a recursive edit state. There are numerous things that can cause this, some indicating problems and others which are not so bad. For example, if you have many frames open and you do something that causes emacs to start the debugger and you are put into a backtrace, but then you change to another window/frame without quitting the debugger and continue doing some other work, such as reading your mail, you will likely see that emacs is in a recursive edit. One way that may help to track down the point at which the recursive session starts is to close all windows and frames except 1, then hit the escape key 3 times. Note the window and what is happening now. This will often represent the point at which emacs was in just prior to the start of the last recursive edit. If you still have [ ] in the modeline, hit escape another 3 times and note where you are at. Again, this should have unwound the stack to where that recursive edit began. Continue the process, but note at each point where and what was going on. This may provide you a clue as to what is causing the recursie edit. In my experience, this has generally be the result of how I am interactin with the system rather than code in my .emacs etc. Doing things like starting to execute a command, switching to another frame to lookup command arguments, getting distracted and starting to read mail and then later returning to my work, but via another frame and forgetting I was already part-way through something somewhere else can result in a recursive session. Usually, they are not an issue. Tim -- tcross (at) rapttech dot com dot au