[TC 11.00b1] Unexpected result using cm_CopyPathOfFilesToClip

[petermad]

When using cm_CopyPathOfFilesToClip in A Search result Fed to listbox and folders are marked - those foldernames as copied as the parent folder followed by two backslashes - Expected result is to copy the full path of the marked folders.

See https://tcmd.madsenworld.dk/CopyPathOfFilesToClip.png

[ghisler(Author)]

I agree that the 2 backslashes are wrong. But are you sure about including the last directory name? When you use the function on a directory in normal view, it doesn't copy the directory name itself.

[petermad]

When you use the function on a directory in normal view

There is no reason to use this function in normal view - it will just consist of lines with the same directory. The function is handy for Bracch view and Search results though ,and therefore I think it should save the whole path of marked directories.

Imagine if I had searched for only directories and want a list of the search result, then I would be interested in the full paths.

[Flint]

But for full results you can use cm_CopyFullNamesToClip. Why have the new command if it just duplicates an existing one?

[petermad]

Why have the new command if it just duplicates an existing one?

If I in a Search result mark both some folders and some files, then the cm_CopyPathOfFilesToClip should give me the folders only for all entries, whereas cm_CopyFullNamesToClip will include the file name for the files.

[Flint]

2petermad
Exactly. It does what its description says: copies a path to the directory where the found item is located (be this item a file, or a subdirectory).
That's why I don't see how you propose to change its behavior. If you want it to copy full path including the item itself, then it will be the same as cm_CopyFullNamesToClip, why do you need a new cm_CopyPathOfFilesToClip for that?

Or do you want the command to copy only parent paths for files, but full paths for subdirs? I expect that would be really confusing.

[petermad]

Or do you want the command to copy only parent paths for files, but full paths for subdirs? I expect that would be really confusing.

Actuall that is what i do, but even if it doesn't at least the double backslashes for dir entries should be fixed.

[TychoBarfy]

BTW, if I searched for files with certain extensions (e.g. *.mp3) in an unlimited depth of sub directories, I possibly get a huge amount of results.
If i select all - to make it quick - and use this command, it should eliminate duplicates of paths before creating the clipboard contents.

[Fla$her]

2TychoBarfy >>>

Will it copy both paths to the clipboard? And if yes, will it copy the same path just once, or as many times as there are selected files in that path?

All paths will be copied. But it will be great, of course, if you also make an option without matches.

2petermad
You want to distort the results of the requested DC analog. This is not good.
To avoid discrepancies, it was worth changing the name to cm_CopyParentPathOfItemsToClip.

[petermad]

05.05.23 Fixed: cm_CopyPathOfFilesToClip appended 2 backslashes to parent directories of folders in search results (32/64)

Confirmed fixed in TC 11.00b2

I still think the whole path should be copied when used for a directory in the Search result panel.

[Horst.Epp]

I still think the whole path should be copied when used for a directory in the Search result panel.

I fully agree.
With the full path for dirs only it would be more usefull.
Why is there a difference in the result compared to a list with files.
Only the name may be a little bit misleading.

[ghisler(Author)]

Well, the command name cm_CopyPathOfFilesToClip is ambiguous, it does not say anything about the path of folders.
Maybe I should really rename it to cm_CopyParentPathOfItemsToClip as suggested above? Or add another command where one copies the full path of folders, and the other the folders themselves?

[petermad]

How about calling the command cm_CopyPathsToClip and then let it copy the full path of folders as Horst.Epp and I suggest.

[Fla$her]

Maybe I should really rename it to cm_CopyParentPathOfItemsToClip as suggested above? Or add another command where one copies the full path of folders, and the other the folders themselves?

We already have cm_CopyFullNamesToClip, which copies the paths to the selected folders and files. Why do we need another command that does the same with folders? Rename will be the right decision.