Find in Files fails to work correct if search directory path is too long

Find in Files fails to work correct if search directory path is too long

7
NewbieNewbie
7

    Aug 12, 2021#1

    Hi,

    I have found a bug of UltraEdit's Find in Files feature. When the search directory is long, then UltraEdit will not find some results. If the directory is too long, then UltraEdit will always return 0 results even if there are many matches.

    6,605547
    Grand MasterGrand Master
    6,605547

      Aug 13, 2021#2

      Please report bugs by email or technical support form to IDM support with version of UltraEdit as it is shown in the About window (select and copy the version information with Ctrl+C), version of Windows (as displayed on running winver.exe) and of course the fully qualified file names (file names with full path) with an example line in one of the files not found by UltraEdit and the used Find in Files options and the search string. The type of the file system (NTFS, FAT32, ...) could be also important in this case.

      Posting such a statement here in the user to user forum has no effect on future versions of UltraEdit.

      PS: Are you aware of the maximum path length limitation (MAX_PATH ) of Windows and many Windows libraries and executables? MAX_PATH is defined with 260 and is the maximum length of a file name with full path with the string terminating null byte. Maximum file name length is 256 characters + drive letter + colon + backslash + string terminating null byte = 260 characters. Files stored in a subdirectory must have a shorter file name to fit into a character array of MAX_PATH length. It is of course possible to code nowadays a Windows application for supporting fully qualified file names with up to 32767 characters using \\?\ to bypass the Windows file management as described by Microsoft on documentation page about Naming Files, Paths, and Namespaces. But it is nevertheless advisable for every Windows user to avoid a directory structure and file names on which the fully qualified file name becomes longer than 259 characters.

      PPS: What do you think how many screens are necessary to output completely visible an error message or a success message with a fully qualified file name having really the maximum length of 32767 characters?
      Best regards from an UC/UE/UES for Windows user from Austria