🚀 go-pugleaf

Dear sirs:

Emacs version is 18.55 running on Sun3/60 with SunOS-3.5.

(1) revert-buffer function seems to try to keep the value of buffer's
    buffer-read-only variable.  Following program, which is about the middle
    part of revert-buffer program, reveals it.

       ....
       ....
       (let ((buffer-read-only nil))    <-- look here
         ;; Bind buffer-file-name to nil
         ....
         ....

    But, after-find-file function, which revert-buffer calls as the last
    step, forces to set buffer-read-only variable ignoring its current value.
    Following is the header part of after-find-file program.

       (setq buffer-read-only (not (file-writable-p buffer-file-name)))


    This fact sometimes causes the situation to which the user doesn't intend.

    For example, after opening some file in read-mode, that is, opening the
    file with ^X-^r (find-file-read-only) command, invoking revert-buffer
    function changes this buffer to non-read-mode.

(2) Invoking the following tiny function shows something strange.


       (defun wn-revert-buffer (buf &optional no-autosave-offer-p noconfirm)
         (save-excursion
           (set-buffer buf)
           (revert-buffer no-autosave-offer-p noconfirm)))


    First, visit some file with ^X-^f (find-file) command, and move the cursor
    to the end of the buffer.

    Then, invoke

        (wn-revert-buffer (current-buffer))

    and you will see the cursor moving to the beginning of the buffer.

    revert-buffer function is designed to keep the cursor position as much as
    (as far as?  English is difficult :-)) possible.  Why does the cursor
    move?

Thanks.





CAUTION: (1) Reply-command in the mail system may NOT generate my address
             correctly.  Please use the following address instead.

               shin%sgtp.apple.juice.or.jp@uunet.uu.net

         (2) I have no relation to Apple Computer Inc. :-)

---
S.Sugou