Skip to main content

files and directories - Path Names Longer Than 256 on Windows


Is there a way to work with pathnames that are longer than the typical 256 in Mathematica?


For example run the following in Cygwin


echo 1 > 034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890

Then run


FilePrint["034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890"]



General::noopen: Cannot open ...




Answer



With a few rare exceptions, Mathematica is generally unable to work with long path names on Windows. This response presents two strategies to work around this difficulty: extended-length path syntax and short path names (documented in Naming Files, Paths, and Namespaces from the Windows Dev Center).


Let's start with a big file name:


$big = "034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890345678903456789034567890";

Extended-length Path Syntax


The Windows echo command cannot handle this big name:



Run["cmd /c echo hello >", $big]
(* 1 *)   (* i.e. "error" *)

It can, however, handle extended-length path syntax (in recent versions of Windows). This entails tacking the prefix \\?\ onto the front of an absolute pathname. We will use some helper functions:


$longPrefix = "\\\\?\\";

toLongPath[filename_] := $longPrefix <> ExpandFileName[filename]

fromLongPath[filename_] := StringReplace[filename, StartOfString~~$longPrefix -> ""]


Usage:


toLongPath[$big]
(* \\?\C:\Users\wreach\Documents\03456789...9034567890 *)

fromLongPath[%]
(* C:\Users\wreach\Documents\03456789...9034567890 *)

The Windows echo command accepts this syntax:


Run["cmd /c echo hello >", toLongPath[$big]]
(* 0 *)   (* i.e. "success" *)


FirstCase[FileNames[], n_ /; StringLength[n] > 200]
(* "03456789034567890345...789034567890" *)

The Mathematica CopyFile function will also accept this syntax:


CopyFile[toLongPath[$big], "zot"];
FilePrint["zot"]
(* hello *)

DeleteFile["zot"]


Short Path Names


Unfortunately, FilePrint does not support extended-length path syntax:


FilePrint[toLongPath[$big]]
(* Cannot open \\?\C:\Users\wreach\Documents\03456...890. >> *)

We will switch to the second strategy: short path names. These are alternative names that Windows provides for use by DOS-like components (read: most of the Windows ecosystem). We can view short path names for files by using the Windows dir /x command:


Import["!cmd /c dir /x 03456*", "Text"]

(* ...

   Directory of C:\Users\wreach\Documents
   ...
   2015-10-24  14:33     8    034567~1     034567890...3456789034567890
   ...
*)

The directory listing shows us that the short file name for $big is 034567~1.


FilePrint["034567~1"]
(* hello *)


It would be nice to obtain such names programmatically. Alas, Mathematica does not have a built-in function to obtain short file names. We will use NETLink to call the Win32 API function GetShortPathName:


Needs["NETLink`"]
InstallNET[];

getLastError = DefineDLLFunction["GetLastError", "kernel32.dll", "DWORD", {}];

getShortPathNameW =
  DefineDLLFunction["GetShortPathNameW"
  , "kernel32.dll", "DWORD", {"LPCTSTR", "System.Text.StringBuilder", "DWORD"}
  , MarshalStringsAs -> "Unicode"

  ];

shortPath[name_String] :=
  NETBlock @ Module[{result = NETNew["System.Text.StringBuilder", 260]}
  , getShortPathNameW[toLongPath@name, result, result@Capacity]
  ; getLastError[] /. 0 :> fromLongPath@result@ToString[]
  ]

Here is our helper function in action:


shortPath[$big]

(* C:\Users\wreach\DOCUME~1\034567~1 *)

This short path can be used everywhere in Mathematica, including FilePrint:


FilePrint[shortPath[$big]]
(* hello *)

Such short paths can also be used by all of the components that support Mathematica, whether they be DLLs, Java, command line tools or anything else.


Note that short paths can only be obtained for files that already exist. This mechanism cannot be used to create new files with big names.



Incidentally, DeleteFile is one of the few functions that accepts extended-length path syntax:



DeleteFile[toLongPath[$big]]

Comments

Post a Comment

Popular posts from this blog

functions - Get leading series expansion term?

Given a function f[x] , I would like to have a function leadingSeries that returns just the leading term in the series around x=0 . For example: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x)] x and leadingSeries[(1/x + 2 + (1 - 1/x^3)/4)/(4 + x)] -(1/(16 x^3)) Is there such a function in Mathematica? Or maybe one can implement it efficiently? EDIT I finally went with the following implementation, based on Carl Woll 's answer: lds[ex_,x_]:=( (ex/.x->(x+O[x]^2))/.SeriesData[U_,Z_,L_List,Mi_,Ma_,De_]:>SeriesData[U,Z,{L[[1]]},Mi,Mi+1,De]//Quiet//Normal) The advantage is, that this one also properly works with functions whose leading term is a constant: lds[Exp[x],x] 1 Answer Update 1 Updated to eliminate SeriesData and to not return additional terms Perhaps you could use: leadingSeries[expr_, x_] := Normal[expr /. x->(x+O[x]^2) /. a_List :> Take[a, 1]] Then for your examples: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x), x] leadingSeries[Exp[x], x] leadingSeries[(1/x + 2 + (1 - 1/x...
Post a Comment
Read more

mathematical optimization - Minimizing using indices, error: Part::pkspec1: The expression cannot be used as a part specification

I want to use Minimize where the variables to minimize are indices pointing into an array. Here a MWE that hopefully shows what my problem is. vars = u@# & /@ Range[3]; cons = Flatten@ { Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; Minimize[{Total@((vec1[[#]] - vec2[[u[#]]])^2 & /@ Range[1, 3]), cons}, vars, Integers] The error I get: Part::pkspec1: The expression u[1] cannot be used as a part specification. >> Answer Ok, it seems that one can get around Mathematica trying to evaluate vec2[[u[1]]] too early by using the function Indexed[vec2,u[1]] . The working MWE would then look like the following: vars = u@# & /@ Range[3]; cons = Flatten@{ Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; NMinimize[ {Total@((vec1[[#]] - Indexed[vec2, u[#]])^2 & /@ R...
Post a Comment
Read more

plotting - Plot 4D data with color as 4th dimension

I have a list of 4D data (x position, y position, amplitude, wavelength). I want to plot x, y, and amplitude on a 3D plot and have the color of the points correspond to the wavelength. I have seen many examples using functions to define color but my wavelength cannot be expressed by an analytic function. Is there a simple way to do this? Answer Here a another possible way to visualize 4D data: data = Flatten[Table[{x, y, x^2 + y^2, Sin[x - y]}, {x, -Pi, Pi,Pi/10}, {y,-Pi,Pi, Pi/10}], 1]; You can use the function Point along with VertexColors . Now the points are places using the first three elements and the color is determined by the fourth. In this case I used Hue, but you can use whatever you prefer. Graphics3D[ Point[data[[All, 1 ;; 3]], VertexColors -> Hue /@ data[[All, 4]]], Axes -> True, BoxRatios -> {1, 1, 1/GoldenRatio}]
Post a Comment
Read more