unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Should killing a help or compile buffer also delete the window?
Date: Mon, 25 Apr 2005 10:32:28 +0000 (UTC)	[thread overview]
Message-ID: <m1DQ0tA-0004RUC@rattlesnake.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1050424122302.530A-100000@acm.acm> (message from Alan Mackenzie on Sun, 24 Apr 2005 13:35:23 +0000 (GMT))

   I'd like C-x 4 0 to just do its job without mithering me with "kill
   buffer `foo'? (yes or no)", unless it's an actual changed buffer
   that's getting killed.

Today's GNU Emacs CVS snapshot, Mon, 2005 Apr 25  09:44 UTC
GNU Emacs 22.0.50.14 (i686-pc-linux-gnu, GTK+ Version 2.6.4)
started with

     /usr/local/src/emacs/src/emacs -Q -D

does not ask me that question in either situation, changed buffer or
not.  It just kills the buffer and the window.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  reply	other threads:[~2005-04-25 10:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-24  5:45 Should killing a help or compile buffer also delete the window? Daniel Brockman
2005-04-24 11:02 ` Robert J. Chassell
2005-04-24 13:35   ` Alan Mackenzie
2005-04-25 10:32     ` Robert J. Chassell [this message]
2005-04-24 21:22 ` Richard Stallman
2005-04-24 22:50   ` Daniel Brockman
2005-04-26 10:04     ` Richard Stallman
2005-04-25 17:20 ` Drew Adams
2005-04-25 21:38   ` Daniel Brockman
2005-04-25 17:22 ` Kevin Rodgers
2005-04-25 19:04 ` Stefan Monnier
2005-04-25 19:37   ` Daniel Brockman
2005-04-26 20:50     ` Stefan Monnier
2005-04-26 14:32   ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-04-25 13:41 David Reitter
2005-04-25 14:11 ` Daniel Brockman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1DQ0tA-0004RUC@rattlesnake.com \
    --to=bob@rattlesnake.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).