Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simplify or document launching external editors #68

Open
lostfictions opened this issue Dec 18, 2020 · 1 comment
Open

Simplify or document launching external editors #68

lostfictions opened this issue Dec 18, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@lostfictions
Copy link

Setting an external editor in the Flatpak version of Godot is trickier than it seems like it should be.

If I go to Editor > Editor Settings... > Text Editor > External and set the following configuration:

image

It fails with the warning (logged on the host only):

**ERROR** OS_Unix::execute - Could not create child process while executing: code

Eventually I figured out I could make it work by using flatpak-spawn as the executable instead, and prefixing --host code as additional arguments:

image

But this isn't obvious at all, especially to folks who are used to Flatpak applications being set up to "just work". It would be nice if this could either be simplified or clearly documented (maybe on its Flathub page) so that other users don't get caught on the same problem.

@Calinou
Copy link
Collaborator

Calinou commented Dec 18, 2020

This is already documented in the README: https://github.com/flathub/org.godotengine.Godot#using-an-external-script-editor

Unfortunately, Flathub doesn't really encourage going to the GitHub repository from its description page. I could modify the AppStream metadata description to mention Flatpak-specific caveats, but it feels tedious to have to do this.
Edit: Done here: #69

Perhaps we could patch Godot in the Flatpak build to make this more seamless to the user. Exec Path would just be a variable for Exec Flags to use, and flatpak-spawn would always be run behind the scenes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants