all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 26243@debbugs.gnu.org
Subject: bug#26243: 25.1; `dired-pop-to-buffer' warning
Date: Fri, 26 Jul 2019 13:13:15 +0200	[thread overview]
Message-ID: <87y30lm4l0.fsf@mouse.gnus.org> (raw)
In-Reply-To: <1355208c-862e-4c1e-8218-a2efdf66142c@default> (Drew Adams's message of "Fri, 24 Mar 2017 11:21:06 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> If code uses function `dired-pop-to-buffer', this is the byte-compiler
> warning you get:
>
> `dired-pop-to-buffer' is an obsolete function (as of 24.3);
> use `dired-mark-pop-up' instead.
>     ^^^^^^^^^^^^^^^^^^^
>
> That is a ridiculous warning.  `dired-mark-pop-up' is about acting on
> each of the marked files and directories.  `dired-pop-to-buffer' pops
> up a single buffer.
>
> There is zero connection between `dired-mark-pop-up' and
> `dired-pop-to-buffer'.

Those functions seem to have little to do with each other; yes.  So I've
now removed the reference.

It was added with a reference to bug 1806, which is a 170 message long
thread which I've not read.  I've Cc'd Juri (who made the change) in
case the reference makes sense anyway, in which case I'll revert my
change.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-07-26 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 18:21 bug#26243: 25.1; `dired-pop-to-buffer' warning Drew Adams
2019-07-26 11:13 ` Lars Ingebrigtsen [this message]
2019-07-29 15:16   ` martin rudalics
2019-07-29 22:41     ` Juri Linkov
2019-07-30  0:53       ` Drew Adams
2019-07-30 11:35       ` Lars Ingebrigtsen
2019-07-30 19:08         ` Drew Adams

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=87y30lm4l0.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=26243@debbugs.gnu.org \
    --cc=drew.adams@oracle.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.