From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, 27959@debbugs.gnu.org
Subject: bug#27959: 26.0.50; File renaming fails on sshfs
Date: Sat, 05 Aug 2017 08:24:41 +0000 [thread overview]
Message-ID: <CAArVCkQVAutLXH21S_HB4gw0-+Zav+Ekp8vXatNrCXD9N0kf_g@mail.gmail.com> (raw)
In-Reply-To: <87o9rv6mk9.fsf@amy>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> schrieb am Fr., 4. Aug. 2017 um
23:39 Uhr:
>
> /tv is mounted via sshfs.
>
> (rename-file "/tv/a.foo" "/tv/b.foo")
>
> Debugger entered--Lisp error: (file-error "Renaming" "Invalid argument"
> "/tv/a.foo" "/tv/b.foo")
> rename-file("/tv/a.foo" "/tv/b.foo")
> eval((rename-file "/tv/a.foo" "/tv/b.foo") nil)
> eval-expression((rename-file "/tv/a.foo" "/tv/b.foo") nil nil 127)
> funcall-interactively(eval-expression (rename-file "/tv/a.foo"
> "/tv/b.foo") nil nil 127)
> call-interactively(eval-expression nil nil)
> command-execute(eval-expression)
>
> But if I say
>
> larsi@amy:~$ mv /tv/a.foo /tv/b.foo
>
> on the same machine, it works fine. So ... where is the "Invalid
> argument" coming from?
>
Probably more fallout of 1f9f514e7c2ba41b0954d0141f99652f6a53a107. Does it
work if you compile without that commit (e.g. git reset --hard
1f9f514e7c2ba41b0954d0141f99652f6a53a107^ from a clean working directory)?
[-- Attachment #2: Type: text/html, Size: 1449 bytes --]
next prev parent reply other threads:[~2017-08-05 8:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 21:38 bug#27959: 26.0.50; File renaming fails on sshfs Lars Ingebrigtsen
2017-08-05 8:24 ` Philipp Stephani [this message]
2017-08-05 9:24 ` Lars Ingebrigtsen
2017-08-05 18:51 ` Lars Ingebrigtsen
2017-08-05 20:59 ` Paul Eggert
2017-08-05 21:09 ` Lars Ingebrigtsen
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=CAArVCkQVAutLXH21S_HB4gw0-+Zav+Ekp8vXatNrCXD9N0kf_g@mail.gmail.com \
--to=p.stephani2@gmail.com \
--cc=27959@debbugs.gnu.org \
--cc=larsi@gnus.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.