ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
Guest1197 has quit [Remote host closed the connection]
AbleBacon has quit [Read error: Connection reset by peer]
scrumplex_ has joined #freedesktop
scrumplex has quit [Ping timeout: 480 seconds]
AbleBacon has joined #freedesktop
jarthur has joined #freedesktop
lyudess has joined #freedesktop
Lyude has quit [Read error: Connection reset by peer]
ximion has quit [Remote host closed the connection]
sima has joined #freedesktop
jturney has quit [Ping timeout: 480 seconds]
Kayden has joined #freedesktop
vsyrjala has quit [Ping timeout: 480 seconds]
bmodem has joined #freedesktop
<manuels2>
Hi
vsyrjala has joined #freedesktop
<manuels2>
How can I get fork the specs
<manuels2>
I want to send a pr to the desktop entry spec.
<manuels2>
I talked a lot with the author of the xdg-terminal-execute author, terminal authors, I discussed on the mailing list, commented on the proposals, and tried to send PRs to terminals.
<manuels2>
The xte proposal is illformed and the terminal intent is going to take ages.
<manuels2>
I simply want to provide the users of my app a reliable way to run _their_ terminal.
<manuels2>
I give in to the idea of pushing such a proposal.
<manuels2>
But at least I realy would like to add a key to the desktop entry spec that carves the defacto standard to run a command in a terminal into stone.
<manuels2>
Defacto because _all_ terminals that make sense out of it have a command execution parameter.
<manuels2>
I dont like the idea of a default of `-e` as specified in the x-t-e proposal. But there is no other way of reliably running such a command in the terminal if not exposed by the app itself.
<manuels2>
so even if folks refuse to establish x-t-e and want to wait decades for app intents apps like albertlauncher can benefit a standard mechanism to run commands in terminals
AbleBacon has quit [Read error: Connection reset by peer]
<manuels2>
The only way to do so is to add the ExecArg (or another name) with the semantic either fully implying its a terminal with command execution interface or a conditional semantic based on `Categories` containing `TerminalEmulator` (as some suggested).
<manuels2>
I am fine with either of them.
<manuels2>
I am also fine with both proposals (x-t-e and terminal intent), and although in every discussion i had so far they were seen as competitors, I think we should have them both. Implementations like launchers should then take them both into account, because they are similar but not congruent in feature sets and coverage. But thats another story and as
<manuels2>
said I give in.
<manuels2>
There is simply no progress. Folks reject x-t-e because the terminal intent draft exist, yet terminal author reject to implement such an interface. Such a shithow.
<manuels2>
So I simply want to get the command line interface standardized, without these alledgedly competing standards. Such that I can let my users choose a terminal and call it a day.