cli: Fix Flatpak launcher argument ordering (#61577) (cherry-pick to preview) (#62958)
Some checks are pending
run_tests / clippy_windows (push) Blocked by required conditions
run_tests / clippy_linux (push) Blocked by required conditions
run_tests / clippy_mac (push) Blocked by required conditions
run_tests / clippy_mac_x86_64 (push) Blocked by required conditions
run_tests / run_tests_windows (push) Blocked by required conditions
run_tests / orchestrate (push) Waiting to run
run_tests / check_style (push) Waiting to run
run_tests / check_workspace_binaries (push) Blocked by required conditions
run_tests / build_visual_tests_binary (push) Blocked by required conditions
run_tests / check_wasm (push) Blocked by required conditions
run_tests / check_dependencies (push) Blocked by required conditions
run_tests / check_docs (push) Blocked by required conditions
run_tests / check_licenses (push) Blocked by required conditions
run_tests / check_scripts (push) Blocked by required conditions
run_tests / check_postgres_and_protobuf_migrations (push) Blocked by required conditions
run_tests / extension_tests (push) Blocked by required conditions
run_tests / tests_pass (push) Blocked by required conditions
run_tests / run_tests_linux (push) Blocked by required conditions
run_tests / run_tests_mac (push) Blocked by required conditions
run_tests / miri_scheduler (push) Blocked by required conditions
run_tests / doctests (push) Blocked by required conditions

Cherry-pick of #61577 to preview

----
Closes https://github.com/zed-industries/zed/issues/62801

# Objective

Fix issue https://github.com/flathub/dev.zed.Zed/issues/395 (reported
against the flathub package, but as described in it, it was introduced
by https://github.com/zed-industries/zed/pull/57440 ).

The symptom was that when running `flatpak run dev.zed.Zed <project
path>` (or some alias), then you'd get two "files" opened `--zed` and
`zed-editor`, with `zed-editor` also being added to the Zed project list
in the open window, which was quite annoying.

## Solution

- The flatpak CLI launcher, which self-launches with potential extra
arguments, now puts those arguments first rather than last.

## Testing

- A simple unit test targets the helper function that adds the arguments
- It also verifies that the parsed args come out as expected

## Self-Review Checklist:

- [ x ] I've reviewed my own diff for quality, security, and reliability
- [ x ] Unsafe blocks (if any) have justifying comments
- [ x ] The content adheres to Zed's UI standards

([UX/UI](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist)
and

[icon](https://github.com/zed-industries/zed/blob/main/crates/icons/README.md)
guidelines)
- [ x ] Tests cover the new/changed behavior
- [ x ] Performance impact has been considered and is acceptable

Note: I believe that other bullets than self-review and tests are not
relevant, as there is no unsafe, no expected performance impact, and no
UI changes.

---

Release Notes:

- Fixed an issue where Flatpak CLI launches would open
unrelated/nonexistent files due to a bug in argument construction

Co-authored-by: Kirill Bulatov <kirill@zed.dev>

Co-authored-by: Jonas Lundholm Bertelsen <drixi.b@gmail.com>
Co-authored-by: Kirill Bulatov <kirill@zed.dev>
This commit is contained in:
zed-zippy[bot] 2026-08-20 16:50:44 +00:00 committed by GitHub
parent 0cb3a3d05a
commit 40f7be514d
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -1029,13 +1029,26 @@ mod linux {
#[cfg(target_os = "linux")]
mod flatpak {
use std::ffi::OsString;
use std::path::PathBuf;
use std::path::{Path, PathBuf};
use std::process::Command;
use std::{env, process};
const EXTRA_LIB_ENV_NAME: &str = "ZED_FLATPAK_LIB_PATH";
const NO_ESCAPE_ENV_NAME: &str = "ZED_FLATPAK_NO_ESCAPE";
fn restart_cli_args(flatpak_dir: &Path, invocation_args: &[OsString]) -> Vec<OsString> {
let mut args = Vec::with_capacity(invocation_args.len() + 2);
if !invocation_args.iter().any(|arg| arg == "--zed") {
// Positional paths consume all following arguments, so launcher options must precede them.
args.push("--zed".into());
args.push(flatpak_dir.join("libexec").join("zed-editor").into());
}
args.extend_from_slice(invocation_args);
args
}
/// Adds bundled libraries to LD_LIBRARY_PATH if running under flatpak
pub fn ld_extra_libs() {
let mut paths = if let Ok(paths) = env::var("LD_LIBRARY_PATH") {
@ -1066,16 +1079,8 @@ mod flatpak {
);
args.push(flatpak_dir.join("bin").join("zed").into());
let mut is_app_location_set = false;
for arg in &env::args_os().collect::<Vec<_>>()[1..] {
args.push(arg.clone());
is_app_location_set |= arg == "--zed";
}
if !is_app_location_set {
args.push("--zed".into());
args.push(flatpak_dir.join("libexec").join("zed-editor").into());
}
let invocation_args = env::args_os().skip(1).collect::<Vec<_>>();
args.extend(restart_cli_args(&flatpak_dir, &invocation_args));
let error = exec::execvp("/usr/bin/flatpak-spawn", args);
eprintln!("failed restart cli on host: {:?}", error);
@ -1131,6 +1136,31 @@ mod flatpak {
.map(|(key, val)| format!("--env=FLATPAK_{}={}", key, val).into())
.collect()
}
#[cfg(test)]
mod tests {
use clap::Parser as _;
use super::*;
#[test]
fn test_restart_cli_args() {
let flatpak_dir = Path::new("/flatpak");
let args = restart_cli_args(flatpak_dir, &["project".into()]);
let parsed =
crate::Args::try_parse_from(std::iter::once(OsString::from("zed")).chain(args))
.unwrap();
assert_eq!(parsed.zed, Some(flatpak_dir.join("libexec/zed-editor")));
assert_eq!(parsed.paths_with_position, ["project"]);
let invocation_args = ["--zed".into(), "/custom/zed-editor".into()];
assert_eq!(
restart_cli_args(flatpak_dir, &invocation_args),
invocation_args
);
}
}
}
#[cfg(target_os = "windows")]