all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 19463@debbugs.gnu.org
Subject: bug#19463: 25.0.50; Files with special chars in the name cannot be written on MS Windows
Date: Mon, 29 Dec 2014 18:37:08 +0200	[thread overview]
Message-ID: <837fxajtu3.fsf@gnu.org> (raw)
In-Reply-To: <87mw66a1q7.fsf@gmx.de>

> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Mon, 29 Dec 2014 16:56:48 +0100
> 
> 
> The following problem I have observed when running tramp-tests.el on MS
> Windows. It isn't a Tramp problem, 'tho.

It's a basic documented limitation of the file APIs, at least on the
level that Emacs on Windows uses them.  See

  http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx

(look under "Naming Conventions").

> Files with special characters in their file name cannont be written
> locally. The following test is derived from tramp-test30-special-characters.
> Note, that this testcase runs w/o problems under GNU/Linux.

This is expected.  What exactly do you want us to do with this issue?
Unless we radically change the way we do file I/O (similarly to what
Cygwin does), which is a very large job, this issue cannot be
resolved.

We simply should not use such file names on Windows.





  reply	other threads:[~2014-12-29 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 15:56 bug#19463: 25.0.50; Files with special chars in the name cannot be written on MS Windows Michael Albinus
2014-12-29 16:37 ` Eli Zaretskii [this message]
2014-12-29 21:55   ` Michael Albinus
2014-12-30  3:32     ` Eli Zaretskii
2014-12-30  8:29       ` Michael Albinus
2014-12-30 16:02         ` Eli Zaretskii
2014-12-30 17:38           ` Michael Albinus
2015-01-31 16:34             ` 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=837fxajtu3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19463@debbugs.gnu.org \
    --cc=michael.albinus@gmx.de \
    /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.