Hey @lukesampson
I installed vlc from extras bucket. The app doesn't get automatically registered with associated extensions i.e double clicking on video won't open the media player.
I recommend that manifest of vlc should have field for associated file types. And maybe when one runs scoop link it should register and override all the associated file types and make vlc as primary for instance.
Along with associated file types field, maybe shortcut for desktop or startup menu; maybe desirable. But file association is critical as is screws up after install experience.
Jaspreet
Thx
Along with associated file types field, maybe shortcut for desktop or startup menu; maybe desirable. But file association is critical as is screws up after install experience.
Creating Start Menu shortcuts is already supported (see the shortcuts property in manifest files). However, due to a bug (https://github.com/lukesampson/scoop/issues/2124), these aren't displayed in search results; they will only be visible if you manually navigate to the Scoop Apps folder in the Start Menu.
@Calinou is still valid? All programs I installed with scoop show up in the search results. They even get listed as "Recently added".
@jas99 What do you mean by "as is screws up after install experience"?
Messing with associated files is a bit much for scoop I guess. This should be handled by the user him/herself. Also, VLC has this feature in the settings menu.
@r15ch13 Well you can prompt user during installations for yes/no to associate if available in manifest. Or maybe manual scoop link vlc would associate filetypes.
Its been lil while I ran my windows machine but vlc file association didn't worked for me. So I manually linked it with open with option. I selected shim and now along with vlc I get blank cmdline window; generated by shim.
Use open with to select the vlc.exe from ~\scoop\apps\vlc\current.
Try running VLC with admin privileges and then use the settings menu to associate the filetypes. This is required in most cases (MPC-HC, 7zip)
@r15ch13 Hey thx for mentioning that; will chk it out and let you know.
But maybe these additional steps should also be in application manifest as non-default steps that requires admin elevation and run with special subcommand.
@r15ch13 Thx things work out.
@r15ch13 @jas99 I don't think this issue should be closed. If we could define file associations directly from the json manifest instead of manual steps would be a much more polished installation.
Something like the shortcuts key where you can give it a binary and a human readable name
"associate": {
".txt": [
"notepad.exe",
],
".yml": [
"notepad.exe",
]
}
or
"associate": {
"notepad.exe": [
".txt",
".yml",
".yaml"
]
}
Some users may not want this forced upon them so we can make an optional toggle
For all configured associations
scoop install tortoisesvn --with-associations
For particular associations
scoop install tortoisesvn --with-associations svn
If it's installed without the toggle
scoop install tortoisesvn
There can be a default note within it
You've just installed `tortoisesvn` and we've detected the following file associations.
.svn => tortoisesvn.exe
..etc..
If you'd like to create these associations, run the following
scoop install tortoisesvn --with-associations
or maybe
scoop assoc tortoisesvn
scoop assoc tortoisesvn .svn
The above addition should help prevent the scoop-extras bucket from having to run external reg and powershell scripts for file associations (also see https://github.com/lukesampson/scoop-extras/pull/1566)
I love nitrocode's suggestion. I managed to replace ~2 dozen installed apps last night with buckets from extra and the biggest issue I've run into is re-associating them. Manually browsing to the path gives some less than satisfactory results for example my 7zip doesn't use the big black and white icon but a document looking icon with the smaller icon in the middle.
A bit late, but I also agree with nitrocode's suggestion. I would also add an option to set the default icon and file type descriptions.
Most helpful comment
@r15ch13 @jas99 I don't think this issue should be closed. If we could define file associations directly from the json manifest instead of manual steps would be a much more polished installation.
Something like the shortcuts key where you can give it a binary and a human readable name
or
Some users may not want this forced upon them so we can make an optional toggle
For all configured associations
For particular associations
If it's installed without the toggle
There can be a default note within it
or maybe
The above addition should help prevent the scoop-extras bucket from having to run external reg and powershell scripts for file associations (also see https://github.com/lukesampson/scoop-extras/pull/1566)