LinkInfo plugin works in Lister but not in QuickView

[fm-xvid]

I am using a plugin, LinkInfo, which only works in Lister (F3) but not in QuickView (Ctrl+Q).

Is there a way to fix this? Here are the entries from the [ListerPlugins] section

Code: Select all

[ListerPlugins]
0=%COMMANDER_PATH%\plugins\wlx\slister\slister.wlx
0_detect="MULTIMEDIA & (EXT="PDF" | EXT="EPUB" | EXT="MOBI" | EXT="AZW")"
1=%COMMANDER_PATH%\plugins\wlx\LinkInfo\LinkInfo.wlx64
1_detect="MULTIMEDIA & (force | EXT="LNK")"
2=%COMMANDER_PATH%\Plugins\wlx\mmedia\mmedia.wlx64
2_detect="MULTIMEDIA"
3=%COMMANDER_PATH%\plugins\wlx\AKFont\AKFont.wlx
3_detect="FORCE | EXT="TTF" | EXT="PFM" | EXT="OTF" | EXT="TTC" | EXT="FON" | EXT="PFB""
4=%COMMANDER_PATH%\plugins\wlx\ICLView\ICLView.wlx
4_detect="MULTIMEDIA & (EXT="DLL" | EXT="EXE" | EXT="ICL" | EXT="ICL32" | EXT="ICO" | size=0 | force)"

Just to add, I am using Total Commander version 10.52 (64-bit) with the 64-bit plugins as well.

[Horst.Epp]

Here it also only works with F3 and not in Quick View.
I even tried to add the lnk extension to the definition by file type.

[Fla$her]

wincmd.ini:

Code: Select all

[Configuration]
QuickViewFollowLinks=0

See also this topic.

25.01.19 Added: wincmd.ini [Configuration] QuickViewFollowLinks=1: Show contents of link target on Ctrl+Q: 0=off, 1=only network paths when source is also on net, 2=always (32/64)

[Dalai]

Notice that TC QuickView opens/shows the link's target but Lister shows the link file itself? That's probably the problem (and could indicate a bug in TC).

I just tested this with several TC versions and it looks like TC 9.22a is the last one to work correctly. TC 9.50 opens the link's target while 9.22a shows the link itself.

It might help if you remove the "force |" part from the detect line, but I haven't tested this.

If this is caused by the setting Fla$her mentioned, I see a (different) bug in TC. I made my tests with local LNK files linking to local files and it still shows the link's target.

Regards
Dalai

[Fla$her]

If this is caused by the setting Fla$her mentioned

This is not a reason, but a solution. Read carefully the text from History.txt.
Or do you want to say that this happens for you when the value is 0?

[Dalai]

2Fla$her
I have read (and I think I understood) the thread you linked to. As I said above: It also happens with local LNK files linking to local resources (files in the Windows start menu). If I take the explanation for the value 1 by its word, TC shouldn't open the link's target when everything is local, but it does. Am I missing something?

Regards
Dalai

[Fla$her]

2Dalai
From TOTALCMD.CHM:

QuickViewFollowLinks=1

Show contents of link target on Ctrl+Q: 1=On network paths only when lnk is also on net, 2=Always, 0=Never

Not only on network paths. Is it clear now?
It would be more correct to write: 1=Always, but on network paths only when lnk is also on net,

[Dalai]

OK, I think I got it now. Well, if the behavior is supposed to be this way, the help text should definitely be updated to avoid such misunderstandings. And the German help isn't any better in this regard.

Regards
Dalai

[Horst.Epp]

For me even QuickViewFollowLinks=2 didn't help with Quick View.
It only works in some way after removing its detection string.
But in Quick View it then only shows some info about the target of a lnk.
So its not really usable in Quick View

[Fla$her]

2Dalai
I agree about .chm.

For me even QuickViewFollowLinks=2 didn't help with Quick View.

And it shouldn't. =2 has not been proposed as a solution.

[petermad]

Here it works fine with this in the [Lister] section:

Code: Select all

25=%COMMANDER_PATH%\PLUGINS\wlx\LinkInfo\LinkInfo.wlx
25_detect="force | (ext="LNK")"

and this in the [Configuration] section:

Code: Select all

QuickViewFollowLinks=0

https://madsenworld.dk/tcmd/LinkInfo.png

[fm-xvid]

Thanks to @Fla$her for finding the cause and the rest of you for testing the plugin.

In my wincmd.ini, there was no "QuickViewFollowLinks" so I added "QuickViewFollowLinks=0" and now it works.

[Fla$her]

I have read (and I think I understood) the thread you linked to.

I would like to make a clarification. The problem on my link was not specifically in the network connection. The problem was the inaccessibility of the path. That is, if the value is 2, LinkInfo will connect only if the path is unavailable (whether it is network or otherwise, it does not matter).

if LNK points to a special location like network connection.

It was erroneous in the description to associate the option only to a network location.

[Horst.Epp]

With QuickViewFollowLinks=0 it now works here to