FVWM: Document mime type compliance?

Mark, 

Thanks for replying.  The following is the functions called, so not the
one you reference.

#Function FvwmMenuDirectory
DestroyFunc FuncFvwmMenuDirectory
AddToFunction FuncFvwmMenuDirectory
+ I PipeRead '/usr/bin/fvwm-menu-directory --title "%d" --dir "$0"'

Which as I said makes a Documents directory directly in the main menu
and then displays the files and directories as if they were a submenu of
"Documents".

The trouble I run into is that every file clicked on opens in vi,
directories open the next level down directory, and what I need is for
the files to open according to the mime type with the proper
application.  

Dominik, 
The man page suggest that you and Mikhael originally wrote this little
script.  Is there a config I've forgotten so that files will properly
open by mime type?  
For example I see in the man for fvwm-menu-directory a --exec-app
[command] which maybe means I need to include the app to run on a file,
but would that work for each mime type?  Maybe there is another
FvwmFunction which needs to be referenced to add mime type calls?
Maybe I'm using the wrong function even? 

Cheers, 
BrianA_MN
------------------------------------------------------------------------------------------------------------------
On Sun, 05 Jan 2020 22:54:46 -0600
"Mark Nejedlo" <[email protected]> wrote:

> On Sun, Jan 5, 2020, at 10:19 PM, Brian wrote:  
> > A while back I added the following to my config.
> > 
> > AddToMenu DOCMenu "Documents" Title
> > + MissingSubmenuFunction FuncFVWMMenuDIrectory
> > + "Documents" Popup /home/brian/Documents
> > 
> > With the hope that it would pull up a llst of documents in my home
> > documents directory and then easily select a document
> > and open it. Well the function does pull up the list of
> > documents/directories and opens subdirectories and files, but all
> > the documents open in "vi" and not in the application designated by
> > the file extension type ie .pdf, .ods, .doc, or .jpg.     
> 
> You didn't include the definition of FuncFVWMMenuDIrectory or the
> (presumably) script it points at, which is what does the heavy
> lifting for MissingSubmenuFunction.
> 
> Speculating wildly, if you are using fvwm_make_directory_menu.sh from
> the FVWM distribution in FuncFVWMMenuDIrectory, you are always
> getting vi because that is what fvwm_make_directory_menu.sh puts as
> the application to run for all non-directory files.  If you want
> different actions based on the extension, you'll need to write a more
> sophisticated script that is extension aware to use in the place of
> fvwm_make_directory_menu.sh.
> 
> Mark
>