From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 39057@debbugs.gnu.org
Subject: bug#39057: 27.0.60; copy-file interactive VS from lisp disagreement
Date: Fri, 10 Jan 2020 15:48:02 +0200 [thread overview]
Message-ID: <83wo9z8lt9.fsf@gnu.org> (raw)
In-Reply-To: <alpine.LSU.2.21.2001101254300.20910@dhcp154.suse.cz> (message from Tino Calancha on Fri, 10 Jan 2020 12:55:59 +0100 (CET))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Fri, 10 Jan 2020 12:55:59 +0100 (CET)
> cc: Tino Calancha <tino.calancha@gmail.com>, 39057@debbugs.gnu.org
>
> > I cannot reproduce this, so there must be more here than meets the
> > eye
> > So please step through the code and tell where it fails and why.
>
> It seems NEWNAME, i.e., the second argument seeing by `copy-file' might be different
> when called interactively; this is true even if the user introduces the
> same value.
>
> I have printed out newname before the line
> newname = expand_cp_target (file, newname);
> at src/fileio.c
>
> I)
> M-: (copy-file "/tmp/foo" "~/") RET
> ;; it shows "~/" as expected
>
> II)
> M-x: copy-file RET /tmp/foo RET ~/ RET
> ;; it shows "~" (the '/' is missing)
Why would it be missing? which code removes it, if you typed it?
> Since you cannot reproduce the issue, it might be platform dependent.
> I am able to reproduce it in this nice site, which runs Emacs 26.3 in a linux machine:
> https://repl.it/languages/elisp
I couldn't reproduce on GNU/Linux either.
> M-! touch /tmp/foo RET
> M-x copy-file RET /tmp/foo RET RET
> ;; received prompt
> ;; FILE /home/runner already exists; copy to it anyway? (yes or no)
This is a different use case.
next prev parent reply other threads:[~2020-01-10 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 21:03 bug#39057: 27.0.60; copy-file interactive VS from lisp disagreement Tino Calancha
2020-01-10 7:54 ` Eli Zaretskii
2020-01-10 11:55 ` Tino Calancha
2020-01-10 13:48 ` Eli Zaretskii [this message]
2020-01-10 14:12 ` Eli Zaretskii
2020-01-13 18:37 ` Stefan Monnier
2020-01-15 20:35 ` Stefan Monnier
2020-01-16 14:31 ` Eli Zaretskii
2020-01-16 15:20 ` Stefan Monnier
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=83wo9z8lt9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39057@debbugs.gnu.org \
--cc=tino.calancha@gmail.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).