unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 11298@debbugs.gnu.org, 'Jambunathan K' <kjambunathan@gmail.com>
Subject: bug#11298: 24.0.95; (WISH) Re-look scratch buffers
Date: Tue, 24 Apr 2012 06:42:36 -0700	[thread overview]
Message-ID: <A3CF45763951405BA14F0AD396AB0823@us.oracle.com> (raw)
In-Reply-To: <jwvty09nc38.fsf-monnier+emacs@gnu.org>

> > But I don't see any `C-x b' scenario that leads to 
> > confirmation being required, if the option has the
> > default value of `after-completion'.
> 
>    % emacs23 -Q
>    C-x b foo TAB RET
> Asks for confirmation here.

Yes, in Emacs 23.3, it does act as you describe:

In GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600)
 of 2011-03-10 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.5) --no-opt --cflags
-Ic:/imagesupport/include'

But it does not here (Emacs 24 latest build, `emacs -Q'):

In GNU Emacs 24.1.50.1 (i386-mingw-nt5.1.2600)
 of 2012-04-23 on MARVIN
Bzr revision: 108006
agustin.martin@hispalinux.es-20120423103325-xmra3329elgzhmpc
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.6) --no-opt --enable-checking --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include
 -ID:/devel/emacs/libs/libiconv-1.13.1-1-dev/include
 -ID:/devel/emacs/libs/libxml2-2.7.8/include/libxml2'







  reply	other threads:[~2012-04-24 13:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 15:55 bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K
2012-04-21 19:53 ` Stefan Monnier
2012-04-21 20:50   ` Jambunathan K
2012-04-22 14:11     ` Richard Stallman
2012-04-24 10:21       ` Jambunathan K
2012-04-23 19:39     ` Stefan Monnier
2012-04-23 20:09       ` Lennart Borgman
2012-04-23 20:11       ` Drew Adams
2012-04-24  1:39         ` Stefan Monnier
2012-04-24 13:42           ` Drew Adams [this message]
2012-04-24 10:57 ` bug#11298: Recipe to surface *code-conversion-work* buffer Jambunathan K
2012-04-24 11:39   ` martin rudalics
2012-04-24 12:54     ` Jambunathan K
2012-04-24 12:20 ` bug#11298: Scratch buffer (Summary of Xah's proposals, as I see it) Jambunathan K
2012-04-24 12:31   ` Jambunathan K
2012-04-24 13:48   ` martin rudalics
2012-04-24 16:33     ` Jambunathan K
2012-04-24 14:17   ` Jan D.
2012-04-24 16:26     ` Jambunathan K
2012-04-25 12:33       ` Jan D.
2012-04-24 18:42   ` Stefan Monnier
2013-11-15  5:06 ` bug#11298: 24.0.95; (WISH) Re-look scratch buffers Jambunathan K

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=A3CF45763951405BA14F0AD396AB0823@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=11298@debbugs.gnu.org \
    --cc=kjambunathan@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).