What I mean is,normally if you want to open a file,then you right click it and select "open with" and select the default program to open it. But what I would find better is that you could select which command opens the program,what I mean is that for example you want to set that .bat files get opened by the winecmd command,so you don't need to open a terminal and type "winecmd >filename<.bat. I know you can just create bash scripts for that,but with this feature it would be much faster that creating bash scripts for every file you wanna open by a command. I also have a good idea how to implement this feature:That normal files have the same "Application tab" that .desktop files have (https://i.nuuls.com/FnEve.png),so that you can select exactly with which command the file gets opened.
You can already do this. In the "Choose Application for [whatever]" window, type the name of the terminal command in the text field, click on the "Terminal options" button at the bottom, and click "Run in Terminal".
But not every command needs to run in a terminal,for example if I want to start a program with a env var,for example "foo=1 foo firefox". And also,I still think that an "Application Tab" with a command option would be cool,cause then I can change how each exectable gets executed,instead of setting the same command for every file with the same file extension.
You can create custom .desktop files for those. This is such a niche use case that I don't think it is worth putting any effort into making it more user-friendly given that 1) we already fully support it and 2) anyone who has such an esoteric use case must be an expert in the system and will have no problem using it (and if they do, maybe they're not as much of an expert as they thing, and should re-evaluate whether this is really good idea to do :) ).
It's not a must have,but it will make everything faster,I have an example: You download a folder that has lets say 20 files and you want to execute all of them with custom commands,right now you would need to create 20 .desktop files,then copy the path of each file to each .desktop file and then add a custom command to each .desktop file and then launch them. That is annoying when you want to download a file,then test it and then just want to uninstall it. With an Application Tab function for executables it would just be faster. I don't want this feature cause I am an expert,but cause it is simply just easier and faster. And when this feature would get implemented,then you can also add features like being able to customize multiple Application Tabs of multiple files at once,for example I could right click 20 files and open the properties and then set that they all will use the same launch command.
> You download a folder that has lets say 20 files and you want to execute all of > them with custom commands But why? What's the specific use case?
(In reply to Nate Graham from comment #5) > > You download a folder that has lets say 20 files and you want to execute all of > > them with custom commands > But why? What's the specific use case? I remember downloading a indie horror game that had many executables (that was the gimmick of the game) and I wanted to play it,but it didn't work with latest wine,so I had to make a .desktop file for each .exe. But I have a better example,I want to test if some ev vars and commands work,so I would have to download the file I want to test,but then I also have to make a .desktop file so I can start it with the command,it just costs time. And I have another example,if I want to start lets say firefox with some custom commands,then I edit the .desktop file that I can access from krunner,but the problem is that if I want to start firefox in any other way than the .desktop file,then it won't start with those commands.
Those are super hyper oddly specific use cases that we already support via the methods you used. Launching them via the command line is another option.
There is another use case,if I download a normal windows .exe,but that doesn't work with latest wine,then I could change the wine version it should use faster,if I wouldn't need to create a .desktop file for the executable. The problem with opening it in the terminal is,that I would have to do that every single time I want to open the file,and I could also forget which wine version worked the best. And also I just hate it when there is a .desktop file of a .exe in every directory in which the normal wine doesn't work,that makes them look different than the other wine program directories and when I see something like this then my ocd kicks in. I mean all those points aren't a big thing,but it would still improve my experience.
Out of curiosity, why are you running so much Windows software? It is all old games?
Most is old games that just didn't get ported to Linux and also many new games that just aren't available for Linux. And for the programs,many Linux ports of emulators lack some features that the windows version has (for example this tool,you can only play sm64ds with joystick control by using that https://github.com/pants64DS/ToxInput) and some emulators don't have a Linux port at all (for example Net64+,it is a tool that allows you to play sm64 online,will get ported to linux in the future,but I wanna use it now https://net64-mod.github.io/ and cemu,a wii u emulator https://cemu.info/ and OdySim,a emulator for one of the first consoles on the world https://odysim.blogspot.com/). Besides from that I still need some programs that are only available for windows (for example xdelta ui https://www.romhacking.net/utilities/598/). So lots of things only work with wine.