From cc09b607330385d6d81b9c47cf64a2442432e93f Mon Sep 17 00:00:00 2001
From: Soispha <soispha@vhack.eu>
Date: Tue, 20 Feb 2024 16:35:15 +0100
Subject: refactor(treewide): Add a `.sh` extension to shell scripts

---
 hm/soispha/conf/lf/commands/scripts/trash | 28 ----------------------------
 1 file changed, 28 deletions(-)
 delete mode 100755 hm/soispha/conf/lf/commands/scripts/trash

(limited to 'hm/soispha/conf/lf/commands/scripts/trash')

diff --git a/hm/soispha/conf/lf/commands/scripts/trash b/hm/soispha/conf/lf/commands/scripts/trash
deleted file mode 100755
index 4da188e5..00000000
--- a/hm/soispha/conf/lf/commands/scripts/trash
+++ /dev/null
@@ -1,28 +0,0 @@
-#! /usr/bin/env dash
-
-# shellcheck source=/dev/null
-SHELL_LIBRARY_VERSION="2.0.13" . %SHELL_LIBRARY_PATH
-
-trash_output=$(mktmp);
-expected_error_output=$(mktmp);
-
-while read -r file; do
-    set -- "$@" "$file"
-done < "$(tmp echo "$fx")"
-
-# TODO: why are we using trashy at all, when trash-cli can do everything?
-#
-# try trashy first, through nix because both trashy and trash-cli provide a trash command, which conflicts
-nix run nixpkgs#trashy -- put "$@" 2> "$trash_output";
-
-# FIXME: Find a way, that does not depend on parsing an error message <2023-08-29>
-cat << EOF > "$expected_error_output";
-error: Error during a \`trash\` operation: Unknown { description: "Path: '\"/.Trash-1000\"'. Message: Permission denied (os error 13)" }
-EOF
-
-if [ "$(cat "$expected_error_output")" = "$(cat "$trash_output")" ];then
-    warning "Deleting with trash-cli to the /.Trash folder";
-    # this file could not be trashed because it is on the tempfs volume, trash-cli can do this this
-    trash-put "$@";
-fi
-# vim: ft=sh
-- 
cgit 1.4.1