bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

emacsserver behavior differs from Info page


From: Tom Lofgren
Subject: emacsserver behavior differs from Info page
Date: 07 Nov 2001 14:30:21 -0800
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1

In GNU Emacs 21.1.1 (i686-pc-linux-gnu, X toolkit)
 of 2001-10-22 on hal
configured using `configure  --prefix=/usr/recourse'
Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: en_US
  locale-coding-system: iso-latin-1
  default-enable-multibyte-characters: t

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

In a vanilla emacs (emacs -q), I do 'M-x server-start', and then I do
'emacsclient foo' from my command-line.  I type some text, and I hit
'C-x #'

I am now asked if I want to save the file.  If I say yes, then the
file is saved, and Emacs switches to a different buffer (it does not
kill the 'foo' buffer, it just switches to another one).  If I say no,
the file is not changed, and again, Emacs does not kill the foo
buffer; it just switches to another one.

The following is an excerpt from the Info documentation on
emacsserver, with my annotations on actual behavior.

---8<---

   When you've finished editing that buffer, type `C-x #'
(`server-edit').  This saves the file and sends a message back to the
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    -> This asks if you want to save the file, and if you do, sends...

`emacsclient' program telling it to exit.  The programs that use
`EDITOR' wait for the "editor" (actually, `emacsclient') to exit.  `C-x
#' also checks for other pending external requests to edit various
files, and selects the next such file.

   You can switch to a server buffer manually if you wish; you don't
have to arrive at it with `C-x #'.  But `C-x #' is the way to say that
you are finished with one.

   Finishing with a server buffer also kills the buffer, unless it
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
already existed in the Emacs session before the server asked to create
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
it.  However, if you set `server-kill-new-buffers' to `nil', then a
^^^

    -> Finishing with a server buffer switches to another buffer, but
    -> does not kill it.

different criterion is used: finishing with a server buffer kills it if
the file name matches the regular expression `server-temp-file-regexp'.
This is set up to distinguish certain "temporary" files.

---8<---

I also checked the value of server-kill-new-buffers, and it is 't',
which seems to be the default.  I would like to see unconditional save
and kill on 'C-x #', as per the docs, instead of the current behavior.
It gets really annoying to have to manually kill 20-30 cvs* files per
day.

In general, I'm happy with Emacs 21.

Tom Lofgren
-- 
T. Lofgren <address@hidden>: Wherever I lay my .emacs, that's my ${HOME}
These opinions are mine, not yours.  Get your own damn opinions.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]