unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: LynX <_LynX@bk.ru>
To: 10284@debbugs.gnu.org
Subject: bug#10284: "Renaming: permission denied" file-error in Windows
Date: Fri, 06 Jan 2012 22:46:00 +0200	[thread overview]
Message-ID: <4F075D88.8030901@bk.ru> (raw)
In-Reply-To: <837h1dtewd.fsf@gnu.org>

Dear Eli,

> Thanks.  But "UNC" doesn't mean "Unicode", it means "Universal Naming
> Convention", and refers to the \\server\share\foo style of file names
> on remote machines.

Sorry now I got it :)

Today I tested it and it worked fine. I was able to move non-empty 
directory to remote shared directory (\\remote_host\shared) and then 
moved it back successfuly.

Regards,
LX





  reply	other threads:[~2012-01-06 20:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4EE3F66D.2050003@bk.ru>
     [not found] ` <83vcpnllo3.fsf@gnu.org>
     [not found]   ` <4EE46AA1.9010700@cs.ucla.edu>
     [not found]     ` <E1RZisW-0000Ok-0C@fencepost.gnu.org>
     [not found]       ` <4EE504C3.3090701@bk.ru>
     [not found]         ` <83obvfkmt6.fsf@gnu.org>
     [not found]           ` <4EE5245E.3090803@bk.ru>
     [not found]             ` <83liqilrs0.fsf@gnu.org>
     [not found]               ` <4EF6D1CE.7020101@bk.ru>
2011-12-25  9:39                 ` bug#10284: "Renaming: permission denied" file-error in Windows Eli Zaretskii
     [not found]                 ` <E1RekZY-0003jE-FO@fencepost.gnu.org>
2011-12-28 19:53                   ` LynX
2011-12-29  6:18                     ` Eli Zaretskii
2011-12-30 19:31                       ` LynX
2011-12-30 20:23                         ` Eli Zaretskii
2011-12-30 21:35                           ` LynX
2011-12-31  6:48                             ` Eli Zaretskii
2012-01-06 20:46                               ` LynX [this message]
2012-01-07  9:54                                 ` 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=4F075D88.8030901@bk.ru \
    --to=_lynx@bk.ru \
    --cc=10284@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).