Add option "Run interactive" when auto confirm install fails

[alr86]

Step 1. Before you submit

• I have read the Troubleshooting and Usage pages.
• I've successfully updated to the latest version following the guidance.
• I've successfully updated the system packages to the latest.
• I've ticked the checkboxes without reading their contents

2. Quick log

My package conflict log:

[sudo] password for [user]: 
loading packages...
resolving dependencies...
looking for conflicting packages...
:: illogical-impulse-quickshell-git-0.1.0.r1-6 and quickshell-0.2.1-3 are in conflict. Remove quickshell? [y/N] 
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: illogical-impulse-quickshell-git-0.1.0.r1-6 and quickshell-0.2.1-3 are in conflict
==> WARNING: Failed to install built package(s).
[./setup]: Command "makepkg -Afsi --noconfirm" has failed.
You may need to resolve the problem manually BEFORE repeating this command.
[Tip] If a certain package is failing to install, try installing it separately in another terminal.
  r = Repeat this command (DEFAULT)
  e = Exit now
  i = Ignore this error and continue (your setup might not work correctly)
 [R/e/i]: 

3. Describe the request

When the fully automated install (--noconfirm) hits a package conflict, the only options are Repeat / Exit / Ignore.

There is no way to re-run the failing makepkg command interactively, so I need to guess and go to failed pkg directory(dots-hyprland/sdata/dist-arch/[...]) and run makepkg manually or force remove quickshell package and run command again.

Please add a fourth option like this:
c = Re-run this command without --noconfirm

[clsty]

c = Re-run this command without --noconfirm

This is not suitable cuz --noconfirm is only applicable for makepkg and pacman, not any other commands, and letting x() handle one special case is not elegant at all.

dots-hyprland/sdata/lib/functions.sh

Lines 34 to 57 in 4442200

	function x(){
	if "$@";then local cmdstatus=0;else local cmdstatus=1;fi # 0=normal; 1=failed; 2=failed but ignored
	while [ $cmdstatus == 1 ] ;do
	echo -e "${STY_RED}[$0]: Command \"${STY_GREEN}$*${STY_RED}\" has failed."
	echo -e "You may need to resolve the problem manually BEFORE repeating this command."
	echo -e "[Tip] If a certain package is failing to install, try installing it separately in another terminal.${STY_RST}"
	echo " r = Repeat this command (DEFAULT)"
	echo " e = Exit now"
	echo " i = Ignore this error and continue (your setup might not work correctly)"
	local p; read -p " [R/e/i]: " p
	case $p in
	[iI]) echo -e "${STY_BLUE}Alright, ignore and continue...${STY_RST}";cmdstatus=2;;
	[eE]) echo -e "${STY_BLUE}Alright, will exit.${STY_RST}";break;;
	*) echo -e "${STY_BLUE}OK, repeating...${STY_RST}"
	if "$@";then cmdstatus=0;else cmdstatus=1;fi
	;;
	esac
	done
	case $cmdstatus in
	0) echo -e "${STY_BLUE}[$0]: Command \"${STY_GREEN}$*${STY_BLUE}\" finished.${STY_RST}";;
	1) echo -e "${STY_RED}[$0]: Command \"${STY_GREEN}$*${STY_RED}\" has failed. Exiting...${STY_RST}";exit 1;;
	2) echo -e "${STY_RED}[$0]: Command \"${STY_GREEN}$*${STY_RED}\" has failed but ignored by user.${STY_RST}";;
	esac
	}

A suitable option is R = Repeat this command (more interactively).

However this will be much harder to implement than it looks like. We know that Bash does not provide a goto feature, and the current x() is based on storing the command as arguments "$@", meaning that it cannot magically provides a "more interactive" version of the stored command to repeat with by only modifying the definition of x() itself. The whole install script will need refactoring.

So yes, it's a sensible TODO but I'm not doing it until I would like to deal with trouble someday.