On Mon, Jun 29, 2020 at 10:54 PM Alex Henrie <alexhenrie24@gmail.com> wrote:

On Mon, Jun 29, 2020 at 1:49 PM Nikolay Sivov <bunglehead@gmail.com> wrote:
>
>
>
> On Mon, Jun 29, 2020 at 10:45 PM Alex Henrie <alexhenrie24@gmail.com> wrote:
>>
>> On Thu, Jun 25, 2020 at 3:29 AM Francois Gouget <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?

-Alex