🚀 go-pugleaf

In article <2842@msn123> renaud@spock (Roland Renaud) writes:

   Repeat by having minimum ~/.emacs file containing line
	   (server-start)

   step 1: Run emacs in one window.
   step 2: In another window, run "emacsclient file".

   File appears in emacsserver (as it should) but after hitting the first
   key (any key) in the emacs session, the contents of the file vanish.

When Emacs displays the startup message, it does a (sit-for 120) before
removing the startup message.  Unfortunately, it doesn't check to make
sure that the world hasn't changed underneath it before erasing the
current buffer.  The emacs server can handle emacsclient requests in the
middle of the (sit-for 120) ...

   If step 2 is repeated, things will work properly.

   Workaround: for some reason, the following line must be
	   in the .emacs file.
   (setq inhibit-startup-message t)  ; stop getting that start up screen

   Not a major problem but it surprised a few people here.

I'm including a fix for this behavior.

-- 
Joe Wells <jbw@bu.edu>
jbw%bucsf.bu.edu@cs.bu.edu
...!harvard!bu-cs!bucsf!jbw
----------------------------------------------------------------------
*** /usr14/gnu/dist-18.55/lisp/startup.el	Fri Apr  7 22:03:10 1989
--- startup.el	Fri Apr  6 17:27:53 1990
***************
*** 192,199 ****
  Type \\[help-with-tutorial] for a tutorial on using Emacs.")))
  		   (set-buffer-modified-p nil)
  		   (sit-for 120))
! 	     (erase-buffer)
! 	     (set-buffer-modified-p nil))))
      (let ((dir default-directory)
  	  (line 0))
        (while command-line-args-left
--- 192,200 ----
  Type \\[help-with-tutorial] for a tutorial on using Emacs.")))
  		   (set-buffer-modified-p nil)
  		   (sit-for 120))
! 	       (cond ((string-equal (buffer-name) "*scratch*")
! 		      (erase-buffer)
! 		      (set-buffer-modified-p nil))))))
      (let ((dir default-directory)
  	  (line 0))
        (while command-line-args-left