If stdin is connected to pipe, read the filenames from there instead.

[Siborgium]

It is sometimes desirable to provide only specific *.desktop files to wldash, for it could be used to create custom menus and scripts. This draft attempts to solve this problem. It, however, needs further consideration and proper discussion -- while the draft is simple (and optional), it is straightforward and (maybe) too simple.

[Siborgium]

Another option I've came up with is to pass filenames through command-line arguments, though I'm afraid it would complicate parsing by a large degree.

[kennylevinsen]

Use of the launcher for custom use-cases (effectively simulating dmenu) makes sense to some degree, but it seems odd to use .desktop files to generate arbitrary menus.

One option here would be to create a separate widget that works like the launcher but behaves more like dmenu. Then you'd be able to configure the use of that widget instead of the launcher whenever you want wldash to be in "prompt" mode.

If implemented in stdin/stdout fashion, one would do:

selection=$(cat options | wldash --config my_prompt_config)

One could also do something like:

WLDASH_DMENU_OPTIONS=options.txt WLDASH_DMENU_RESULT=selection.txt wldash --config my_prompt_config

I haven't thought deeper about it, but having something dedicated might work better than trying to repurpose the current launcher.