Things I can't figure out with nnn

[TTSKarlsson]

Machine: Arch, KDE 6 Plasma, nnn-nerd installed through paru for icons, but every step tested with the seemingly official(?) nnn package. I'm using standard bash in a ghostty terminal.

I'm just getting straight to the points:

NNN_OPENER is not recognized if exported to the current shell, but when called on the same line as nnn:

⋗ echo $NNN_OPENER
/home/tkarlsson/.config/nnn/plugins/nuke

⋗ nnn -dc <--- Does not know about NNN_OPENER

⋗ NNN_OPENER=/home/tkarlsson/.config/nnn/plugins/nuke nnn -dc  <--- Suddenly knows about NNN_OPENER

Can't execute files

I'm not sure what's going on with this at all (this is with nuke enabled as above), when I press right or enter on executable (go compiled executable), showing with screens:

This happens: When pressing right or enter on listpackages executable the TUI quickly blinks and you can see the main buffer for a screenframe or two, but no output.

Expectation: I expect it to run the listpackages in the current shell and preferably quit the nnn file manager.

Not using nuke

When not using the plugin nuke, everything is run through xdg-open but gets blocked because it's not in a 'trusted context'

This one is a system problem obviously, maybe someone knows a workaround. I've tried creating desktop files and adding to mimelist and so on, but it seems an app like nnn can't be trusted by KDE.

I've stopped here for now as I need the basics to work first. I hope someone knows what's going on here.

[N-R-K]

NNN_OPENER is not recognized if exported to the current shell

How are you exporting it exactly?

[TTSKarlsson]

When .bashrc is sourced:

# nnn file manager
export NNN_OPENER=$HOME/.config/nnn/plugins/nuke

And as you can see from the citation in op the env variable exists in the shell when doing echo $NNN_OPENER

[N-R-K]

Hmm, weird. I have no clue why that would happen.

Can you go into nnn and press ?, on the bottom it should show all the active env vars. Do you see NNN_OPENER there?