Re: Interpreted buffer poisoning?
Mats Cronqvist <[email protected]> Tue, 12 Aug 2008 15:05:31 +0200
| Newsgroups | gmane.comp.lang.erlang.distel.devel |
|---|---|
| Message-ID | <[email protected]> |
Paul Fisher wrote: > While it is extra effort to unset interpretion on a buffer, recompile, > reload, and then interpret the buffer again in order to debug after code > changes, it works and I can get by. > > But if I forget to unset interpretation on a buffer where there are > breakpoints enabled, and make *any* change to the buffer, the > breakpoints go from red highlights to purple and nothing I do will allow > breakpoints to work again until I restart emacs. Even if I undo the > change (or unset/set interpretation for the buffer )this "poisoned" > state remains. > > Any suggestions for dealing with this? reloading erlang-mode should do it. M-x erlang-mode > (And is anyone working on making > the debug/edit/compile/reload cycle work more transparently?) > not as far as i know. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/