long-filenames

I want to make a tool that takes some filenames as parameters, but when I use this code: ARGV.each do|a| puts "Argument: #{a}" end and I use drag and drop or "send to" in Windows, I get the short filename. So a file like "C:\Ruby193\bin\test\New Text Document.txt" becomes C:\Ruby193\bin\test\NEWTEX~1.TXT as the argument. There is no problem when I run the script from the commandline, with the longfilenames as parameters. How do i get the long filename when i use drag and drop or send to? AShelly I don't know if it is possible to change the argument you recieve on a drag and drop, but you could

I have part of a build process that creates a hideously long paths in Windows. It's not my fault. It's several directories deep, and none of the directory names are abnormally long; they're just long and numerous enough to make it over MAX_PATH (260 chars). I'm not using anything other than ASCII in these names. The big problem is that the blow-up happens deep in the guts of Module::Build during the dist target, although I figure the build system doesn't matter because they'd make the same directories. Creating one of these overly-long directories with File::Path fails: use File::Path qw( make

I am trying to convert a long filename to a short filename (8.3) on Windows. A batch-file with a command line argument works as intended: short.bat : @echo OFF echo %~s1 calling short.bat C:\Documents and Settings\User\NTUSER.DAT returns C:\DOCUM~1\USER\NTUSER.DAT However, I don't like having an extra .bat-file for this. I would rather call cmd.exe with the whole command from a ruby script. How can I do this? As an intermediate step I tried to hardcode the path in the batch-file, but that does not work: short1.bat : @echo OFF SET filename="C:\Documents and Settings\User\NTUSER.DAT" echo

Can someone please tell us/me if the MAX_PATH issue still exists in (the technical preview of) Windows 10. And if it exists: How many characters can a path and an individual file name have? magicandre1981 The issue will be always present in Windows, to keep compatibility with old software. Use the NT-style name syntax "\\?\D:\very long path" to workaround this issue. In Windows 10 (Version 1607 - Anniversary Update) and Windows Server 2016 you seem to have an option to ignore the MAX_PATH issue by overriding a group policy entry enable NTFS long paths under Computer Configuration -> Admin

private string[] ColeccionDeCortes(string Path) { DirectoryInfo X = new DirectoryInfo(Path); FileInfo[] listaDeArchivos = X.GetFiles(); string[] Coleccion; foreach (FileInfo FI in listaDeArchivos) { //Add the FI.Name to the Coleccion[] array, } return Coleccion; } I'd like to convert the FI.Name to a string and then add it to my array. How can I do this? You can't add items to an array, since it has fixed length, what you're looking for is a List<string> , which can later be turned to an array using list.ToArray() . Alternatively, you can resize the array. Array.Resize(ref array, array.Length