dmenu-extended doesn't honor Terminal=true in .desktop files? about dmenu-extended HOT 5 CLOSED

That's interesting.
What do you have in your preferences file for:

    "terminal": "gnome-terminal", 

When you run ranger as per the example .desktop file, it should execute the script ~/.dmenuEextended_shellCommand.sh which contains

#! /bin/bash
ranger

using the command gnome-terminal -e /home/user/.dmenuEextended_shellCommand.sh

What flavour of Linux are you running?

from dmenu-extended.

Regarding your questions:
In my dmenu-extended preferences I have "terminal": "urxvt". I just tried with konsole and the issue persists.
I am running Arch Linux.

When in dmenu-extended I pick ranger directly, everything works fine and I get my terminal of choice running ranger.
If instead I pick a directory (which should be opened by ranger), the strange behavior appears. It seems to be mediated by xdg-open. It's as if it does open it in a terminal, but in the wrong one (the login terminal). The expected behavior would be to open a new terminal (under the window manager) in which to run ranger.

from dmenu-extended.

I'm about 50% sure I understand what you're saying.
I can select a folder from the menu and it opens in Nautilus fine, but that's the behaviour I expect.
Have you configured your system such that xdg-open would open a folder in ranger?
If so, what happens when you type a command such as

xdg-open /home/user/Downloads

into a terminal and run that. Does it do as you expect?
I can't speak for why the terminal programs you're running are launched in the login terminal, that's bizzare.
Try setting this in your preferences file and see if this does what you want:

    "filebrowser": "gnome-terminal -e ranger", 

Then open a directory from within dmenu-extended.

from dmenu-extended.

I'm sorry, I had noticed my message was convoluted and I rewrote it twice, but to no avail apparently.

xdg-open /path/to/some/folder works fine in terminal

Setting "filebrowser": "urxvt -e ranger" does indeed work and make everything behave as expected.

There may be a bigger issue somewhere down below, I'm not sure it's in dmenu-extended. I'll do some digging and report back to you if I find something.

This issue is solved. Thank you!

from dmenu-extended.

from dmenu-extended.