Change program depending on application opening it

[kocv59]

Can the program change depending on which application is opening it? An example can be to create one handler that opens a csv file in the editor if opened with handlr open. But if you click on a csv file in the browser it would open in a GUI csv viewer or in a different tab in the terminal when #102 is done.

Then the file association can be set for the whole system and handlr can decide what application opens instead of having to change the file associations in every application.

[Anomalocaridid]

Depending on your web browser, it might use its own settings for default file associations, but that does not involve handlr.

If you shadow xdg-open with a script that calls handle, you might be able to let it fall back on handlr, but the browser's own settings would still take precedence for what it decides to open.

You might want to consider setting up a selector and setting multiple associations if you are not already. That way, when you open a CSV file, you could decide which program you want to use.

[kocv59]

I set the browser to use the system default that xdg-open uses but if I can customize in handlr I can open it in a different program if the request is from a browser or not from a terminal.

[Anomalocaridid]

The issue is I don't know of any way to implement the ability for handlr to reliably detect what program is running it.

[kocv59]

Scripts can use -t 0 to tell if it's running in the terminal or not. So the feature can be associate text/csv on the whole system with handlr and configure handlr that if it's a terminal choose one executable or .desktop file and if it's not choose another one.

Not sure if it can detect the exact program but detecting if its from the terminal or not can handle lots of these cases.

[Anomalocaridid]

Detecting whether or not it is being run in a terminal is certainly doable.

Although now I need to figure out how to let the user set different defaults for opening in a terminal and opening in a GUI.

I am thinking probably one of the following:

• Separate mimeapps.list files, one for terminal, one for GUI.
• Since mimeapps.list already supports having multiple programs for each mimetype, maybe let the user configure which one should be used for each case, falling back to default mimeapps.list behavior if necessary.

Suggestions are more than welcome if you have any ideas.

Unfortunately this feature is significant enough to be blocked by #86 for now.