Creating Shortcuts with Original Extension

English support forum

Moderators: sheep, Hacker, Stefan2, white

AlecRoth
Junior Member
Junior Member
Posts: 14
Joined: 2004-03-06, 08:45 UTC

Creating Shortcuts with Original Extension

Post by *AlecRoth » 2004-03-06, 08:52 UTC

How can I use the Create Shortcut action Total Commander to create a .lnk that contains the original file's extension. When I create and extension to, say, a file called "Document.wpd", the extension file name is "Document.lnk". I would like it to be "Document.wpd.lnk". Is this possible?

User avatar
Clo
Moderator
Moderator
Posts: 5731
Joined: 2003-12-02, 19:01 UTC
Location: Bordeaux, France
Contact:

?????

Post by *Clo » 2004-03-06, 09:17 UTC

2AlecRoth
:)   Hello !
• You can always rename the *.LNK file like you wish, but I doubt it works later...
• I don't know your goal at this; however, if you want to launch the file with the right program, it's simpler and more secure to associate it with that program: "Files" menu >>> Associate with... Then follow the dialog-boxes.
• Hence, you'll can launch the file then with a double-click on it, and/or install the program with an icon in the button-bar.
• In that case, you have just to carry the file on this program-icon via Drag & Drop. Isn't necessary to associate the file with it before…
¤ Hoping that'll help you,
:mrgreen:  Kind regards,
Claude
Clo
#31505 Traducteur Français de TC French translator Aide en Français Tutoriels Français English Tutorials

icfu
Power Member
Power Member
Posts: 6052
Joined: 2003-09-10, 18:33 UTC

Post by *icfu » 2004-03-06, 14:49 UTC

I like TC's behaviour when creating links to executable files sometimes. But it's annoying on all non exectuables that's why I still use explorer method for creating links.

Would be great if a checkbox "keep extension" would be added to link creation box or some switch in wincmd.ini.

@Clo:
You can always rename the *.LNK file like you wish, but I doubt it works later...
Only thing that matters is the extension behind the last dot. If it is "lnk" it is a link, otherwise it is not.

Icfu

User avatar
Clo
Moderator
Moderator
Posts: 5731
Joined: 2003-12-02, 19:01 UTC
Location: Bordeaux, France
Contact:

For Desktop---

Post by *Clo » 2004-03-06, 15:00 UTC

2icfu
:)   Hi Jeff,
• Thanks for the info... I'm not a LNK-maniac. In fact, I use them only to install programs quickly in Win extra-tool-bars on my Desktop.
- For the rest, I do like I explained to AlecRoth; maybe the old habits from Win 3.1 ?

:mrgreen:  Kind regards,
Claude
Clo
#31505 Traducteur Français de TC French translator Aide en Français Tutoriels Français English Tutorials

User avatar
ghisler(Author)
Site Admin
Site Admin
Posts: 38451
Joined: 2003-02-04, 09:46 UTC
Location: Switzerland
Contact:

Post by *ghisler(Author) » 2004-03-09, 17:48 UTC

When you create multiple links at the same time, change the proposed *.LNK to *.*.LNK , then it will include also the original extension.
Author of Total Commander
http://www.ghisler.com

icfu
Power Member
Power Member
Posts: 6052
Joined: 2003-09-10, 18:33 UTC

Post by *icfu » 2004-03-09, 21:57 UTC

Too much work, sorry.
Explorer method (mark all files, right click, create link) is faster. I see no reason why extension gets dropped when creating links and regarding your answer you won't add it to wishlist? Well, I'm used to it. ;)

Icfu

AlecRoth
Junior Member
Junior Member
Posts: 14
Joined: 2004-03-06, 08:45 UTC

Post by *AlecRoth » 2004-03-11, 10:59 UTC

Thanks for the *.* trick.

Like icfu, I feel it would be nice if there were a way to make this automatic (optionally), so I don't have to change the entry in the dialog box when creating a shortcut. What I had been doing was typing *.EXT.LNK where EXT is the extension I want to keep. *.* saves me typing and now I can do multiple extensions.

The reason for keeping the extension is in those cases where filename is the same but the extensions are different. On my system, this happens quite a bit. Leaving off the extension is not an option for me.

IGL
Member
Member
Posts: 179
Joined: 2004-02-26, 10:47 UTC
Location: Poland

Post by *IGL » 2004-03-11, 12:14 UTC

I do see a reason for keeping extension in links (Filename.ext.lnk), eg.
when you have the same filename with various extensions, when you want to now more precisely what does the lnk point to and more. But I do not see any practical reason for replacing extension with lnk. ANd adding another * manually is uncomortable.
Mr Ghisler please, spare us that action, make us free of this or give us an option to make filename.ext.lnk.
:-)

User avatar
Black Dog
Power Member
Power Member
Posts: 1024
Joined: 2003-02-05, 22:17 UTC
Location: Odessa
Contact:

Post by *Black Dog » 2004-03-13, 00:21 UTC

[face=courier]On 11-03-2004 14:14:47 +0000 IGL wrote:

I> I do see a reason for keeping extension in links
I> (Filename.ext.lnk), eg.


Well, I don't - as for me additional "extension" in shortcut name is useless and I always avoid of using the dot as a part of file name, so I guess Commander present day behavior is absolutely right.[/face]

icfu
Power Member
Power Member
Posts: 6052
Joined: 2003-09-10, 18:33 UTC

Post by *icfu » 2004-03-13, 00:54 UTC

Links to song.jpg and song.mp3 have the same filename. You can't even create them at the same time because of that, makes no sense.

Dropping the file extension leads to superfluous renaming considerations.

Anyway, an optional "keepextension" setting in ini will satisfy both needs, no reason to be against that feature.

Icfu

User avatar
Lefteous
Power Member
Power Member
Posts: 9458
Joined: 2003-02-09, 01:18 UTC
Location: Germany
Contact:

Post by *Lefteous » 2004-03-13, 07:25 UTC

From my point of view the current behavior should be changed to filenames that include the original extension. This should be the default behavior.
An option to create shortcuts without original extension could be included, but is not a must.

jb
Senior Member
Senior Member
Posts: 402
Joined: 2003-02-09, 22:56 UTC
Location: Switzerland

Post by *jb » 2004-03-13, 13:03 UTC

Lefteous wrote:From my point of view the current behavior should be changed to filenames that include the original extension. This should be the default behavior.
An option to create shortcuts without original extension could be included, but is not a must.
I totally agree. Preserving the original file/directory name entirely by default is actually a must, while replacing the extension (current behaviour) is rather a dispensable option.
There is one more argument against the latter: Even if TC 6.02 creates a shortcut to a directory such as "IrfanViewV3.85" then annoyingly you get "IrfanViewV3.lnk". That is, you get an incomplete shortcut name, although with directories an extension clearly belongs to the name, because unlike with files the extension of a directory can NOT be used to associate the directory with a program.

User avatar
karlchen
Power Member
Power Member
Posts: 4557
Joined: 2003-02-06, 22:23 UTC
Location: Germany

Post by *karlchen » 2004-03-13, 13:44 UTC

Hello to all.

I would like to support all those wishing that the default behaviour should be changed to include the filename extension in the linkfilename.
I noticed that more often than not I would like to keep the original filename extension. I do not see any sense in hiding part of a filename from myself (or any other user.)

So, please, Christian, put on your wish list for the next version of TC:
When creating links make the default action to keep the original filename extension.
Or, please, add a configurable wincmd.ini setting which allows each user to choose his/her favourite default behaviour. (This should satisfy all.)

Regards,
Karl
Last edited by karlchen on 2004-03-14, 19:56 UTC, edited 1 time in total.
Linux Mint 19.2 32-bit xfce Desktop, Total Commander 9.22a 32-bit
Haß gleicht einer Krankheit, dem Miserere, wo man vorne herausgibt, was eigentlich hinten wegsollte. (Goethe)

User avatar
Sticky
Junior Member
Junior Member
Posts: 76
Joined: 2004-03-11, 23:29 UTC
Location: Denver, CO, USA

Post by *Sticky » 2004-03-13, 20:42 UTC

What is all this talk about the default action? An OPTION is what you need! It's whacky to switch stuff up on the users for no reason.
A nice check box next to "Copy NTFS permissions" would be ideal. Somewhere that can easily be changed 'on the fly'. But, even if it's that easy to change, it still shouldn't be "default". Why change things up unecessarily for the users who are currently satisfied--like me and black dog? We shouldn't have to do any extra work for your option; that's your job. But what do I know, this is only my fourth post... :-)

User avatar
Black Dog
Power Member
Power Member
Posts: 1024
Joined: 2003-02-05, 22:17 UTC
Location: Odessa
Contact:

Post by *Black Dog » 2004-03-13, 20:46 UTC

[face=courier]On 13-03-2004 02:54:09 +0000 icfu wrote:

i> Anyway, an optional "keepextension" setting in ini will
i> satisfy both needs, no reason to be against that feature.


I'm not against, just can't see the reason to change something - it's OK for me like it is now.[/face]

Post Reply