From: Alex Henrie Subject: Re: [PATCH v2 0/2] Improved file association desktop integration Message-Id: Date: Mon, 29 Jun 2020 14:40:53 -0600 In-Reply-To: References: <20200624071127.109241-1-alexhenrie24@gmail.com> On Mon, Jun 29, 2020 at 2:27 PM Nikolay Sivov wrote: > > > > On Mon, Jun 29, 2020 at 11:22 PM Alex Henrie wrote: >> >> On Mon, Jun 29, 2020 at 2:05 PM Nikolay Sivov wrote: >> > >> > >> > >> > On Mon, Jun 29, 2020 at 10:54 PM Alex Henrie wrote: >> >> >> >> On Mon, Jun 29, 2020 at 1:49 PM Nikolay Sivov wrote: >> >> > >> >> > >> >> > >> >> > On Mon, Jun 29, 2020 at 10:45 PM Alex Henrie wrote: >> >> >> >> >> >> On Thu, Jun 25, 2020 at 3:29 AM Francois Gouget 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 >> >> ` 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). > Do they get updated if you move prefix with Office somewhere, or if you remove it? Steam example is even more artificial. > > Maybe disabling it by default, and keeping that checkbox in winecfg, would be good for now, I don't know. I'd really like desktop integration to "just work" for novice Wine users who only have one prefix. Maybe we should disable all desktop integration by default on prefixes other than $HOME/.wine, but in the general case desktop integration for programs that the user installs is a desirable thing. -Alex