11:05 a.m.
Hello
This behaviour annoys me for a long time. I understand that upon some
error Xemacs enters in recursive-edit mode. However my impression is
that, at least in my configuration, Xemacs enters recursive-edit far too
often.
Of course I can quit by abort-recursive-edit, but as I said I find it
annoying. I looked for some variable to get rid of this behaviour, I
found none. So do I have to live with it? Or is there something in my
configuration which causes this behaviour?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4:26 p.m.
Uwe Brauer writes:
This behaviour annoys me for a long time. I understand that upon
some
error Xemacs enters in recursive-edit mode. However my impression is
that, at least in my configuration, Xemacs enters recursive-edit far too
often.
Control-a during incremental search often causes this, in my
experience. . .
I'll try to look at the backtrace next time it happens. . .
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht(a)inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
1:02 p.m.
Uwe Brauer writes:
This behaviour annoys me for a long time. I understand that upon
some
error Xemacs enters in recursive-edit mode. However my impression is
that, at least in my configuration, Xemacs enters recursive-edit far too
often.
I almost never see recursive edit, so I can't guess from my own
experience what you're talking about. If you can't say more than "too
often", there's not much we can do. We need to know what you are
doing when recursive edit gets invoked.
Of course I can quit by abort-recursive-edit, but as I said I find
it
annoying. I looked for some variable to get rid of this behaviour, I
found none. So do I have to live with it? Or is there something in my
configuration which causes this behaviour?
It's not your configuration. As far as I can see, recursive editing
simply isn't configurable.
Most likely, as Henry suggests, it's something about the way you use
isearch. (The other cases are in search and replace, and in the
prompt for save-some-buffers, which I would think you would notice and
mention.) You could try removing the single call to
`(recursive-edit)' in isearch.el, but I can't promise that won't screw
up something else.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
2:17 p.m.
New subject: debugging and error? (was: to often in recursive edit)
> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Uwe Brauer writes:
> This behaviour annoys me for a long time. I understand that upon some
> error Xemacs enters in recursive-edit mode. However my impression is
> that, at least in my configuration, Xemacs enters recursive-edit far too
> often.
I almost never see recursive edit, so I can't guess from my own
experience what you're talking about. If you can't say more than "too
often", there's not much we can do. We need to know what you are
doing when recursive edit gets invoked.
Hm I am not 100 % sure I am really in recursive-edit, since
describe-mode does not list it, but even if I explicitly enter
recursive-edit describe-mode does not list it.
All I can say is:
it seems that I entered recursive edit right now, without using
isearch. So how to I know that I am in recursive-edit.
Well in the modeline I see [(Message
instead of (Message
and I know that C-] returns the modeline in its original state. So maybe this
indicator is misleading.
I run view-lossage and see
Entering debugger..
It seems that this call changed the modeline.
There is another issue is:
the ([ indicator is not only annoying, but sometimes screws up when I
want to save a file:
when I am in a LaTeX buffer and try to save the buffer, and if the ([
modeline indicator is shown, then a message pops up, "save
buffer as", which should not happen.
So C-] quits the modeline ([ indicator and the saving function works as
expected.
I am not sure whether my indications clarified the issue.... :'(
Ah when I type C-] then the window splits in two and the ([ modeline
indicator disappears.
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
3:07 p.m.
New subject: debugging and error? (was: to often in recursive edit)
Uwe Brauer writes:
Well in the modeline I see [(Message
instead of (Message
Then you're in recursive edit. But we need to know why.
I run view-lossage and see
What does view-lossage say your last few hundred keystrokes were?
the ([ indicator is not only annoying, but sometimes screws up when
I
want to save a file:
Well, yes, that kind of thing is going to happen when you're in
recursive edit. You're in a state where you're disconnected from your
previous history to some extent.
Ah when I type C-] then the window splits in two
Dunno why that would happen, unless you were in a split window
configuration before you entered recursive edit.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
8:07 p.m.
New subject: debugging and error? (was: to often in recursive edit)
Uwe Brauer wrote:
I run view-lossage and see
Entering debugger..
The debugger uses recursive-edit, but it shouldn't be entered unless
explicitly requested using debug-on-entry or by setting
debug-on-error.
What are the values of debug-on-error and debug-function-list ?
Both of those should be nil by default, and I wouldn't recommend
changing either via customize or init files, so both of those should
still be nil after normal start-up. If debugging has been enabled for
a function via debug-on-entry, it will remain enabled until explicitly
cancelled via cancel-debug-on-entry.
--
Glynn Clements <glynn(a)gclements.plus.com>
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
9:04 p.m.
New subject: debugging and error?
> "Glynn" == Glynn Clements
<glynn(a)gclements.plus.com> writes:
Uwe Brauer wrote:
> I run view-lossage and see
>
> Entering debugger..
The debugger uses recursive-edit, but it shouldn't be entered
unless
explicitly requested using debug-on-entry or by setting
debug-on-error.
Right, this was the problem!
What are the values of debug-on-error
t
Both of those should be nil by default, and I wouldn't recommend
changing either via customize or init files, so both of those should
still be nil after normal start-up. If debugging has been enabled for
a function via debug-on-entry, it will remain enabled until explicitly
cancelled via cancel-debug-on-entry.
I don't remember why I had this setting,
maybe in a time where I had to
debug a lot of stuff. Forgot completely about it, set it to nil and
everything is fine now.
thanks
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta
4027
days inactive
4028
days old
6 comments
4 participants
participants (4)
-
Glynn Clements -
Henry S. Thompson -
Stephen J. Turnbull -
Uwe Brauer