unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: 31648@debbugs.gnu.org
Subject: bug#31648: 26; (elisp) `Indirect Buffers': `clone-indirect-buffer'
Date: Tue, 29 May 2018 15:25:44 -0700 (PDT)	[thread overview]
Message-ID: <0c0705a4-6790-4267-ab5e-59519f3d9915@default> (raw)

The doc of `clone-indirect-buffer' is incorrect.  It implies that the
new, indirect buffer, is not displayed when the command is invoked
interactively.

The doc string is correct.  Please correct the manual similarly.  The
statement of the second sentence here, from the doc string is missing
from the manual:

 DISPLAY-FLAG non-nil means show the new buffer with 'pop-to-buffer'.
 This is always done when called interactively.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

(One might wonder why non-nil, instead of nil, was chosen to show the
buffer, since that's the default interactive behavior - but it's too
late now.)




In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
 of 2018-04-10
Repository revision: c267421647510319d2a70554e42f0d1c394dba0a
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install 'CFLAGS=-O2 -static -g3''





             reply	other threads:[~2018-05-29 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29 22:25 Drew Adams [this message]
2018-06-02 11:19 ` bug#31648: 26; (elisp) `Indirect Buffers': `clone-indirect-buffer' Eli Zaretskii

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=0c0705a4-6790-4267-ab5e-59519f3d9915@default \
    --to=drew.adams@oracle.com \
    --cc=31648@debbugs.gnu.org \
    /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).