From 2bceba4557329cefff5229f62542d4e52f611abd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?cat=20=C3=A6scling?= <aescling@cat.family>
Date: Tue, 22 Jul 2025 13:46:57 -0400
Subject: [PATCH] Wrap env::remove_var calls in unsafe blocks

env::remove_var is newly marked unsafe in the 2024 edition due to its
inherent unreliability in multithreaded contexts.

This code is single-threaded so there should be no problem.

See https://doc.rust-lang.org/edition-guide/rust-2024/newly-unsafe-functions.html#stdenvset_var-remove_var
---
 src/main.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main.rs b/src/main.rs
index eaf96e4..9bfe959 100644
--- a/src/main.rs
+++ b/src/main.rs
@@ -22,9 +22,9 @@ fn prepare_env() {}
 fn prepare_env() {
     // When starting from iTerm, these env vars could cause some display issues.
     log::debug!("unset $TERM_PROGRAM");
-    env::remove_var("TERM_PROGRAM");
+    unsafe { env::remove_var("TERM_PROGRAM") };
     log::debug!("unset $TERM_PROGRAM_VERSION");
-    env::remove_var("TERM_PROGRAM_VERSION");
+    unsafe { env::remove_var("TERM_PROGRAM_VERSION") };
 }
 
 fn check_nvim(vim_exe_path: &str) {