For anyone on ArchLinux that's having problems with the image previewer showing random characters instead of the image, just add the chafa option '--polite on' in your previewer script.

My image previewer function in the previewer script:

image() {
	geometry="$(($2-2))x$3"
    chafa "$1" -f sixels -s "$geometry" --animate false | fold -w 65535
}

For anyone on ArchLinux that's having problems with the image previewer showing random characters instead of the image, just add the chafa option '--polite on' in your previewer script.

My image previewer function in the previewer script:

image() {
	geometry="$(($2-2))x$3"
    chafa "$1" --polite on -f sixels -s "$geometry" --animate false | fold -w 65535
}

Hello all. I've written a command which should add all selected files to my chezmoi source state. From a regular terminal the command is as such: chezmoi add myfile

In my lfrc I have the following:

cmd chezmoi_add %{{
    set -f
    for i in $fx do
        chezmoi add $i
    done
}}

map ac chezmoi_add

However whenever I try to use it on a file I get the following in the bottom left corner of lf:

--: -c: line 4: `              chezmoi add $i'

Can anyone shed some light into what I am doing wrong?

Hello all. I've written a command which should add all selected files to my chezmoi source state. From a regular terminal the command is as such: chezmoi add myfile

In my lfrc I have the following:

cmd chezmoi_add %{{
    set -f
    for i in $fx do
        chezmoi add $i
    done
}}

map ac chezmoi_add

However whenever I try to use it on a file I get the following in the bottom left corner of lf:

--: -c: line 4: `              chezmoi add $i'

Can anyone shed some light into what I am doing wrong?

EDIT: Figured it out. The solution was to put the do on the next line. This is strange because I had other commands with for loops in them and they worked even when the do was on the same line as the for

In reply to @promitheas:matrix.org

Hello all. I've written a command which should add all selected files to my chezmoi source state. From a regular terminal the command is as such: chezmoi add myfile

In my lfrc I have the following:

cmd chezmoi_add %{{
    set -f
    for i in $fx do
        chezmoi add $i
    done
}}

map ac chezmoi_add

However whenever I try to use it on a file I get the following in the bottom left corner of lf:

--: -c: line 4: `              chezmoi add $i'

Can anyone shed some light into what I am doing wrong?

EDIT: Figured it out. The solution was to put the do on the next line. This is strange because I had other commands with for loops in them and they worked even when the do was on the same line as the for

In reply to @promitheas:matrix.org

Hello all. I've written a command which should add all selected files to my chezmoi source state. From a regular terminal the command is as such: chezmoi add myfile

In my lfrc I have the following:

cmd chezmoi_add %{{
    set -f
    for i in $fx do
        chezmoi add $i
    done
}}

map ac chezmoi_add

However whenever I try to use it on a file I get the following in the bottom left corner of lf:

--: -c: line 4: `              chezmoi add $i'

Can anyone shed some light into what I am doing wrong?

EDIT: Figured it out. The solution was to put the do on the next line. This is strange because I had other commands with for loops in them and they worked even when the do was on the same line as the for

In reply to @soispha:vhack.eu
For loops need a semicolon before the do (or a newline, which you used)

In reply to @promitheas:matrix.org
New question: How can I use the unselect command after my chezmoi add $i line so that once the file is added to chezmoi it is no longer selected?

In reply to @soispha:vhack.eu
I think you can just clear ~/.local/share/lf/some_file or some path like that

Separate question: How can I pass arguments to shell commands? I read through the manual and found the shellopts section, which if I understood it correctly sais that I need to pass them as a string after the shell command. I am extending the open function to edit files with neovim, because somefiles without extensions would open a blank neovim buffer instead of the actual file:

cmd open %{{
	$alacritty '--hold -e nvim' $f
}}

I would like a new window to be created instead of neovim to open within lf, hence why I am trying to spawn an alacritty window which will execute the neovim command.

In reply to @promitheas:matrix.org
Could you please explain that a bit? Do you mean I just add a shell command after adding files to chezmoi, which will delete a certain file? How can I know which is the right file to delete?

Unix ~/.local/share/lf/files
Windows C:\Users<user>\AppData\Local\lf\files

That's the file that contains the current selection. If you delete it in your mapping (rm ...), all files will be unselected

In reply to @promitheas:matrix.org

Separate question: How can I pass arguments to shell commands? I read through the manual and found the shellopts section, which if I understood it correctly sais that I need to pass them as a string after the shell command. I am extending the open function to edit files with neovim, because somefiles without extensions would open a blank neovim buffer instead of the actual file:

cmd open %{{
	$alacritty '--hold -e nvim' $f
}}

I would like a new window to be created instead of neovim to open within lf, hence why I am trying to spawn an alacritty window which will execute the neovim command.

Lf should allow you to just write normal shell code in there. So opening a new window should be:

cmd open &{{
alacrity --hold -e "nvim '$f'"
}}

In reply to @soispha:vhack.eu
(I also changed the '%' to a '&' to allow you to use lf while the window is open, nut sure if you intend lf to be usable or actually wanted to block it until you close the window again)

Yes, I missed that about the &.

So far here is what I have. I modified the example from the manual for opening text files based on their mime-type with vi and all other files with xdg-open, and it works sort of. The only issue is that when I exit nvim, the terminal that it was running in remains open until I manually close it.

cmd open &{{
	case $(file --mime-type -Lb $f) in
		text/*)
			parent_pid=$$;
			alacritty --hold -e nvim $f & wait $!;
			kill -9 $parent_pid;;
		*)
			for f in $fx;
				do xdg-open $f > /dev/null 2> /dev/null &
				done;;
	esac
}}

I have a suspicion that kill -9 is not actually working from within the script, because if I run the following command then manually kill the resulting process id it does actually kill it.

kill -9 pid_printed_after_running_in_background

In reply to @soispha:vhack.eu
(I also changed the '%' to a '&' to allow you to use lf while the window is open, nut sure if you intend lf to be usable or actually wanted to block it until you close the window again)

Yes, I missed that about the &.

So far here is what I have. I modified the example from the manual for opening text files based on their mime-type with vi and all other files with xdg-open, and it works sort of. The only issue is that when I exit nvim, the terminal that it was running in remains open until I manually close it.

cmd open &{{
	case $(file --mime-type -Lb $f) in
		text/*)
			parent_pid=$$;
			alacritty --hold -e nvim $f & wait $!;
			kill -9 $parent_pid;;
		*)
			for f in $fx;
				do xdg-open $f > /dev/null 2> /dev/null &
				done;;
	esac
}}

I have a suspicion that kill -9 is not actually working from within the script, because if I run the following command then manually kill the resulting process id it does actually kill it.

alacritty --hold -e neofetch

kill -9 pid_printed_after_running_in_background

Yes, I missed that about the &.

So far here is what I have. I modified the example from the manual for opening text files based on their mime-type with vi and all other files with xdg-open, and it works sort of. The only issue is that when I exit nvim, the terminal that it was running in remains open until I manually close it.

cmd open &{{
	case $(file --mime-type -Lb $f) in
		text/*)
			parent_pid=$$;
			alacritty --hold -e nvim $f & wait $!;
			kill -9 $parent_pid;;
		*)
			for f in $fx;
				do xdg-open $f > /dev/null 2> /dev/null &
				done;;
	esac
}}

I have a suspicion that kill -9 is not actually working from within the script, because if I run the following command then manually kill the resulting process id it does actually kill it.

alacritty --hold -e neofetch &

kill -9 pid_printed_after_running_in_background

In reply to @soispha:vhack.eu
You should be able to use exec to run nvim, resulting in alacritty's lifetime being tied to neovim's.

Just going to post this here in case anyone can use the info. I got it working but not by using exec as that is a shell builtin and as i understand it there are some tricky stuff with calling it from a script(?). Instead I now have this in my lfrc:

cmd open &{{
	case $(file --mime-type -Lb $f) in
		text/*)
			alacritty -e sh -c "nvim \"$fx\"";;
			# parent_pid=$$;
			# alacritty -e nvim $f & wait $!;
			# kill -9 $parent_pid;;
		*)
			for f in $fx;
				do xdg-open $f > /dev/null 2> /dev/null &
				done;;
	esac
}}

I used sh -c to execute the neovim command to open the file (wrapped in double quotes), and the trick to pass the lf variable $fx to it was to properly escape the double quotes.