slime-macroexpand-again when buffer not a macroexpansion buffer
Bug #777405 reported by
mon_key
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Slime |
New
|
Undecided
|
Unassigned |
Bug Description
`slime-
To post a comment you must log in.
What this means is that when one evaluates M-x slime-macroexpa nd-again in a lisp file which is not a macroexpansion- buffer e.g. some-file- i-do-not- want-clobbered. lisp the contents of the file _are_ clobbered by slime-macroexpa nd-again and left in a more or less unrecoverable state! This happens easily when one uses values of `minibuffer- history' for M-x command completion esp. b/c `slime- macroexpand- *' is a prefix for at least seven different interactive macro-expansion related commands including: macroexpand- 1 macroexpand- 1-inplace macroexpand- again macroexpand- all macroexpand- all-inplace macroexpand- undo macroexpansion- minor-mode
slime-
slime-
slime-
slime-
slime-
slime-
slime-
The Interactive `slime- macroexpand- *' commands which might potentially clobber the contents of current-buffer should check that current-buffer is in fact a macro-expansion buffer before proceeding...
--
/s_P\