[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#17893: 24.4.50; (error "Marker does not point anywhere")
|
From: |
Drew Adams |
|
Subject: |
bug#17893: 24.4.50; (error "Marker does not point anywhere") |
|
Date: |
Wed, 2 Jul 2014 07:22:23 -0700 (PDT) |
> > Doesn't it seem odd that the backtrace would *start* with
> > `clear-temporary-map'?
>
> No, it's run from a pre-command-hook.
I see. Would a feasible enhancement be for an error backtrace to
show which pre-command-hook function was invoked, and indicate that
that function was invoked from `pre-command-hook'?
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/01
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2014/07/01
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/01
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2014/07/01
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/01
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2014/07/02
- bug#17893: 24.4.50; (error "Marker does not point anywhere"),
Drew Adams <=
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2014/07/02
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/02
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stefan Monnier, 2014/07/02
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/02
- bug#17893: 24.4.50; (error "Marker does not point anywhere"), Stephen Berman, 2014/07/02
bug#17893: 24.4.50; (error "Marker does not point anywhere"), Drew Adams, 2014/07/15