🚀 go-pugleaf

"...a command's intended definition may not be best for editing with."
(section 29.3.1, GNU Emacs Manual, Fifth Edition, Emacs Version 18, October 1986).

I posted a request to the GNU bboard, and got no useful responses, so I
have to assume that the behavior I describe cannot be cured in any
simple way.  BTW, I did get one response that told me how to prevent
GNU Emacs from spontaneously destroying windows when I enlarge other
windows, and one response that said "If you find out how to do these
things, please tell me, because they bother me too".

There are many operations that I try to perform that cause GNU Emacs to
*FORCE* me to respond to one or more questions; for example, if I
'touch' a c source file to force make to do a recompile (say, to
recompile with a debug switch after a program bombs), when I try to
edit the source file again GNU Emacs will not let me proceed until I
respond to its "Are you sure?" message.  Furthermore, in this and other
situations, GNU Emacs forces me to respond "yes" or "no".

In an editor that is supposed to be user-reconfigurable, and is
supposed to be usable by both novice and expert users, I regard the
inability to disable what I've come to call "Nag mode" as a serious
bug.  I want the ability to tell Emacs to warn me if I'm about to do
something "stupid", but not to impede me.  I want the ability to tell
Emacs to permit me to type 'y' or 'n' in response to *ANY* question
(i.e., always to act as though 'y-or-n-p' is being called, rather then
'yes-or-no-p').  Many of these behaviors are coded into the system, so
simply redefining 'yes-or-no-p' so that it just calls 'y-or-n-p'
doesn't work, and even if I could recompile with a switch that disabled
them this is not appropriate: I should no more dictate to others that
they live dangerously than Emacs should dictate to me that I be
absurdly cautious.  I have been a programmer for over 10 years, and
have been using an Emacs look-alike (first FINE, then Unipress Emacs,
now GNU Emacs) virtually the whole time; I don't want to be mothered by
my editor --  if I say "do it" I want the editor to do it *UNLESS* I
have specifically requested it to look over my shoulder.

While I'm at it, nobody has been able to tell me how to cure another
behavior that I also regard as a bug if it is not used-controllable. 
When I delete a window, I do not want the space thus liberated
distributed among all other windows; I have arranged my screen the way
I want it, and I don't want Emacs to mess with it.  I want the space
given up to the window above the one that is being deleted, as it is in
Unipress Emacs.  This behavior facilitates splitting a window to look
around in a file that you're already editing, then getting  rid of the
window when you're done, a technique I used to use all the time until I
switched over to GNU Emacs.  Now it's such a pain to do it that I'm
forced to jump around in the file within the same window.