Starting vifm not from terminal

u0 · 2021-07-07 23:42:55

When I start vifm not from terminal it freazes.
I want to start it in Qtile with command promptand and autocomplete.

If i create script in ~/.scripts. And add it to $PATH

#!/bin/bash
alacritty -e vifm &

Prompt can still run binary but not script.

Or in case I want to run vifm from terminal with parameters
it can ignore it and run only script instead.

Is there an elegant way to make script run from prompt but run binary from terminal?
Or other solution?

Trilby · 2021-07-08 00:25:47

You'll need to be a lot more specific.

u0 wrote:

Prompt can still run binary but not script.

What does this mean? Do you mean you can run /usr/bin/vifm from a shell prompt, but you cannot run the script? Why not? Please post the complete command and output of attempting to run the script.

u0 wrote:

Or in case I want to run vifm from terminal with parameters
it can ignore it and run only script instead.

What does each "it" referr to here? Do you mean you've named the script "vifm"? If you want to call the script "vifm" you should pass on any command line parameters:

#!/bin/sh
alacritty -e vifm "$@" &

u0 wrote:

Is there an elegant way to make script run from prompt but run binary from terminal?

What is "prompt" if not a shell session in the terminal?

u0 · 2021-08-18 15:00:17

By prompt I mean when you press [mod] and [r] in qtile. Appears a line where you can enter name of a program and run it.

I put the file named vifm in
~/.scripts/

it containes

#!/bin/sh
alacritty -e vifm "$@" &

Exporting dir to $PATH

export PATH=~/.scripts:$PATH

Now when I type vifm in alacritty it blinks and nothing happens.

I think it is better to solve one task at a time.
I want to be able to start vifm from [mod] and [r].
But it freezes all processes at tty1

Last edited by u0 (2021-08-18 15:41:25)

willemw · 2021-08-18 17:45:43

Try changing the script to:

alacritty -e /usr/bin/vifm "$@" &

i.e. prepend the full path to vifm.

Last edited by willemw (2021-08-18 17:51:11)

u0 · 2021-08-19 00:01:39

Yes script pointed to itself.

vifm still freezes when started from prompt/launcher

Docbroke · 2021-08-19 01:37:01

Try running with --no-config

alacrity -e /usr/bin/vifm --no-config "$@" &

If it still fails, please try running same command from another terminal instead of qtile shortcut, and let's see the error output.

Last edited by Docbroke (2021-08-19 01:39:27)

willemw · 2021-08-19 05:58:44

You can remove the & at the end.

To see what goes wrong, catch all output and save it to a file:

#!/bin/sh

(
  alacritty --command /usr/bin/vifm "$@"

) > /tmp/vifm.log 2>&1

u0 · 2021-08-19 21:11:20

vifm works OK from alacritty and xterm.

$PATH points to ~/.scripts/vifm
So now when I type vifm in terminal it starts NEW alacritty with vifm.

But it freezes from qtile/awesome/ command prompt.
By command pronpt I mean those thing when you press [mod] [r] to run name of the program. In qtile it corresponds to lazy.spawncmd

It could be qtile command prompt widget uses another path to run program so it starts without alacritty.
https://docs.qtile.org/en/v0.18.0/_modu … rompt.html

Last edited by u0 (2021-08-19 21:59:25)

thiagowfx · 2021-08-20 04:12:14

u0 wrote:

But it freezes from qtile/awesome/ command prompt.
By command pronpt I mean those thing when you press [mod] [r] to run name of the program. In qtile it corresponds to lazy.spawncmd

Is that prompt something akin to rofi or dmenu_run?

Does it support auto completion for other applications at all?

u0 · 2021-08-20 14:15:50

thiagowfx wrote:

Is that prompt something akin to rofi or dmenu_run?
Does it support auto completion for other applications at all?

Yes it is like rofi and dmenu_run. It supports autocompletion.

I use default built in options of qtile for now.

Arch Linux

#1 2021-07-07 23:42:55

Starting vifm not from terminal

#2 2021-07-08 00:25:47

Re: Starting vifm not from terminal

#3 2021-08-18 15:00:17

Re: Starting vifm not from terminal

#4 2021-08-18 17:45:43

Re: Starting vifm not from terminal

#5 2021-08-19 00:01:39

Re: Starting vifm not from terminal

#6 2021-08-19 01:37:01

Re: Starting vifm not from terminal

#7 2021-08-19 05:58:44

Re: Starting vifm not from terminal

#8 2021-08-19 21:11:20

Re: Starting vifm not from terminal

#9 2021-08-20 04:12:14

Re: Starting vifm not from terminal

#10 2021-08-20 14:15:50

Re: Starting vifm not from terminal

Board footer