OOPS!--how can I select the "oopsed" entity that reappears?

I have sometimes caught myself typing "oops" , when I intended "undo".
So the oops command re-creates something that I erased maybe 10 minutes
ago,--- and whatever it was, I don't need it coming back to haunt me.
How can I find it?

 

How can you find what? So you want to undo - then type "u" as many times as
needed.

 

It will be the "previous" entity.
just erase "p".

 

It will be the "previous" entity.

No, it won't .

The identity of the last item erased isn't kept in a system variable, and
I'm not aware of a way to retrieve it, though Acad obviously keeps track of
it internally.

The solution would be, don't type the wrong command. If this is an ongoing
problem, and you can live without the OOPS command, you could redefine it to
do some thing harmless.

(command "undefine" "oops")

(defun cops ()
(alert "OOPS is not UNDO!")
(princ)
)

I'd strongly advise against redefining oops to be the same as undo, because
that would only exacerbate the bad habit.

 

No, it won't .

Yes it will.

"Doctor, it hurts if I do this"

"Then don't do that"

Great advice.

 

Yes it will.

I stand corrected. On a quick test I didn't see this, but it seems to work
consistently. This would indeed serve as a way to "find" an unerased entity,
assuming you know you need to be looking for such a thing.

OP said he "sometimes caught" himself typing the wrong command. Does he
always, infallibly, catch the mistake when he makes it? I'd tend to doubt
that. He could be undeleting objects all over the place and not noticing if
they're off screen. And if he's not aware of it, then the "erase previous"
trick isn't going to be of any help. A simple U would accomplish the same
thing -- undo the OOPS -- if he knew it needed doing.

Actually that would be the only reasonable and correct advice, if the
patient were doing something unnecessary and self destructive. In the case
of a bad habit, maybe the habit needs changing. The doc may need to "help"
the patient stop doing the wrong thing.

Perhaps you got so excited about firing off a response that you didn't
notice I offered a specific solution: a lisp function to disable the OOPS
command and replace it with something harmless. I see this as one possible
approach to the bad-habit problem.

The idea of using an alert box is that it would be annoying, and hopefully
serve as an incentive to stop typing the wrong command. A less annoying
alternative would be (princ "\nOOPS is not UNDO!"). In either case, I'd
intend this only as a temporary training tool, on the asssumption that he
could live without OOPS temporarily until the command confusion thing went
away. I'd also recommend a change from UNDO to U, just to shake up these
habits a bit more. I'm not sure why he'd be typing UNDO in any case, as most
people use U.

 

THANKS everybody.
Gee whiz, I didnt mean to start a whole psychological/medical analysis
here!. It ain't such a serious issue.
But what confused me was that the "last" option doesnt work.It seems
logical to me that ,since the undo command adds an entity onto the
screen and into the data base, that entity should be selectable with
"last".
But I suppose I'll survive by using "previous" instead.

 

I stand corrected.
" Perhaps you got so excited about firing off a response that you didn't..."

BTW, who's OP?

 

Original Poster.

 

OIC.

Thought he was kin to Andy

 

Since OOPS brings back the entire selection set from the last ERASE command
(or BLOCK or WBLOCK if you chose to delete the entities in the process), it
can bring back multiple entities. Picking Last would only select one of
them, IF those are even the last entities in the drawing. If you drew some
other things after erasing and before doing OOPS, then Last would find
something that's not even part of that OOPSed set, so you need to use
Previous. The only time Last would be equivalent would be when BOTH: you
hadn't added any other things to the drawing since erasing; AND you had only
erased one entity.

 

The ERASE P is only going to work if you discover the mistake and act on it
right away, before you've done anything else that would change your
"previous" set. If that's the case, then it seems to me that a simple U to
undo the mistaken OOPS would accomplish the same thing with fewer
keystrokes.