From: Ian Zimmerman <bayard@newsguy.com>
Subject: server buffer killing
Date: Fri, 10 Oct 2003 09:41:40 -0700 [thread overview]
Message-ID: <E1A80Ki-0000J3-00@homage> (raw)
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.2.1 (i386-debian-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2002-03-22 on raven, modified by Debian
configured using `configure i386-debian-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --with-x=yes --with-x-toolkit=athena --without-gif'
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: nil
locale-coding-system: nil
default-enable-multibyte-characters: t
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
There seems to be a small but crucial typo in server.el which makes the documentation of
server-kill-new-buffers wrong:
If non-nil, kill a buffer unless it already existed before editing
it with Emacs server. If nil, kill only buffers as specified by
`server-temp-file-regexp'.
*** /usr/share/emacs/21.2/lisp/server.el Sun Oct 21 18:25:57 2001
--- ./server.el Fri Oct 10 09:37:25 2003
***************
*** 401,407 ****
server-kill-new-buffers
(save-excursion
(set-buffer buffer)
! server-existing-buffer))
(setq killed t)
(bury-buffer buffer)
(kill-buffer buffer))
--- 401,407 ----
server-kill-new-buffers
(save-excursion
(set-buffer buffer)
! (not server-existing-buffer)))
(setq killed t)
(bury-buffer buffer)
(kill-buffer buffer))
As it is, server buffers for non-temporary files _never_ get killed
with C-x #. Not really a big deal, as I can always kill them with C-x
k and answer the prompt, but the inconsistency with documentation is
jarring :-)
--
Wer Schoenheit angeschaut mit Augen, hat dem Tode schon Anheim gegeben.
Von Platen.
reply other threads:[~2003-10-10 16:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1A80Ki-0000J3-00@homage \
--to=bayard@newsguy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.