Re: FVWM: Is there a way to stop a window from de-iconifying itself?

> Hi Chris,
>
> I don't have an FVWM3 solution. Sorry if this is not relevant, but have 
> you considered running the program in in a non-windowed version of emacs 
> (emacs -nw)  or running your elisp program in "batch" mode?
>
> The expression below:
>
>       (progn (sleep-for 10) 't)
>
> does not cause emacs to try to deiconify when run in *scratch* with 
> either eval-last-sexp or eval-print-last-sexp. Is it possible that there 
> is something in the code that you are running that is explicitly calling 
> a function to display a buffer/frame? Another tack might be to try to 
> determine why the code that you are running is causing a frame to 
> display when other elisp code does not.

My code was only a demonstration to reproduce the problem easily; the
core issue it was showing was 'call display-buffer after some delay so
you can iconify Emacs'. My actual Emacs deiconification problems mostly
come from interactive code (such as MH-E) that calls display-buffer
after doing some time-consuming thing (such as displaying a complex
formatted email message) that takes long enough that I iconify Emacs to
do something else, although there are other paths that force
deiconification that I see less frequently. Unfortunately running 'emacs
-nw' is far less attractive for what I use GNU Emacs for.

	- cks