Full path to the file/folder inside an archive

[petermad]

It is understandable that %P and %N has to work differently in Search reults and Branch view, since these views are not shown with a folder structure. For both views it looks as if for example %P%N will lead to the same result as in simple view - so a button or command using %P%N wil work in all three views.

But Archives do have a folder structure, so I don'r really see a need for different behaviour of the variables, exept that %P and %p has to treat the name of the archive file as a filder name.

[[Yustas.NeO]]

It is understandable that %P and %N has to work differently in Search reults and Branch view, since these views are not shown with a folder structure. For both views it looks as if for example %P%N will lead to the same result as in simple view - so a button or command using %P%N wil work in all three views.

I do not quite understand the logic... Regardless of view, the file still has its own path, name and extension!

Tell me why in SEARCH %p and %t returns different (C:\PROGRA~1\TOTALC~1\test\LONGFO~1\ and empty) and in BRANCH %p and %t returns other(!) different (C:\PROGRA~1\TOTALC~1\test\LONGFO~1\ and C:\PROGRA~1\TOTALC~1\test\). I just change the panel.

Maybe it would be better to implement new parametrs that return relative data for archives, search and branch?
%Pr=C:\Program Files\Total Commander\test\long foldername\long archivename.ZIP\
%Nr=1\long foldername in archive\3\long filename 1.extension
and for branch and search
%Pr=C:\Program Files\Total Commander\test\
%Nr=long foldername\long archivename.ZIPzip

[nsp]

Tell me why in SEARCH %p and %t returns different (C:\PROGRA~1\TOTALC~1\test\LONGFO~1\ and empty) and in BRANCH %p and %t returns other(!) different (C:\PROGRA~1\TOTALC~1\test\LONGFO~1\ and C:\PROGRA~1\TOTALC~1\test\). I just change the panel.

Maybe it would be better to implement new parametrs that return relative data for archives, search and branch?....

%P is the source PATH in normal view this is where you are, in branch view this is where you started. (Source do not mean Filename PATH)
%N is the file name (relative to start !)

As explained normally from everywhere %P%N should represent the complete filename.


if we use branch view inside an archive %Z%P%N is almost the good result but : %P is the archive and %N the relative path inside the archive (as for all %N inside archive)

When using %Z modifier, %N give wrong result in normal view and branch view, %P gives wrong result in branch view !

I personally think that the current behavior is good exept that it is buggy inside archive ( %L %S are also buggy)

%N %L and %S %P are also not coherent inside virtual panel but it is another story...

Probably Mr Ghisler should give a look here and prpose a coherent behavior when using %Z and also inside virtual panel !

[ghisler(Author)]

The parameter do not offocially support ZIP files yet - I will try to add it. I will add support for %P, %N, %T, %M and their lowercase counterparts. The list files will not be supported. The problem here is that TC stores the names with their relative path in the "name" field.

[karlchen]

Hm, sometimes it pays to read the helpfile carefully and take its content literally.

Dialog box: Configuration - Change button bar

%Z anywhere in the parameters: Allow to pass archives as path to programs for %P or %T when inside an archive
Example: %Z%P passes name of archive to external tool when TC shows contents of an archive

Only the parameteres %P and %T are mentioned.

And we assumed this would include %N and %M as well and the lower case counterparts, %p, %t, %n, %m.

Karl

[ghisler(Author)]

Regarding the different handling of branch view and search results: TC passes the path shown in the current path panel (breadcrumb bar) to %P, while it passes the name shown in the list to %N. This was necessary for the case where users defined commands with just %N in them, relying in the current path to make it work. Combined, %P%N will still represent the full path to the file. Because these parameters may be used this way by many people, I will not change it. However, I will fix the problems with names within archives.

[petermad]

Fixed in TC 8.0b23

%N, %n, %p, %P, %t, %T, %M and %m are now handled as expected inside archives.

[nsp]

Fixed in TC 8.0b23

%N, %n, %p, %P, %t, %T, %M and %m are now handled as expected inside archives.

Even %Z%L is working