On 6/29/20 3:27 PM, Nikolay Sivov wrote:
On Mon, Jun 29, 2020 at 11:22 PM Alex Henrie <alexhenrie24@gmail.com mailto:alexhenrie24@gmail.com> wrote:
On Mon, Jun 29, 2020 at 2:05 PM Nikolay Sivov <bunglehead@gmail.com <mailto:bunglehead@gmail.com>> wrote: > > > > On Mon, Jun 29, 2020 at 10:54 PM Alex Henrie <alexhenrie24@gmail.com <mailto:alexhenrie24@gmail.com>> wrote: >> >> On Mon, Jun 29, 2020 at 1:49 PM Nikolay Sivov <bunglehead@gmail.com <mailto:bunglehead@gmail.com>> wrote: >> > >> > >> > >> > On Mon, Jun 29, 2020 at 10:45 PM Alex Henrie <alexhenrie24@gmail.com <mailto:alexhenrie24@gmail.com>> wrote: >> >> >> >> On Thu, Jun 25, 2020 at 3:29 AM Francois Gouget <fgouget@free.fr <mailto:fgouget@free.fr>> wrote: >> >> > >> >> > On Wed, 24 Jun 2020, Alex Henrie wrote: >> >> > >> >> > > The big change here is rewriting the patches to avoid the term >> >> > > "blacklist", which I have replaced with "naughty list". >> >> > >> >> > In this context it's not clear what naughty means. What in a file >> >> > extension is "badly behaved, disobedient or mildly rude or indecent"? >> >> >> >> Several built-in Wine programs are badly behaved in the sense that >> >> they associate themselves with file types that native desktop programs >> >> are better suited to open. >> > >> > >> > Would it be a problem to remove such integration completely? I can't think of a good scenario when it would be useful. >> >> The associations have to be in Wine for programs that call `start.exe >> <file>` to open a file. > > > This has to be a prefix configuration, not affecting opening/strating things through DE. E.g. 'wine start test.txt' supposedly expected to open notepad, > that doesn't have to be configured for DE associations. Maybe you're talking about something else, I meant this part: > > >> Several built-in Wine programs are badly behaved in the sense that > >> they associate themselves with file types that native desktop programs > >> are better suited to open. > > Builtin programs or installed programs only need shell extensions stuff in registry to open via 'wine start', > they don't have to touch system configuration. > > Is that a different issue? If I understand you correctly now, you're proposing to get rid of desktop integration for associations altogether. I imagine that would be very undesirable for people who use MS Office on Linux through Wine. I'd also like to be able to install Steam games in the Windows client by browsing https://store.steampowered.com/ in the native browser and then clicking steamapp:// links that open in Wine.That becomes unusable once you have more than one prefix (I believe desktop integration does not specify WINEPREFIX for launch commands).
In fact it does; see write_freedesktop_association_entry() in winemenubuilder.c.
Do they get updated if you move prefix with Office somewhere, or if you remove it?
winemenubuilder automatically updates associations on prefix update, or when manually run with the -a argument.
Of course associations never get removed, which is a problem, but it's hard to solve. It's not obvious to me that it's worth throwing out the whole of winemenubuilder just because of that, though.
Not to mention that moving prefixes is probably not a common operation anyway.
Steam example is even more artificial.
Why? Running Steam from within Wine is very common, even now after Proton has been introduced.
Nor is Steam the only program with an idiosyncratic protocol or file extension.
Maybe disabling it by default, and keeping that checkbox in winecfg, would be good for now, I don't know.