From: Lars Ingebrigtsen <larsi@gnus.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 739593d 3/5: Make gnus-copy-file act like copy-file etc.
Date: Wed, 13 Sep 2017 21:33:18 +0200 [thread overview]
Message-ID: <87o9qecs1t.fsf@mouse.gnus.org> (raw)
In-Reply-To: <b4mr2vc3k1x.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 12 Sep 2017 08:14:02 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> * etc/NEWS: Mention this.
>> * lisp/gnus/gnus-util.el (gnus-copy-file): Treat the destination
>> as special only if it is a directory name.
>
> Er, isn't it necessary to make `copy-file' allow a destination
> directory for the second argument NEWNAME?
>
> M-x gnus-copy-file RET ~/foo RET /tmp RET
> => File already exists: /tmp
Breaking this ages-old (and convenient) behaviour doesn't seem like a
good idea to me either.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2017-09-13 19:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170911053128.28763.28434@vcs0.savannah.gnu.org>
[not found] ` <20170911053130.C5F002068F@vcs0.savannah.gnu.org>
2017-09-11 23:14 ` master 739593d 3/5: Make gnus-copy-file act like copy-file etc Katsumi Yamaoka
2017-09-12 2:12 ` Ken Brown
2017-09-12 2:33 ` Katsumi Yamaoka
2017-09-12 19:22 ` Paul Eggert
2017-09-14 4:17 ` Stefan Monnier
2017-09-14 16:54 ` Eli Zaretskii
2017-09-14 17:59 ` Paul Eggert
2017-09-14 18:38 ` Eli Zaretskii
2017-09-15 4:04 ` Paul Eggert
2017-09-15 9:16 ` Eli Zaretskii
2017-09-12 2:42 ` Eli Zaretskii
2017-09-13 19:33 ` Lars Ingebrigtsen [this message]
2017-09-13 20:07 ` Paul Eggert
2017-09-13 20:11 ` Lars Ingebrigtsen
2017-09-13 20:41 ` Paul Eggert
2017-09-13 21:10 ` Lars Ingebrigtsen
2017-09-13 23:32 ` Paul Eggert
2017-09-14 11:25 ` Lars Ingebrigtsen
2017-09-14 2:35 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o9qecs1t.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=yamaoka@jpl.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 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.