https://bugs.kde.org/show_bug.cgi?id=420144
--- Comment #3 from codingko...@gmail.com --- - "/usr/bin/code-oss --no-sandbox --new-window" opens a new empty window of VS Code. "Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium." is printed to the console. - "/usr/bin/code-oss --no-sandbox --new-window %F" opens a new empty window of VS Code, with "%F" (literally) opened as a new file. I do still call this a "new empty window" because of it launching without opening the most recent directory, which is what it can be configured to do when launched without the "--new-window" switch. The same string as before is printed to the console. > How can an action take a filepath, that sounds wrong, but I assume we would > parse it out. It doesn't make sense to me either, but it does seem to be valid under the specification. "Action keys" (https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html#extra-actions-keys) simply refers to the Exec key as it's used normally, under which "%F" is valid. desktop-file-validate doesn't say that there are any issues with it either. -- You are receiving this mail because: You are watching all bug changes.
