[[[...(org)...]]] in the mode line

[[[...(org)...]]] in the mode line

[ishi soichi]

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

Hi.  Most likely the problem is my settings of Emacs.  But I do not know
what causes it.

After booting Emacs, (I am not sure if it is due to the state of idling), "[
]" appears around the name of mode.
For example, if it is the org-mode,

[[[...(org)...]]]

if it is the scratch buffer,

[[[...(Lisp Iteration)...]]]

This seems to appear to all modes simultaneously.
Seemingly it does not affect the continuation of my work, but it bothers
because I do not understand why it is happening.

Could anyone guess what is causing it?

Thanks in advance.

soichi

[-- Attachment #2: Type: text/html, Size: 803 bytes --]

Re: [[[...(org)...]]] in the mode line

[Jeff Horn]

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.

On Mon, Jan 24, 2011 at 12:13 AM, ishi soichi <soichi777@gmail.com> wrote:
> Hi.  Most likely the problem is my settings of Emacs.  But I do not know
> what causes it.
> After booting Emacs, (I am not sure if it is due to the state of idling), "[
> ]" appears around the name of mode.
> For example, if it is the org-mode,
> [[[...(org)...]]]
> if it is the scratch buffer,
> [[[...(Lisp Iteration)...]]]
> This seems to appear to all modes simultaneously.
> Seemingly it does not affect the continuation of my work, but it bothers
> because I do not understand why it is happening.
> Could anyone guess what is causing it?
> Thanks in advance.
> soichi
>



-- 
Jeffrey Horn
http://www.failuretorefrain.com/jeff/

Re: ]] in the mode line

[rusi]

On Jan 24, 10:26 am, Jeff Horn <jrhorn...@gmail.com> wrote:
> 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.
>
>
>
> On Mon, Jan 24, 2011 at 12:13 AM, ishi soichi <soichi...@gmail.com> wrote:
> > Hi.  Most likely the problem is my settings of Emacs.  But I do not know
> > what causes it.
> > After booting Emacs, (I am not sure if it is due to the state of idling), "[
> > ]" appears around the name of mode.
> > For example, if it is the org-mode,
> > [[[...(org)...]]]
> > if it is the scratch buffer,
> > [[[...(Lisp Iteration)...]]]
> > This seems to appear to all modes simultaneously.
> > Seemingly it does not affect the continuation of my work, but it bothers
> > because I do not understand why it is happening.
> > Could anyone guess what is causing it?
> > Thanks in advance.
> > soichi
>
> --
> Jeffrey Hornhttp://www.failuretorefrain.com/jeff/

abort-recursive-edit -- usually bound to C-] -- done as many times as
there are '[..]' should remove them

Re: [[[...(org)...]]] in the mode line

[Memnon Anon]

Hi,

> On Mon, Jan 24, 2011 at 12:13 AM, ishi soichi <soichi777@gmail.com> wrote:
...
>> [[[...(org)...]]]
>> [[[...(Lisp Iteration)...]]]

Jeff Horn <jrhorn424@gmail.com> 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

Re: [[[...(org)...]]] in the mode line

[Tim X]

Memnon Anon <gegendosenfleisch@googlemail.com> writes:

> Hi,
>
>> On Mon, Jan 24, 2011 at 12:13 AM, ishi soichi <soichi777@gmail.com> wrote:
> ...
>>> [[[...(org)...]]]
>>> [[[...(Lisp Iteration)...]]]
>
> Jeff Horn <jrhorn424@gmail.com> 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

RE: [[[...(org)...]]] in the mode line

[Drew Adams]

In addition to what Tim and others have said, do `C-x C-b' and see if you have a
nonempty *Backtrace* buffer.

If so, visit it to see what happened: typically an error led to a backtrace
stack display.  You can quit the debugger (*Backtrace*) by hitting `q'. But if
this is happening often then it can be a good idea to at least check what kind
of error is being raised.

Re: [[[...(org)...]]] in the mode line

[ishi soichi]

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

Thanks everyone.

"Backtrace" rings a bell.  When I try to write elisp codes, often this
buffer pops up because my elisp skills are not so good...
Well, it relieves me a bit because now I understand where to look for the
problem.

I will keep in mind if the Backtrace buffer shows up.

Thanks again.

soichi

[-- Attachment #2: Type: text/html, Size: 427 bytes --]