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

fix(flatpak): Remove cwd from desktop entry #5002

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

briandipalma
Copy link

cwd provided from desktop entry overrides Lua configured cwd so you end up with different behaviour when you launch from DE launcher and from running flatpak run ....

I'm guessing this is the file that's used to create the flatpak desktop entry.

`cwd` provided from desktop entry overrides Lua configured cwd so you end up with different behaviour when you launch from DE launcher and from running `flatpak run ...`.
@wez
Copy link
Owner

wez commented Feb 12, 2024

Thanks for diving in!
Can you explain more about what you're trying to resolve here?

@briandipalma
Copy link
Author

I installed the flatpak today and started configuring wezterm: https://github.com/briandipalma/iac/blob/main/dotfiles/wezterm/wezterm.lua#L9

But this line was not having any effect

config.default_cwd = wezterm.home_dir .. "/dev/iac"

when I ran the flatpak from the desktop environment launcher (Pop_OS/GNOME). Yet it did work when I ran the flatpak from the command line with flatpak run org.wezfurlong.wezterm. So obviously I went to dig into the desktop file which is what the launcher uses. I noticed the --cwd and from what I can tell in the documentation that flag overrides the config file. So I guessed that was the problem. Deleting it fixed the problem.

Do we need to specify --cwd in the desktop file? I would have thought that, based on the documentation, wezterm would open up in the users home directory as fallback anyway.

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

Successfully merging this pull request may close these issues.

None yet

2 participants