Expanded EFM Actions only act on directories not files? #15

Open
opened 3 months ago by AVLinux · 2 comments

Hi,

As of this commit 422c0b6765 it became possible to add other items to the EFM 'Actions' menu. I have created several action Desktop files and they now appear as expected in the Action menu:

http://bandshed.net/images/screenshots/shot-2022-07-19_14-39-04.jpg

Here is an example of a Desktop file for an Action to install a Debian Package, note this Desktop file works as-is in other File Managers as a generic Custom Action so it is a valid working Desktop file:

[Desktop Entry]
Type=Application
Name=Install Debian Package
Comment=Install Local Debian Package with APT Install
Icon=deb
OnlyShowIn=Enlightenment;
NoDisplay=true
Exec=sudo debinstall %F
Terminal=true
MimeType=application/x-deb;application/vnd.debian.binary-package;
X-Enlightenment-Action-Mime=inode/directory
Categories=System;
StartupNotify=false
StartupWMClass=e_fm

If a Debian Package (.deb) file is selected within a directory and right-clicked on to show the 'Actions' menu and 'Install Debian Package' is selected as an Action then the file name and location is not passed to the install script, the directory name and location is which causes the script to fail because a valid file wasn't presented to be processed. The purpose of customized Actions in other File Managers is usually to process files not the directories themselves with the obvious exception of archiving a directory.

This is not limited to the Deb Installing Action, all Actions which involve selected files all fail with the same issue..

Can the recognition of file mimetypes and ability to select and process files within the directories be added to this EFM Action feature? This would really expand the usefulness and abilities of EFM!

Hi, As of this commit 422c0b6765aa5ffb6c8cd25f8fac461332a1eb58 it became possible to add other items to the EFM 'Actions' menu. I have created several action Desktop files and they now appear as expected in the Action menu: http://bandshed.net/images/screenshots/shot-2022-07-19_14-39-04.jpg Here is an example of a Desktop file for an Action to install a Debian Package, note this Desktop file works as-is in other File Managers as a generic Custom Action so it is a valid working Desktop file: ``` [Desktop Entry] Type=Application Name=Install Debian Package Comment=Install Local Debian Package with APT Install Icon=deb OnlyShowIn=Enlightenment; NoDisplay=true Exec=sudo debinstall %F Terminal=true MimeType=application/x-deb;application/vnd.debian.binary-package; X-Enlightenment-Action-Mime=inode/directory Categories=System; StartupNotify=false StartupWMClass=e_fm ``` If a Debian Package (.deb) file is selected within a directory and right-clicked on to show the 'Actions' menu and 'Install Debian Package' is selected as an Action then the file name and location is not passed to the install script, the directory name and location is which causes the script to fail because a valid file wasn't presented to be processed. The purpose of customized Actions in other File Managers is usually to process files not the directories themselves with the obvious exception of archiving a directory. This is not limited to the Deb Installing Action, all Actions which involve selected files all fail with the same issue.. Can the recognition of file mimetypes and ability to select and process files within the directories be added to this EFM Action feature? This would really expand the usefulness and abilities of EFM!
Poster

After some discussion on IRC it was found Filetype detection could be attained by putting the appropriate mimetype as follows (wav file example):

X-Enlightenment-Action-Mime=audio/x-wav

However the issue of any selected files being passed to the command line remains... When individual files are selected for processing the folder location not the file location gets passed to the command line so individual files cannot be processed with the Action.

After some discussion on IRC it was found Filetype detection could be attained by putting the appropriate mimetype as follows (wav file example): `X-Enlightenment-Action-Mime=audio/x-wav` However the issue of any selected files being passed to the command line remains... When individual files are selected for processing the folder location not the file location gets passed to the command line so individual files cannot be processed with the Action.
Poster

After git pull and building from bea94314bd
I'm running into some issues, better explained in a screencast Video here:

http://bandshed.net/video/EFM.mp4

After git pull and building from bea94314bd77d9dcfe102f40c9648e4d6c284d04 I'm running into some issues, better explained in a screencast Video here: http://bandshed.net/video/EFM.mp4
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: enlightenment/enlightenment#15
Loading…
There is no content yet.